This directory contains Amplifier's integrated design intelligence capability that provides reusable design methodology, knowledge, and specialist agents for any project.
Amplifier now includes comprehensive design intelligence that combines:
- Design Philosophy - Core design thinking and principles
- Knowledge Base - Evidence-based design knowledge
- Design Protocols - Reusable process templates and guidelines
- Design Specialists - 7 specialized AI agents
- Orchestration -
/designercommand for coordinating design work
docs/design/
├── README.md (this file)
├── knowledge-base/
│ ├── README.md - Knowledge base overview
│ ├── color-theory.md - Color science, WCAG contrast, color psychology
│ ├── animation-principles.md - 12 animation principles, easing, timing
│ ├── accessibility.md - WCAG 2.1 standards, POUR principles
│ └── typography.md - Type scales, font systems, responsive text
└── protocols/
├── COMPONENT-CREATION-PROTOCOL.md - Component design checklist
├── DESIGN-CHECKLIST.md - Nine dimensions evaluation
├── ANTI-PATTERNS.md - Common design mistakes to avoid
├── WIREFRAME-STANDARDS.md - Wireframe guidelines
└── REQUIREMENTS-TEMPLATE.md - Design requirements template
Core design philosophy is located in ai_context/ alongside software development philosophy:
ai_context/DESIGN-PHILOSOPHY.md- Five Pillars deep diveai_context/DESIGN-PRINCIPLES.md- Quick reference guideai_context/design/DESIGN-FRAMEWORK.md- 9 Dimensions + 4 Layers methodologyai_context/design/DESIGN-VISION.md- Beyond the artifact philosophy
These are automatically imported via @CLAUDE.md for all Claude Code sessions.
Seven specialist agents are available in .claude/agents/:
- animation-choreographer - Motion design and transitions
- art-director - Aesthetic strategy and visual direction
- component-designer - Component design and creation
- design-system-architect - Design system architecture
- layout-architect - Information architecture and layout
- responsive-strategist - Device adaptation and responsive design
- voice-strategist - Voice & tone for UI copy
The /designer command orchestrates design work by routing tasks to appropriate specialists:
/designer create a button component with hover states
The command will:
- Analyze your request
- Select appropriate specialist(s)
- Coordinate their work
- Deliver comprehensive design output
You can also invoke design agents directly using the Task tool:
Task with subagent_type="component-designer": "Design a button component..."
Design agents automatically reference the knowledge base. You can also reference it directly:
@docs/design/knowledge-base/color-theory.md
@docs/design/protocols/COMPONENT-CREATION-PROTOCOL.md
All design work evaluates against nine dimensions:
- Purpose - Why does this exist?
- Visual Hierarchy - What should users notice first?
- Color & Contrast - Are colors accessible and meaningful?
- Typography - Is text readable and scannable?
- Spacing - Does whitespace guide the eye?
- Responsive Design - Does it work on all devices?
- Accessibility - Can everyone use it?
- Motion - Does animation serve a purpose?
- Voice - Is the copy clear and appropriate?
Design operates at four integrated layers:
- Foundational - Tokens, typography, color systems
- Structural - Layout, spacing, grid systems
- Behavioral - Interactions, animations, states
- Experiential - Complete user journeys
- User vision transformed - Take user's raw ideas and refine them
- Evidence-based decisions - Use knowledge base, not trends
- Accessible by default - WCAG 2.1 AA minimum
- Purposeful, not decorative - Every element serves a function
- Technically implementable - Design within web platform constraints
When working on a project, design agents create project-specific files:
.design/AESTHETIC-GUIDE.md- Project visual direction (created by art-director).design/specs/[feature]-[date].md- Design specifications per feature
These are separate from the reusable design capability in this directory.
Design intelligence integrates seamlessly with Amplifier's software development philosophy:
- Ruthless simplicity applies to both code and design
- Modular design philosophy - Components are self-contained bricks
- Analysis-first - Understand before designing/implementing
- Test-driven - Design specifications precede implementation
- Explore the knowledge base - Understand the evidence-based design foundation
- Review design protocols - Learn the design process workflows
- Try /designer - Experience orchestrated design intelligence
- Read philosophy docs - Understand the design thinking framework