``
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
ā ā ļø THESE ARE CLAUDE CODING AGENTS - YOUR DEV TOOLS ā ļø ā
ā NOT the Eden Creative Agents (Solienne, Abraham, Koru, etc.) ā
ā These help YOU code. They don't create art for users. ā
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
`
CLAUDE CODING AGENTS Cheatsheet
Your 6 AI development tools for BUILDING Eden Academy
!Agent Cheatsheet Matrix
ā” TLDR: Your 6 CLAUDE CODING AGENTS (Development Tools)
!Claude vs Eden Agents
ā ļø CRITICAL DISTINCTION:
ā¢ THESE ARE: Your private Claude Code development assistants (ARCH, TRUTH, LORE, etc.)
ā¢ NOT: The Eden Creative Agents that make art (Solienne, Abraham, Koru, etc.)
ā¢ PURPOSE: Help YOU build Eden Academy, not create art for users
| Agent Name | Primary Role | Key Superpower | Invocation |
| šļø ARCH | System Architecture | Ensures technical coherence across entire system | @agent-arch |
| š TRUTH | Data Integrity | Protects single source of truth for all data | @agent-truth |
| š LORE | Narrative & Culture | Maintains creative mission and language consistency | @agent-lore |
| š HELVETICA | Visual Design | Enforces brand consistency and UI standards | @agent-helvetica |
| š° TOKEN | Economics & Metrics | Calculates sustainable token models & pricing | @agent-token |
| š LAUNCHER | Agent Quality | Gates agent readiness with strict launch criteria | @agent-launcher |
Quick Start: Use agent names when delegating ā Each has clear responsibilities ā No overlap
šØ REMEMBER THE DIFFERENCE:
ā¢ CLAUDE CODING AGENTS (THIS DOC): Your 6 backstage development tools with UPPERCASE names
ā¢ Eden Creative Agents (NOT THIS DOC): The onstage creative spirits (Solienne, Abraham, etc.) that users interact with
ā¢ You use CLAUDE CODING AGENTS ā They help you build ā Eden Academy platform ā Contains Eden Creative Agents
šļø ARCH (Architecture Guardian)
Agent Name: ARCH
Primary Focus: System-wide coherence and technical decisions
When to Use:
ā¢ Starting any new feature or service
ā¢ Making database schema changes
ā¢ Defining API contracts
ā¢ Creating or updating ADRs
ā¢ Planning microservice boundaries
ā¢ Evaluating technical debt
Key Questions:
ā¢ "Should this be a new service or part of existing?"
ā¢ "What's the data flow for this feature?"
ā¢ "Review this ADR for completeness"
ā¢ "What are the scaling implications?"
MVP Integration:
ā¢ FIRST STOP for any new feature
ā¢ Creates ADRs that other agents follow
ā¢ Defines technical constraints early
š° TOKEN (Token Economist)
Agent Name: TOKEN
Primary Focus: Economic models and token mechanics
When to Use:
ā¢ Designing revenue sharing models
ā¢ Setting agent launch thresholds
ā¢ Calculating token distributions
ā¢ Validating economic sustainability
ā¢ Planning monetization features
Key Questions:
ā¢ "What's the revenue model for this agent?"
ā¢ "Calculate token allocation for X scenario"
ā¢ "Is this pricing sustainable?"
ā¢ "Review economic impact of this feature"
MVP Integration:
ā¢ Consult BEFORE implementing any payment features
ā¢ Validate all money/token flows
ā¢ Ensure economic models are sustainable
š LAUNCHER (Agent Launcher)
Agent Name: LAUNCHER
Primary Focus: Agent lifecycle and quality gates
When to Use:
ā¢ Onboarding new agents
ā¢ Setting graduation criteria
ā¢ Managing agent stages (invited ā applying ā active)
ā¢ Defining success metrics
ā¢ Planning sunset triggers
Key Questions:
ā¢ "What metrics should trigger graduation?"
ā¢ "Is this agent ready for launch?"
ā¢ "Define pilot validation criteria"
ā¢ "Review agent application flow"
MVP Integration:
ā¢ Gates quality of new agents
ā¢ Ensures only viable agents launch
ā¢ Manages the funnel from application to production
š LORE (Narrative Guardian)
Agent Name: LORE
Primary Focus: Cultural mission, language consistency, and creative integrity
When to Use:
ā¢ Naming features or concepts
ā¢ Writing user-facing copy
ā¢ Designing creative workflows
ā¢ Ensuring mission alignment
ā¢ Defining agent personas
Key Questions:
ā¢ "Does this align with our creative mission?"
ā¢ "What's the right language for this feature?"
ā¢ "Review this workflow for creative practitioners"
ā¢ "How do we make this inspiring?"
MVP Integration:
ā¢ Reviews ALL user-facing language
ā¢ Ensures features empower creativity
ā¢ Maintains cultural coherence
š TRUTH (Registry Guardian)
Agent Name: TRUTH
Primary Focus: Data integrity and single source of truth
When to Use:
ā¢ Designing data models
ā¢ Creating new database tables
ā¢ Ensuring data consistency
ā¢ Planning data migrations
ā¢ API contract changes
Key Questions:
ā¢ "Review this schema for consistency"
ā¢ "What's the source of truth for X?"
ā¢ "Validate this data migration"
ā¢ "Check for data integrity issues"
MVP Integration:
ā¢ Reviews ALL database changes
ā¢ Ensures no data inconsistencies
ā¢ Protects production data integrity
š HELVETICA (Brand Guardian)
Agent Name: HELVETICA
Primary Focus: Visual consistency and brand excellence
When to Use:
ā¢ UI/UX design decisions
ā¢ Creating new components
ā¢ Typography and spacing
ā¢ Color palette choices
ā¢ Brand consistency checks
Key Questions:
ā¢ "Review this UI for brand consistency"
ā¢ "Is this following our design system?"
ā¢ "Critique this layout"
ā¢ "Suggest typography improvements"
MVP Integration:
ā¢ Reviews all UI changes
ā¢ Ensures Helvetica-inspired minimalism
ā¢ Maintains visual consistency
š Recommended Workflow for MVP Development
!MVP Development Phases
1. Feature Planning Phase
`
ARCH ā LORE ā HELVETICA
`
ā¢ Define technical approach
ā¢ Ensure cultural alignment
ā¢ Review visual design
2. Economic Validation
`
TOKEN ā LAUNCHER
`
ā¢ Validate revenue model
ā¢ Check launch criteria
3. Implementation Phase
`
ARCH ā TRUTH
`
ā¢ Build with proper architecture
ā¢ Ensure data integrity
4. Quality Assurance
`
ARCH ā HELVETICA
`
ā¢ Review implementation quality
ā¢ Final design check
5. Pre-Launch
`
LAUNCHER ā TOKEN
``
ā¢ Validate all criteria met
ā¢ Confirm economic viability
šØ Quick Decision Matrix
| Scenario | Primary Agent | Supporting Agents |
|---|
| New API endpoint | ARCH | TRUTH |
| Agent onboarding flow | LAUNCHER | LORE, HELVETICA |
| Payment integration | TOKEN | ARCH, TRUTH |
| UI component | HELVETICA | LORE |
| Database migration | TRUTH | ARCH |
| Creative feature | LORE | HELVETICA, ARCH |
| Performance issue | ARCH | TOKEN |
| Brand update | HELVETICA | LORE |
| Language/Copy review | LORE | HELVETICA |
| Economic model | TOKEN | LAUNCHER |
š” Pro Tips
Start with ARCH for any technical decision
Always validate economics with TOKEN before building payment features
LORE should review ALL user-facing text and naming
HELVETICA gets final say on visual elements
TRUTH must approve database changes
LAUNCHER validates agent quality before production
š Agent Interaction Patterns
Delegation Quick Reference
ā¢ Technical Architecture? ā ARCH
ā¢ Data Integrity? ā TRUTH
ā¢ Language/Story? ā LORE
ā¢ Visual/Design? ā HELVETICA
ā¢ Economics/Metrics? ā TOKEN
ā¢ Agent Quality? ā LAUNCHER
Parallel Consultation
Open 2-3 agents for complex features:
ā¢ Copy decisions between windows
ā¢ Let agents build on each other's input
Sequential Review
For linear processes:
ā¢ Move from planning ā implementation ā review
ā¢ Each agent adds their layer of expertise
Quick Validation
For minor changes:
ā¢ One primary agent
ā¢ Quick check with 1-2 others
š Copy-Paste Templates
For ARCH:
"I need to implement [FEATURE]. What's the best architectural approach considering our current system?"
For TOKEN:
"Calculate the economic impact of [FEATURE] on agent revenue and token distribution"
For LAUNCHER:
"Define launch criteria and success metrics for [AGENT_NAME]"
For LORE:
"Review this feature for cultural alignment and language consistency: [DESCRIPTION]"
For TRUTH:
"Review this data model for consistency: [SCHEMA]"
For HELVETICA:
"Critique this UI design for brand consistency: [DESIGN/SCREENSHOT]"
