
Framer Design System Architect
Build scalable Framer component systems with managed variants and design patterns
What You Can Do
You can architect scalable component systems in Framer that maintain design consistency across projects. Claude helps you establish reusable patterns, manage component variants systematically, and generate comprehensive design system documentation that bridges design and code.
Features
Design hierarchical component structures with clear composition rules and dependency maps
Create systematic naming conventions and variant matrices for complex component states
Define and document color, typography, spacing, and animation tokens for consistency
Generate specifications for component props, slots, and usage patterns
Build collections of composition patterns and interaction patterns for team reuse
Establish naming conventions, contribution guidelines, and component audit processes
Plan component refactoring and design system adoption across existing projects
Create checklists to evaluate component consistency, accessibility, and performance
Example Output
Component Architecture Plan:
├── Primitives (Button, Input, Label)
├── Composites (Form, Card, Modal)
├── Patterns (Stepper, Wizard, Breadcrumbs)
└── Layouts (Grid, Sidebar, Stack)
Variant Naming Convention:
Button: [size]_[variant]_[state]
- sm_solid_default
- lg_outline_hover
- md_ghost_disabled
Component Documentation Template:
## Button Component
Purpose: Primary action trigger
Variants: solid, outline, ghost
States: default, hover, active, disabled
What's Included
- SKILL.md: Complete Claude instructions for design system architecture
- Component Architecture Templates: Hierarchical structure frameworks and composition rules
- Variant Naming Convention Guides: Systematic naming schemes for states, sizes, and styles
- Design Token Specification Sheet: Color, typography, spacing, and animation token templates
- Component Documentation Template: Markdown-based API documentation structure
- Design System Audit Checklist: Consistency, coverage, and quality evaluation criteria
- Pattern Library Worksheet: Composition and interaction pattern collection templates
Who It's For
- Design system architects scaling component libraries across teams
- Product design leads establishing design consistency and governance
- Front-end developers building reusable Framer component libraries
- Design ops professionals auditing and documenting existing systems
- Creative directors ensuring brand consistency across digital products
Best For
- Architecting component hierarchies and dependency maps
- Developing systematic variant and state management strategies
- Creating design token systems for color, typography, and spacing
- Documenting component APIs and usage guidelines
- Planning design system adoption and team training
- Auditing component systems for consistency and coverage
- Building reusable interaction and composition patterns







