Refresh UI/UX context from design system, Storybook, and codebase
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
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 patternsNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Produce an accounts-receivable aging report and surface overdue invoices for a Well workspace. Use when the user asks who owes them money, an AR aging report, overdue invoices, days sales outstanding (DSO), or which customers to chase.
The English summary is being prepared. Showing the original description.
Iterate until success or limit, composing existing skills with Jidoka integration
The English summary is being prepared. Showing the original description.
Build a balance sheet (bilan) from a Well workspace. Use when the user asks for a balance sheet, bilan, assets/liabilities/equity, or financial position at a point in time.
The English summary is being prepared. Showing the original description.
Generate and maintain BPMN 2.0 diagrams linked to Gherkin scenarios
The English summary is being prepared. Showing the original description.
Forecast cash flow and runway for a Well workspace from booked invoices and collected bank transactions. Use when the user asks for a cash-flow forecast, runway, how long until they run out of cash, projected balance, or expected inflows/outflows.
The English summary is being prepared. Showing the original description.
Review code changes against hard rules and conventions
The English summary is being prepared. Showing the original description.