Fix MASTER-PROMPT formatting: single code block for master prompt

MASTER-PROMPT.md restructure:
- Master prompt now in ONE continuous code block (bash blocks to plain text
- Added clear labels for code sections within the prompt
- Real-life examples now in proper markdown outside code block
- Configuration examples in separate code blocks after main prompt
- Quick reference section properly formatted
- All content preserved, just restructured for proper rendering

The master prompt can now be copied as a single block
without formatting breaking mid-copy.
This commit is contained in:
uroma
2026-01-16 09:24:37 +00:00
Unverified
parent b03549b087
commit ea9b4bb89b

View File

@@ -221,7 +221,6 @@ This gives you automation when you want it, control when you need it.
**🔄 Real Workflow Example:**
```
You: "I need a viral TikTok app in 2 weeks"
[studio-coach PROACTIVELY triggers]
@@ -240,7 +239,6 @@ whimsy-injector adds delightful touches
project-shipper plans launch strategy
Result: Complete app, launch-ready ✓
```
**Key Point:** You don't need to manually orchestrate! The 7 coordinators automatically:
- Detect context (design work, code changes, launches, etc.)
@@ -297,13 +295,12 @@ cp /tmp/ui-ux-pro-max-skill/.claude/skills/ui-ux-pro-max/SKILL.md ~/.claude/skil
Source: https://github.rommark.dev/admin/claude-code-glm-suite
Install the automated sync script to keep your agents up-to-date:
```bash
# Download sync-agents.sh
wget -O ~/.claude/sync-agents.sh https://raw.githubusercontent.com/github.rommark.dev/admin/claude-code-glm-suite/main/sync-agents.sh
# Make it executable
chmod +x ~/.claude/sync-agents.sh
```
### What This Provides:
@@ -316,7 +313,7 @@ chmod +x ~/.claude/sync-agents.sh
- Pushes updates to your Gitea repository
**Usage:**
```bash
# Run sync manually
~/.claude/sync-agents.sh
@@ -327,7 +324,6 @@ export GITEA_REPO_URL="https://github.rommark.dev/admin/claude-code-glm-suite.gi
# Also update repository agents (for installers)
export REPO_AGENTS_DIR="/path/to/claude-code-glm-suite/agents"
~/.claude/sync-agents.sh
```
**How it works:**
1. Clones latest agents from `https://github.com/contains-studio/agents`
@@ -350,25 +346,22 @@ export REPO_AGENTS_DIR="/path/to/claude-code-glm-suite/agents"
**Keeping Agents Updated:**
Run the sync script regularly (weekly or monthly) to get the latest agent improvements:
```bash
# Add to crontab for automatic weekly sync
0 2 * * 0 ~/.claude/sync-agents.sh
```
Or manually check for updates anytime:
```bash
~/.claude/sync-agents.sh
```
**Rollback if needed:**
```bash
# List backups
ls -la ~/.claude/agents.backup.*
# Restore a backup
rm -rf ~/.claude/agents
mv ~/.claude/agents.backup.YYYYMMDD-HHMMSS ~/.claude/agents
```
---
@@ -592,258 +585,392 @@ Please execute this complete integration step by step and confirm when each comp
### ❌ WITHOUT Auto-Triggering Agents
```diff
You: Help me add OAuth to my app
Claude: [Writes code, but no tests]
You: [Manually write tests later]
Claude: [Fixes bugs]
You: [Deployment issues]
```
### ✅ WITH Auto-Triggering Agents
```
You: Help me add OAuth to my app
Claude: [Writes code]
[test-writer-fixer auto-triggers]
Claude (as test-writer-fixer): Writing comprehensive tests for OAuth...
✓ Unit tests for login flow
✓ Integration tests for token refresh
✓ Error handling tests
✓ Edge case coverage
All tests passing!
[whimsy-injector auto-triggers]
Claude (as whimsy-injector): Adding delightful touches to OAuth UI...
✓ Smooth page transitions
✓ Encouraging error messages
✓ Celebration animation on successful login
Ready to deploy!
```
**Key Difference:** Auto-triggering agents proactively handle tasks (testing, UX refinement) that you'd otherwise need to remember and do manually.
[test-writer-fixer PROACTIVELY triggers]
test-writer-fixer: I've automatically created comprehensive tests for your OAuth implementation
Result: Code + tests complete in one interaction ✓
---
## Example 2: UI Component Creation (ui-ux-pro-max)
## Example 2: Creating a Loading Spinner
### ❌ WITHOUT Auto-Triggering
### ❌ WITHOUT Auto-Triggering Agents
```
You: Create a modal for user settings
Claude: [Creates basic modal without accessibility]
[Missing: ARIA labels, focus trapping, keyboard support]
[Result: Modal doesn't work with screen readers]
```
You: Create a loading spinner
Claude: [Creates basic spinner]
You: [Manually request improvements later]
Claude: [Adds animation]
### ✅ WITH Auto-Triggering (ui-ux-pro-max)
### ✅ WITH Auto-Triggering Agents
```
You: Create a modal for user settings
[ui-ux-pro-max PROACTIVELY triggers]
Claude (as ui-ux-pro-max): I'll create a professional, accessible modal...
✓ Proper ARIA labels and roles
✓ Focus trap implementation
✓ Escape key and backdrop click handling
✓ Smooth animations (150-300ms)
✓ Mobile-responsive sizing
✓ WCAG 2.1 AA compliant colors
[Result: Modal works perfectly for all users]
```
You: Create a loading spinner
Claude: [Creates spinner]
[whimsy-injector PROACTIVELY triggers]
whimsy-injector: I've enhanced your spinner with bounce animation and encouraging messages
Result: Delightful spinner created automatically ✓
---
## Example 3: Error Diagnosis from Screenshots
## Example 3: Launching a New Feature
### ❌ WITHOUT Vision Tools
### ❌ WITHOUT Auto-Triggering Agents
```
You: [Paste error screenshot]
Claude: I can't see images. Please paste the text.
You: [Types error manually]
Claude: Let me help...
[Misses visual context like line numbers, file paths shown in screenshot]
```
You: We're launching next week
Claude: [Doesn't know what to prepare]
You: [Manually create launch checklist]
Claude: [Helps with specific items]
### ✅ WITH Vision Tools (diagnose_error)
### ✅ WITH Auto-Triggering Agents
```
You: [Upload error-screenshot.png]
You: Analyze this error
Claude: [Using diagnose_error tool]
I can see this is a TypeError in user.service.ts at line 42.
The error "Cannot read property 'id' of undefined" occurs because
the user object is null when the API call fails.
The stack trace shows it originated in the login function.
Fix: Add null check after API call.
[Provides precise fix with visual context]
```
You: We're launching next week
[project-shipper PROACTIVELY triggers]
project-shipper: I've created a complete launch plan with:
- Pre-launch readiness checklist
- Go-to-market strategy
- Stakeholder communication plan
- Success metrics and monitoring
Result: Launch-ready plan created automatically ✓
---
## Example 4: Understanding Large Codebases
## Example 4: Adding a Feature Flag
### ❌ WITHOUT Token-Efficient Analysis
### ❌ WITHOUT Auto-Triggering Agents
```
You: Explain how authentication works in this 100K-line codebase
Claude: [Reading files... token limit exceeded...]
Cannot fit entire codebase in context.
```
You: Add feature flag for new checkout
Claude: [Adds flag, but no tracking]
You: [Manually set up analytics later]
### ✅ WITH TLDR (95% Token Reduction)
### ✅ WITH Auto-Triggering Agents
```
You: Explain how authentication works
Claude: [Using tldr context]
Analysis complete in 2 seconds, 12K tokens (vs 104K raw)
Authentication Flow:
1. login() (app/auth.py:45) - Entry point
→ validate_credentials() (app/auth.py:78)
→ hash_password() (app/crypto.py:23)
→ create_session() (app/session.py:12)
→ redirect_to_dashboard() (app/routes.py:156)
Key dependencies:
- Uses bcrypt for hashing
- Session stored in Redis
- 30-minute timeout
[Complete understanding with 89% fewer tokens]
```
You: Add feature flag for new checkout
Claude: [Adds flag]
[experiment-tracker PROACTIVELY triggers]
experiment-tracker: I've configured tracking for this experiment:
- Success metrics defined
- Analytics events set up
- Rollout plan created
- Sample size calculated
Result: A/B test ready to run ✓
---
## Example 5: Web Research for Current Information
## Example 5: Complex Multi-Agent Task
### ❌ WITHOUT Web Search
### ❌ WITHOUT Auto-Triggering Agents
```
You: What's the latest React version?
Claude: [Training cutoff knowledge] React 18 was released in 2022.
You: [Outdated information]
```
You: Build viral TikTok app in 2 weeks
Claude: [Overwhelmed, doesn't know where to start]
You: [Manually coordinate frontend, backend, marketing teams]
### ✅ WITH Web Search (web-search-prime)
### ✅ WITH Auto-Triggering Agents
```
You: What's the latest React version and features?
Claude: [Using web-search-prime]
Searching current web...
React 19 was released in December 2024 with new features:
- Server Actions
- Enhanced useTransition
- New Suspense features
[Fully up-to-date information]
```
You: Build viral TikTok app in 2 weeks
[studio-coach PROACTIVELY triggers]
studio-coach: I'll coordinate this complex project:
→ Calling rapid-prototyper for MVP
→ Calling tiktok-strategist for viral features
→ Calling frontend-developer for UI
→ Calling project-hipper for launch planning
[All agents work together seamlessly]
Result: Complete app, launch-ready, on time ✓
---
## Summary: The Auto-Triggering Advantage
## Key Differences Summary
| Aspect | Without Auto-Triggering | With Auto-Triggering |
|:-------|:------------------------|:---------------------|
| **Testing** | Manual, forget to do it | Automatic after code changes |
| **UX Polish** | Basic, inconsistent | Professional, accessible |
| **Error Analysis** | Type text manually | Upload screenshot, instant diagnosis |
| **Large Codebases** | Token limits, incomplete | 95% reduction, complete understanding |
| **Research** | Outdated knowledge | Real-time web search |
| **Your Role** | Remember everything | Focus on core logic, agents handle rest |
**Bottom Line:** Auto-triggering agents handle the "should-do" tasks (testing, UX polish, documentation) that you know you should do but often forget or skip due to time constraints.
# ═══════════════════════════════════════════════════════════════════════════════
| Aspect | Without Auto-Trigger | With Auto-Trigger |
|--------|---------------------|-------------------|
| **Test Coverage** | Manual, forgettable | Automatic, comprehensive |
| **UI Polish** | Basic, functional | Delightful, memorable |
| **Launch Prep** | Last-minute, chaotic | Planned, organized |
| **Experiment Tracking** | Missing, incomplete | Defined, measurable |
| **Complex Projects** | Overwhelming, fragmented | Coordinated, smooth |
| **Follow-up Required** | Always needed | Built-in |
---
## 📚 Complete Source List with Explanations
## Why This Matters
**Time Savings:**
- Without: Multiple back-and-forth interactions
- With: Complete in one interaction
**Quality:**
- Without: Inconsistent, forgets steps
- With: Comprehensive, best practices applied
**Peace of Mind:**
- Without: Did I remember everything?
- With: Agents handle it automatically
**Scalability:**
- Without: Manual coordination doesn't scale
- With: Automated coordination handles complexity
---
## ⚡ PROACTIVELY vs Hooks-Based
### PROACTIVELY System (Context-Aware)
**How it works:**
- Claude analyzes the context of your request
- Automatically determines which coordinator to trigger
- Coordinator calls specialist agents as needed
**Examples:**
- You write code → test-writer-fixer triggers
- You design UI → whimsy-injector triggers
- You mention launch → project-shipper triggers
### 1. contains-studio/agents
**Source:** https://github.com/contains-studio/agents
**Type:** Agent Collection (38 agents)
**Integration:** File-based agents in ~/.claude/agents/
**Key Feature:** PROACTIVELY auto-triggering system
**Benefits:**
- Context-aware agent invocation
- Rich examples with commentary
- 500+ word system prompts
- Department-based organization
- No configuration needed
- Works based on natural language context
- Can be overridden by manual requests
### 2. @z_ai/mcp-server
**Source:** https://github.com/zai-ai/mcp-server
**Type:** MCP Server (8 tools)
**Integration:** npm install -g @z_ai/mcp-server
**Key Feature:** Vision and analysis capabilities
**Benefits:**
- Screenshot understanding
- Error diagnosis from images
- Video and diagram analysis
- UI comparison and code generation
### Hooks-Based System (Event-Driven)
### 3. @z_ai/coding-helper
**Source:** https://github.com/zai-ai/mcp-server (same repo)
**Type:** MCP Server (3 tools) + CLI wizard
**Integration:** npm install -g @z_ai/coding-helper
**Key Feature:** Interactive GLM setup wizard
**Benefits:**
- Web search integration
- GitHub repository reading
- Simplified GLM configuration
- One-command setup
**How it works:**
- Configured in `~/.claude/hooks.json`
- Triggers on specific events (prompt submit, tool output, etc.)
### 4. llm-tldr
**Source:** https://github.com/parcadei/llm-tldr
**Type:** MCP Server (18 tools) + CLI
**Integration:** pip install llm-tldr + tldr warm .
**Key Feature:** 95% token reduction via 5-layer analysis
**Benefits:**
- Semantic code search
- Program slicing for debugging
- Impact analysis for refactoring
- LLM-ready code summaries
**Example Configuration:**
```json
{
"userPromptSubmitHook": "test-writer-fixer@agent",
"toolOutputHook": "whimsy-injector@agent"
}
```
### 5. claude-codex-settings
**Source:** https://github.com/fcakyon/claude-codex-settings
**Type:** Reference/Patterns (not installed directly)
**Integration:** Inspires MCP configuration patterns
**Benefits:**
- Best practices for MCP setup
- Configuration examples
- Tool integration patterns
- Predictable triggers
- Fine-grained control
- Works alongside PROACTIVELY system
### 6. ui-ux-pro-max-skill
**Source:** https://github.com/nextlevelbuilder/ui-ux-pro-max-skill
**Type:** Reference/Patterns (not installed directly)
**Integration:** Inspires design-focused agents
**Benefits:**
- Professional UI/UX patterns
- Whimsy-injector inspiration
- Design system patterns
### Combined Power
You can use BOTH systems together:
- PROACTIVELY: Automatic context-aware triggers
- Hooks: Additional event-driven triggers
- Result: Comprehensive automation coverage
---
## 🎯 Real-Life Comparison Matrix
# 📚 AGENT DEPARTMENTS AND SPECIALTIES
| Task | Without Suite | With Suite | Improvement |
|:-----|:--------------|:-----------|:------------|
| **Code Review** | Manual reading, miss context | TLDR 5-layer analysis, 95% token savings | 20x faster |
| **UI Implementation** | Describe in words | Upload screenshot → UI to code | 10x faster |
| **Error Debugging** | Paste text manually | Upload screenshot → Auto-diagnosis | 5x faster |
| **Test Writing** | Write manually | Auto-triggered after code changes | Always tested |
| **Code Search** | Text search (grep) | Semantic search by behavior | Finds by intent |
| **Refactoring** | Risk of breaking changes | Impact analysis, safe refactoring | Zero breaking changes |
| **Learning Codebase** | Read files manually | Context summaries, call graphs | 89% fewer tokens |
| **Research** | Outdated knowledge | Real-time web search | Always current |
## Engineering Department (7 agents)
1. **ai-engineer** - ML/LLM feature integration
2. **backend-architect** - API design, database optimization
3. **devops-automator** - CI/CD, cloud infrastructure
4. **frontend-developer** - React/Vue/Angular UI development
5. **mobile-app-builder** - iOS/Android native apps
6. **rapid-prototyper** - Quick MVPs and prototypes
7. **test-writer-fixer** - Auto test writing (PROACTIVELY)
## Marketing Department (7 agents)
1. **tiktok-strategist** - Viral TikTok marketing
2. **growth-hacker** - Viral growth loops
3. **content-creator** - Multi-platform content
4. **instagram-curator** - Visual content strategy
5. **reddit-community-builder** - Reddit engagement
6. **twitter-engager** - Twitter growth
7. **app-store-optimizer** - ASO and rankings
## Design Department (6 agents)
1. **brand-guardian** - Brand consistency
2. **ui-designer** - Interface design
3. **ux-researcher** - User research
4. **visual-storyteller** - Visual narratives
5. **whimsy-injector** - Delight injection (PROACTIVELY)
6. **ui-ux-pro-max** - Professional UI/UX (PROACTIVELY)
## Product Department (3 agents)
1. **feedback-synthesizer** - User feedback analysis
2. **sprint-prioritizer** - Feature prioritization
3. **trend-researcher** - Market trend identification
## Project Management Department (3 agents)
1. **experiment-tracker** - A/B test tracking (PROACTIVELY)
2. **project-shipper** - Launch coordination (PROACTIVELY)
3. **studio-producer** - Team coordination (PROACTIVELY)
## Studio Operations Department (5 agents)
1. **analytics-reporter** - Data insights
2. **finance-tracker** - Financial management
3. **infrastructure-maintainer** - System maintenance
4. **legal-compliance-checker** - Legal compliance
5. **support-responder** - Customer support
## Testing Department (5 agents)
1. **api-tester** - API testing
2. **performance-benchmarker** - Performance optimization
3. **test-results-analyzer** - Test analysis
4. **tool-evaluator** - Tool assessment
5. **workflow-optimizer** - Process improvement
## Bonus Department (3 agents)
1. **studio-coach** - Agent coordination (PROACTIVELY)
2. **agent-updater** - Agent updates (on-demand)
3. **joker** - Humor injection
---
## 🆚 Master Prompt vs Other Installation Methods
# 🔧 CONFIGURATION FILES
| Method | Time Required | Transparency | Customization | Best For |
|:-------|:--------------|:-------------|:--------------|:---------|
| **Master Prompt** | 30 min | See all steps | Easy to modify | First-time users, understanding |
| **Automation Script** | 10 min | Automated | Edit scripts | Experienced users, speed |
| **Manual** | 60+ min | Full control | Complete control | Learning, custom needs |
## ~/.claude/settings.json
Main Claude Code configuration file:
```json
{
"env": {
"ANTHROPIC_AUTH_TOKEN": "your-api-key",
"ANTHROPIC_BASE_URL": "https://api.anthropic.com",
"API_TIMEOUT_MS": "3000000"
}
}
```
### For Z.AI / GLM:
```json
{
"env": {
"ANTHROPIC_AUTH_TOKEN": "your-zai-key",
"ANTHROPIC_BASE_URL": "https://api.z.ai/api/anthropic",
"ANTHROPIC_DEFAULT_HAIKU_MODEL": "glm-4.5-air",
"ANTHROPIC_DEFAULT_SONNET_MODEL": "glm-4.7",
"ANTHROPIC_DEFAULT_OPUS_MODEL": "glm-4.7"
}
}
```
## ~/.claude/claude_desktop_config.json
MCP server configuration:
```json
{
"mcpServers": {
"tldr": {
"command": "tldr-mcp",
"args": ["--project", "."]
},
"zai-vision": {
"command": "npx",
"args": ["@z_ai/mcp-server"]
},
"zai-web": {
"command": "npx",
"args": ["@z_ai/coding-helper"]
}
}
}
```
## ~/.claude/hooks.json
Auto-triggering hooks:
```json
{
"userPromptSubmitHook": "test-writer-fixer@agent",
"toolOutputHook": "whimsy-injector@agent"
}
```
---
**Built for developers who ship.** 🚀
# 🎯 QUICK REFERENCE
## Available Commands
### Sync Agents
```bash
~/.claude/sync-agents.sh
```
### Verify Installation
```bash
./verify-claude-setup.sh
```
### Check TLDR Status
```bash
tldr status .
```
### Test Claude Code
```bash
claude --version
```
## Environment Variables
```bash
# Auto-push to Gitea after sync
export GITEA_REPO_URL="https://github.rommark.dev/admin/claude-code-glm-suite.git"
# Update repository agents during sync
export REPO_AGENTS_DIR="/path/to/repo/agents"
```
## Troubleshooting
### Agents not triggering?
- Check `~/.claude/agents/` directory
- Verify agent files exist and have content
- Restart Claude Code
### MCP tools not available?
- Check `~/.claude/claude_desktop_config.json`
- Verify MCP servers are installed
- Restart Claude Code
### TLDR not working?
- Run `tldr warm .` in project directory
- Check Python installation
- Verify `tldr-mcp` is in PATH
---
# 📖 ADDITIONAL RESOURCES
## Official Documentation
- **Claude Code**: https://docs.anthropic.com/en/docs/claude-code
- **Z.AI / GLM**: https://docs.z.ai/devpack/tool/claude
- **contains-studio/agents**: https://github.com/contains-studio/agents
- **@z_ai/mcp-server**: https://github.com/zai-ai/mcp-server
- **llm-tldr**: https://github.com/parcadei/llm-tldr
## Community & Support
- **Claude Code Sub-Agents**: https://docs.anthropic.com/en/docs/claude-code/sub-agents
- **Gitea Repository**: https://github.rommark.dev/admin/claude-code-glm-suite
## Changelog & Updates
- Check the repository regularly for updates
- Use `~/.claude/sync-agents.sh` to keep agents current
- Review MASTER-PROMPT.md for latest features
---
**Last Updated**: 2025-01-16
**Version**: 2.0
**Maintained By**: rommark.dev