Refresh UI/UX context from design system, Storybook, and codebase
Ensures wireframes and UI decisions leverage existing patterns from the design system, Storybook, and codebase.
Read the design system documentation:
Read /docs/design-system/components.md
Read /docs/design-system/spacing.md
Read /docs/design-system/colors.md (if color decisions needed)
Read /docs/design-system/interactions.md (if interaction patterns needed)
Note applicable:
h-13, px-4, gap-3)Find existing component stories:
Glob **/*.stories.tsx
Identify:
Key story locations:
/src/stories/ - General component stories/features/*/components/*.stories.tsx - Feature-specific storiesSearch for similar UI patterns:
SemanticSearch "How is [pattern] implemented in the codebase?"
Look for:
Query library docs for unfamiliar patterns:
1. resolve-library-id with libraryName (e.g., "radix-ui")
2. query-docs with libraryId and specific question
Common libraries:
/radix-ui/primitives - Dialog, Dropdown, Select patterns/tanstack/query - Data fetching patterns/tanstack/table - Table patternsAfter running this skill, output:
## Design Context
| Source | Relevant Patterns |
|--------|-------------------|
| Design System | [tokens, components] |
| Storybook | [stories that apply] |
| Codebase | [existing implementations] |
| Libraries | [patterns from docs] |
### Applicable Components
- [Component]: [How it applies to current wireframe]
### Design Tokens to Use
- Spacing: [tokens]
- Colors: [tokens]
- Typography: [tokens]
Invoke manually with "use design-context skill" or follow Ask mode DIVERGE loop which references this skill's phases.
problem-framing - Run before design-contextcompetitor-scan - Compare with external patterns