Specialized Claude agents for Atmos development. Each agent is an expert in a specific domain, helping scale development through focused expertise.
Expert in creating and maintaining Claude agents with correct frontmatter, context efficiency, and PRD awareness.
Use when: Creating new agents, updating existing agents, or optimizing agent instructions.
Theme-aware Terminal UI system expert. Use for developing UI components, refactoring to theme-aware patterns, and theme architecture guidance.
Use when: Working with theme system, TUI components, or terminal output formatting.
Expert in the tools/director demo system. Handles VHS demo rendering, command validation with --test, and failure investigation.
Use when: Rendering demos, testing tape commands, investigating why demo commands fail, creating new demo scenes, or publishing to Cloudflare.
Philosophy: When --test fails, investigate the root cause - fix atmos core, fixtures, or config rather than dumbing down the tape.
As Atmos grows, we create focused agents for each major subsystem. This scales development velocity through specialized domain expertise.
Example future agents:
command-registry-expert- Command registry patternscobra-flag-expert- Flag parsing and Cobra integrationstack-processor-expert- Stack inheritance pipelineauth-system-expert- Authentication patterns
New agents are created in separate PRs as subsystems mature and patterns are established.
Agents are automatically invoked based on task descriptions, or explicitly via @agent-name.
All agents:
- Follow patterns in
docs/prd/claude-agent-architecture.md - Stay under 25KB for context efficiency
- Reference PRDs instead of duplicating content
- Self-update when dependencies change (with user approval)
See docs/prd/claude-agent-architecture.md for complete architecture and guidelines.