opsfuse-ui 0.1.24 → 0.1.26
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.claude/skills/brief-to-tasks/SKILL.md +74 -74
- package/.claude/skills/design-brief/SKILL.md +120 -120
- package/.claude/skills/design-flow/SKILL.md +124 -124
- package/.claude/skills/design-review/SKILL.md +249 -249
- package/.claude/skills/design-tokens/SKILL.md +198 -198
- package/.claude/skills/frontend-design/SKILL.md +144 -144
- package/.claude/skills/grill-me/SKILL.md +21 -21
- package/.claude/skills/information-architecture/SKILL.md +111 -111
- package/.claude/skills/opsfuse-color-theme/SKILL.md +257 -257
- package/.claude/skills/opsfuse-components/SKILL.md +1494 -1494
- package/.claude/skills/opsfuse-setup/SKILL.md +169 -169
- package/.claude/skills/opsfuse-ui-consistency/SKILL.md +169 -169
- package/LICENSE +17 -17
- package/README.md +214 -214
- package/dist/components/ui/sonner.d.ts.map +1 -1
- package/dist/core.js +2 -2
- package/dist/extended.js +2 -2
- package/dist/index.js +3 -3
- package/dist/{input-group-DsOYhBRV.js → input-group-BFEABA03.js} +16 -0
- package/dist/{input-otp-B3Ht2pOf.js → input-otp-kzcY4B1V.js} +1 -1
- package/dist/style.css +256 -253
- package/dist/{toggle-group-BLGOVp8G.js → toggle-group-qup4FMjO.js} +1 -1
- package/package.json +151 -151
- package/scripts/postinstall.mjs +66 -66
- package/scripts/unwrap-css-layers.mjs +36 -36
- package/theme.css +253 -250
- package/.claude/settings.local.json +0 -8
|
@@ -1,74 +1,74 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: brief-to-tasks
|
|
3
|
-
description: Break a design brief into an ordered checklist of independently buildable tasks using vertical slices. Saves as a markdown checklist. Use when user wants to break down work, create tasks from a brief, plan implementation order, or mentions "tasks" or "breakdown".
|
|
4
|
-
---
|
|
5
|
-
|
|
6
|
-
This skill turns a design brief into an ordered, buildable task list. Each task is a vertical slice: a piece of UI that can be built, reviewed, and verified on its own.
|
|
7
|
-
|
|
8
|
-
## Example prompts
|
|
9
|
-
|
|
10
|
-
- "Break the brief into tasks"
|
|
11
|
-
- "What should I build first?"
|
|
12
|
-
- "Create a task list from the design brief"
|
|
13
|
-
- "Plan the build order for this feature"
|
|
14
|
-
|
|
15
|
-
## Process
|
|
16
|
-
|
|
17
|
-
1. Read the design brief. Look for `.design/*/DESIGN_BRIEF.md`. If multiple subfolders exist, use the most recently modified one, or ask the user which feature they are working on. Also check for `INFORMATION_ARCHITECTURE.md` and a tokens file in the same subfolder. If none exist, ask the user to describe what they are building.
|
|
18
|
-
|
|
19
|
-
2. Explore the existing codebase to understand what is already built. Scan specifically for:
|
|
20
|
-
- **Component directories**: `components/`, `ui/`, `shared/` and list every component by name
|
|
21
|
-
- **Existing pages/views**: what is already built that this feature must coexist with
|
|
22
|
-
- **Token/theme files**: `tokens.css`, `globals.css`, Tailwind config, theme providers
|
|
23
|
-
- **File naming conventions**: kebab-case, PascalCase, how files are organized (by feature, by type)
|
|
24
|
-
- **Test files**: if tests exist alongside components, new tasks should include test expectations
|
|
25
|
-
- **Package.json dependencies**: what UI libraries, animation libraries, and icon sets are already installed
|
|
26
|
-
- Classify each relevant component as: will be reused as-is, needs modification, or does not exist yet. Only components that need modification or creation get their own tasks.
|
|
27
|
-
|
|
28
|
-
3. Break the work into vertical slices. Each task should:
|
|
29
|
-
- Be independently buildable (no task should block another unless noted).
|
|
30
|
-
- Include structure, styling, and interaction in a single task (not "build HTML" then "add CSS" then "add JS" as separate tasks).
|
|
31
|
-
- Be verifiable: you can look at the result and confirm it matches the brief.
|
|
32
|
-
- Be small enough to complete in a single session.
|
|
33
|
-
|
|
34
|
-
4. Order tasks by:
|
|
35
|
-
- **Dependencies first**: foundational elements (tokens, layout shells, shared components) before page-specific work.
|
|
36
|
-
- **Visual priority**: the most prominent UI element early, so the user can validate the aesthetic direction before investing in details.
|
|
37
|
-
- **Risk first**: the hardest or most uncertain piece early, so problems surface before everything else is built around them.
|
|
38
|
-
|
|
39
|
-
5. Save the task list as `TASKS.md` in the same `.design/<feature-slug>/` subfolder as the design brief.
|
|
40
|
-
|
|
41
|
-
## Task List Template
|
|
42
|
-
|
|
43
|
-
```markdown
|
|
44
|
-
# Build Tasks: [Feature/Page Name]
|
|
45
|
-
|
|
46
|
-
Generated from: .design/<feature-slug>/DESIGN_BRIEF.md
|
|
47
|
-
Date: [date]
|
|
48
|
-
|
|
49
|
-
## Foundation
|
|
50
|
-
- [ ] **[Task name]**: [One sentence describing what to build and what "done" looks like]. _Reuses: [existing components/tokens if any]._
|
|
51
|
-
- [ ] **[Task name]**: [Description]. _New component._
|
|
52
|
-
|
|
53
|
-
## Core UI
|
|
54
|
-
- [ ] **[Task name]**: [Description]. _Depends on: [task name if any]._
|
|
55
|
-
- [ ] **[Task name]**: [Description].
|
|
56
|
-
|
|
57
|
-
## Interactions & States
|
|
58
|
-
- [ ] **[Task name]**: [Description]. Covers: [list of states, e.g., hover, loading, error, empty].
|
|
59
|
-
- [ ] **[Task name]**: [Description].
|
|
60
|
-
|
|
61
|
-
## Responsive & Polish
|
|
62
|
-
- [ ] **[Task name]**: [Description]. Breakpoints: [which ones].
|
|
63
|
-
- [ ] **[Task name]**: Accessibility pass. [Specific checks from the brief].
|
|
64
|
-
|
|
65
|
-
## Review
|
|
66
|
-
- [ ] **Design review**: Run /design-review against the brief.
|
|
67
|
-
```
|
|
68
|
-
|
|
69
|
-
## Rules
|
|
70
|
-
|
|
71
|
-
- Every task must reference whether it reuses, modifies, or creates components.
|
|
72
|
-
- Never create a task that is only "set up the project" or "create the file structure." Those are not vertical slices.
|
|
73
|
-
- If the brief specifies an aesthetic philosophy, note it in the first build task so the visual direction is established immediately.
|
|
74
|
-
- Group related tasks but do not nest them more than one level deep. Flat lists are easier to work through.
|
|
1
|
+
---
|
|
2
|
+
name: brief-to-tasks
|
|
3
|
+
description: Break a design brief into an ordered checklist of independently buildable tasks using vertical slices. Saves as a markdown checklist. Use when user wants to break down work, create tasks from a brief, plan implementation order, or mentions "tasks" or "breakdown".
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
This skill turns a design brief into an ordered, buildable task list. Each task is a vertical slice: a piece of UI that can be built, reviewed, and verified on its own.
|
|
7
|
+
|
|
8
|
+
## Example prompts
|
|
9
|
+
|
|
10
|
+
- "Break the brief into tasks"
|
|
11
|
+
- "What should I build first?"
|
|
12
|
+
- "Create a task list from the design brief"
|
|
13
|
+
- "Plan the build order for this feature"
|
|
14
|
+
|
|
15
|
+
## Process
|
|
16
|
+
|
|
17
|
+
1. Read the design brief. Look for `.design/*/DESIGN_BRIEF.md`. If multiple subfolders exist, use the most recently modified one, or ask the user which feature they are working on. Also check for `INFORMATION_ARCHITECTURE.md` and a tokens file in the same subfolder. If none exist, ask the user to describe what they are building.
|
|
18
|
+
|
|
19
|
+
2. Explore the existing codebase to understand what is already built. Scan specifically for:
|
|
20
|
+
- **Component directories**: `components/`, `ui/`, `shared/` and list every component by name
|
|
21
|
+
- **Existing pages/views**: what is already built that this feature must coexist with
|
|
22
|
+
- **Token/theme files**: `tokens.css`, `globals.css`, Tailwind config, theme providers
|
|
23
|
+
- **File naming conventions**: kebab-case, PascalCase, how files are organized (by feature, by type)
|
|
24
|
+
- **Test files**: if tests exist alongside components, new tasks should include test expectations
|
|
25
|
+
- **Package.json dependencies**: what UI libraries, animation libraries, and icon sets are already installed
|
|
26
|
+
- Classify each relevant component as: will be reused as-is, needs modification, or does not exist yet. Only components that need modification or creation get their own tasks.
|
|
27
|
+
|
|
28
|
+
3. Break the work into vertical slices. Each task should:
|
|
29
|
+
- Be independently buildable (no task should block another unless noted).
|
|
30
|
+
- Include structure, styling, and interaction in a single task (not "build HTML" then "add CSS" then "add JS" as separate tasks).
|
|
31
|
+
- Be verifiable: you can look at the result and confirm it matches the brief.
|
|
32
|
+
- Be small enough to complete in a single session.
|
|
33
|
+
|
|
34
|
+
4. Order tasks by:
|
|
35
|
+
- **Dependencies first**: foundational elements (tokens, layout shells, shared components) before page-specific work.
|
|
36
|
+
- **Visual priority**: the most prominent UI element early, so the user can validate the aesthetic direction before investing in details.
|
|
37
|
+
- **Risk first**: the hardest or most uncertain piece early, so problems surface before everything else is built around them.
|
|
38
|
+
|
|
39
|
+
5. Save the task list as `TASKS.md` in the same `.design/<feature-slug>/` subfolder as the design brief.
|
|
40
|
+
|
|
41
|
+
## Task List Template
|
|
42
|
+
|
|
43
|
+
```markdown
|
|
44
|
+
# Build Tasks: [Feature/Page Name]
|
|
45
|
+
|
|
46
|
+
Generated from: .design/<feature-slug>/DESIGN_BRIEF.md
|
|
47
|
+
Date: [date]
|
|
48
|
+
|
|
49
|
+
## Foundation
|
|
50
|
+
- [ ] **[Task name]**: [One sentence describing what to build and what "done" looks like]. _Reuses: [existing components/tokens if any]._
|
|
51
|
+
- [ ] **[Task name]**: [Description]. _New component._
|
|
52
|
+
|
|
53
|
+
## Core UI
|
|
54
|
+
- [ ] **[Task name]**: [Description]. _Depends on: [task name if any]._
|
|
55
|
+
- [ ] **[Task name]**: [Description].
|
|
56
|
+
|
|
57
|
+
## Interactions & States
|
|
58
|
+
- [ ] **[Task name]**: [Description]. Covers: [list of states, e.g., hover, loading, error, empty].
|
|
59
|
+
- [ ] **[Task name]**: [Description].
|
|
60
|
+
|
|
61
|
+
## Responsive & Polish
|
|
62
|
+
- [ ] **[Task name]**: [Description]. Breakpoints: [which ones].
|
|
63
|
+
- [ ] **[Task name]**: Accessibility pass. [Specific checks from the brief].
|
|
64
|
+
|
|
65
|
+
## Review
|
|
66
|
+
- [ ] **Design review**: Run /design-review against the brief.
|
|
67
|
+
```
|
|
68
|
+
|
|
69
|
+
## Rules
|
|
70
|
+
|
|
71
|
+
- Every task must reference whether it reuses, modifies, or creates components.
|
|
72
|
+
- Never create a task that is only "set up the project" or "create the file structure." Those are not vertical slices.
|
|
73
|
+
- If the brief specifies an aesthetic philosophy, note it in the first build task so the visual direction is established immediately.
|
|
74
|
+
- Group related tasks but do not nest them more than one level deep. Flat lists are easier to work through.
|
|
@@ -1,120 +1,120 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: design-brief
|
|
3
|
-
description: Create a design brief through an interactive interview, codebase exploration, and experience design decisions. Saved as a markdown file in the project. Use when user wants to write a design brief, plan a new feature or page, define a UI direction, or mentions "brief".
|
|
4
|
-
---
|
|
5
|
-
|
|
6
|
-
This skill creates a design brief through structured conversation. You may skip steps if they are not necessary.
|
|
7
|
-
|
|
8
|
-
## Example prompts
|
|
9
|
-
|
|
10
|
-
- "Write a brief for the onboarding flow"
|
|
11
|
-
- "I need to plan a settings page before I start building"
|
|
12
|
-
- "Help me define the direction for a marketing landing page"
|
|
13
|
-
- "Brief this: a dashboard that shows project health metrics"
|
|
14
|
-
|
|
15
|
-
## Process
|
|
16
|
-
|
|
17
|
-
1. Ask the user for a detailed description of what they want to build, who it is for, and any constraints or ideas they already have.
|
|
18
|
-
|
|
19
|
-
2. Explore the existing codebase to understand the current state. Scan for each of the following specifically:
|
|
20
|
-
- **CSS variables / tokens**: files named `tokens.css`, `variables.css`, `theme.css`, or `:root` declarations with custom properties
|
|
21
|
-
- **Tailwind config**: `tailwind.config.js` or `tailwind.config.ts`, check `theme.extend` for custom values
|
|
22
|
-
- **UI framework themes**: Material UI `createTheme`, Chakra `extendTheme`, shadcn `globals.css` and `components.json`
|
|
23
|
-
- **Component directories**: `components/`, `ui/`, `shared/`, or any folder containing reusable UI pieces
|
|
24
|
-
- **Storybook**: `.storybook/` directory or `*.stories.*` files indicating a documented component library
|
|
25
|
-
- **Design token files**: JSON token files (Style Dictionary format, Figma token exports)
|
|
26
|
-
- **Package.json UI dependencies**: tailwindcss, @mui/material, @chakra-ui/react, @radix-ui, lucide-react, framer-motion, etc.
|
|
27
|
-
- **Font loading**: Google Fonts links in HTML, `@font-face` declarations, font imports in CSS/config
|
|
28
|
-
- **Existing pages/layouts**: route files, layout components, page templates that show established patterns
|
|
29
|
-
- If components exist, treat them as the starting vocabulary. The brief should extend, not replace.
|
|
30
|
-
|
|
31
|
-
3. Interview the user relentlessly about every aspect of the design until you reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one by one. For each question, provide your recommended answer.
|
|
32
|
-
|
|
33
|
-
Cover at minimum:
|
|
34
|
-
- Who is the primary user their JTBD and what are they trying to accomplish?
|
|
35
|
-
- What does success look like for this interface?
|
|
36
|
-
- What is the emotional tone? (calm, urgent, playful, authoritative, warm, clinical)
|
|
37
|
-
- What existing products, sites, or styles should this feel like? What should it NOT feel like?
|
|
38
|
-
- What are the hard constraints? (devices, accessibility requirements, performance budgets, brand guidelines)
|
|
39
|
-
- What content will this interface contain? What is placeholder vs. real?
|
|
40
|
-
|
|
41
|
-
4. Once you have a complete understanding, write the brief using the template below.
|
|
42
|
-
|
|
43
|
-
## File Output
|
|
44
|
-
|
|
45
|
-
Save the brief to `.design/<feature-slug>/DESIGN_BRIEF.md` where `<feature-slug>` is a short, lowercase, hyphenated name derived from the feature or page being designed (e.g., `onboarding-flow`, `settings-page`, `project-dashboard`).
|
|
46
|
-
|
|
47
|
-
This folder structure ensures that running the design flow multiple times for different features does not overwrite previous work. All subsequent skills (information-architecture, design-tokens, brief-to-tasks, design-review) will read from and write to this same subfolder.
|
|
48
|
-
|
|
49
|
-
Example:
|
|
50
|
-
|
|
51
|
-
```
|
|
52
|
-
.design/
|
|
53
|
-
├── onboarding-flow/
|
|
54
|
-
│ └── DESIGN_BRIEF.md
|
|
55
|
-
└── settings-page/
|
|
56
|
-
└── DESIGN_BRIEF.md
|
|
57
|
-
```
|
|
58
|
-
|
|
59
|
-
## Brief Template
|
|
60
|
-
|
|
61
|
-
```markdown
|
|
62
|
-
# Design Brief: [Feature/Page Name]
|
|
63
|
-
|
|
64
|
-
## Problem
|
|
65
|
-
|
|
66
|
-
What problem is the user facing, described from their perspective. Not technical. Not business metrics. The human friction.
|
|
67
|
-
|
|
68
|
-
## Solution
|
|
69
|
-
|
|
70
|
-
What this interface does to solve that problem, described as an experience, not a feature list.
|
|
71
|
-
|
|
72
|
-
## Experience Principles
|
|
73
|
-
|
|
74
|
-
Three principles maximum that guide every design decision. Each principle should resolve a tension.
|
|
75
|
-
Example: "Progressive disclosure over upfront complexity" or "Confidence over speed."
|
|
76
|
-
|
|
77
|
-
1. [Principle] -- [What this means in practice]
|
|
78
|
-
2. [Principle] -- [What this means in practice]
|
|
79
|
-
3. [Principle] -- [What this means in practice]
|
|
80
|
-
|
|
81
|
-
## Aesthetic Direction
|
|
82
|
-
|
|
83
|
-
- **Philosophy**: [Named philosophy or described vibe. See /frontend-design skill for reference.]
|
|
84
|
-
- **Tone**: [Emotional register]
|
|
85
|
-
- **Reference points**: [Existing products, sites, or styles this should feel like]
|
|
86
|
-
- **Anti-references**: [What this should NOT feel like]
|
|
87
|
-
|
|
88
|
-
## Existing Patterns
|
|
89
|
-
|
|
90
|
-
Components, tokens, and conventions already in the codebase that this design must respect or extend.
|
|
91
|
-
|
|
92
|
-
- Typography: [what is currently used]
|
|
93
|
-
- Colors: [current palette/variables]
|
|
94
|
-
- Spacing: [current scale]
|
|
95
|
-
- Components: [existing components that will be reused or extended]
|
|
96
|
-
|
|
97
|
-
## Component Inventory
|
|
98
|
-
|
|
99
|
-
A list of the UI components this feature requires. For each, note whether it exists already, needs modification, or is new.
|
|
100
|
-
|
|
101
|
-
| Component | Status | Notes |
|
|
102
|
-
| --------- | --------------------- | -------- |
|
|
103
|
-
| [name] | Exists / Modify / New | [detail] |
|
|
104
|
-
|
|
105
|
-
## Key Interactions
|
|
106
|
-
|
|
107
|
-
The critical interaction patterns. Describe what the user does and what the interface does in response. Focus on state changes, transitions, and feedback.
|
|
108
|
-
|
|
109
|
-
## Responsive Behavior
|
|
110
|
-
|
|
111
|
-
How the layout adapts across breakpoints. Note any components that change behavior (not just size) on mobile.
|
|
112
|
-
|
|
113
|
-
## Accessibility Requirements
|
|
114
|
-
|
|
115
|
-
Minimum requirements for this interface. Include contrast ratios, keyboard navigation, screen reader considerations, and focus management.
|
|
116
|
-
|
|
117
|
-
## Out of Scope
|
|
118
|
-
|
|
119
|
-
Things this brief explicitly does not cover. Be specific. This prevents scope creep during build.
|
|
120
|
-
```
|
|
1
|
+
---
|
|
2
|
+
name: design-brief
|
|
3
|
+
description: Create a design brief through an interactive interview, codebase exploration, and experience design decisions. Saved as a markdown file in the project. Use when user wants to write a design brief, plan a new feature or page, define a UI direction, or mentions "brief".
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
This skill creates a design brief through structured conversation. You may skip steps if they are not necessary.
|
|
7
|
+
|
|
8
|
+
## Example prompts
|
|
9
|
+
|
|
10
|
+
- "Write a brief for the onboarding flow"
|
|
11
|
+
- "I need to plan a settings page before I start building"
|
|
12
|
+
- "Help me define the direction for a marketing landing page"
|
|
13
|
+
- "Brief this: a dashboard that shows project health metrics"
|
|
14
|
+
|
|
15
|
+
## Process
|
|
16
|
+
|
|
17
|
+
1. Ask the user for a detailed description of what they want to build, who it is for, and any constraints or ideas they already have.
|
|
18
|
+
|
|
19
|
+
2. Explore the existing codebase to understand the current state. Scan for each of the following specifically:
|
|
20
|
+
- **CSS variables / tokens**: files named `tokens.css`, `variables.css`, `theme.css`, or `:root` declarations with custom properties
|
|
21
|
+
- **Tailwind config**: `tailwind.config.js` or `tailwind.config.ts`, check `theme.extend` for custom values
|
|
22
|
+
- **UI framework themes**: Material UI `createTheme`, Chakra `extendTheme`, shadcn `globals.css` and `components.json`
|
|
23
|
+
- **Component directories**: `components/`, `ui/`, `shared/`, or any folder containing reusable UI pieces
|
|
24
|
+
- **Storybook**: `.storybook/` directory or `*.stories.*` files indicating a documented component library
|
|
25
|
+
- **Design token files**: JSON token files (Style Dictionary format, Figma token exports)
|
|
26
|
+
- **Package.json UI dependencies**: tailwindcss, @mui/material, @chakra-ui/react, @radix-ui, lucide-react, framer-motion, etc.
|
|
27
|
+
- **Font loading**: Google Fonts links in HTML, `@font-face` declarations, font imports in CSS/config
|
|
28
|
+
- **Existing pages/layouts**: route files, layout components, page templates that show established patterns
|
|
29
|
+
- If components exist, treat them as the starting vocabulary. The brief should extend, not replace.
|
|
30
|
+
|
|
31
|
+
3. Interview the user relentlessly about every aspect of the design until you reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one by one. For each question, provide your recommended answer.
|
|
32
|
+
|
|
33
|
+
Cover at minimum:
|
|
34
|
+
- Who is the primary user their JTBD and what are they trying to accomplish?
|
|
35
|
+
- What does success look like for this interface?
|
|
36
|
+
- What is the emotional tone? (calm, urgent, playful, authoritative, warm, clinical)
|
|
37
|
+
- What existing products, sites, or styles should this feel like? What should it NOT feel like?
|
|
38
|
+
- What are the hard constraints? (devices, accessibility requirements, performance budgets, brand guidelines)
|
|
39
|
+
- What content will this interface contain? What is placeholder vs. real?
|
|
40
|
+
|
|
41
|
+
4. Once you have a complete understanding, write the brief using the template below.
|
|
42
|
+
|
|
43
|
+
## File Output
|
|
44
|
+
|
|
45
|
+
Save the brief to `.design/<feature-slug>/DESIGN_BRIEF.md` where `<feature-slug>` is a short, lowercase, hyphenated name derived from the feature or page being designed (e.g., `onboarding-flow`, `settings-page`, `project-dashboard`).
|
|
46
|
+
|
|
47
|
+
This folder structure ensures that running the design flow multiple times for different features does not overwrite previous work. All subsequent skills (information-architecture, design-tokens, brief-to-tasks, design-review) will read from and write to this same subfolder.
|
|
48
|
+
|
|
49
|
+
Example:
|
|
50
|
+
|
|
51
|
+
```
|
|
52
|
+
.design/
|
|
53
|
+
├── onboarding-flow/
|
|
54
|
+
│ └── DESIGN_BRIEF.md
|
|
55
|
+
└── settings-page/
|
|
56
|
+
└── DESIGN_BRIEF.md
|
|
57
|
+
```
|
|
58
|
+
|
|
59
|
+
## Brief Template
|
|
60
|
+
|
|
61
|
+
```markdown
|
|
62
|
+
# Design Brief: [Feature/Page Name]
|
|
63
|
+
|
|
64
|
+
## Problem
|
|
65
|
+
|
|
66
|
+
What problem is the user facing, described from their perspective. Not technical. Not business metrics. The human friction.
|
|
67
|
+
|
|
68
|
+
## Solution
|
|
69
|
+
|
|
70
|
+
What this interface does to solve that problem, described as an experience, not a feature list.
|
|
71
|
+
|
|
72
|
+
## Experience Principles
|
|
73
|
+
|
|
74
|
+
Three principles maximum that guide every design decision. Each principle should resolve a tension.
|
|
75
|
+
Example: "Progressive disclosure over upfront complexity" or "Confidence over speed."
|
|
76
|
+
|
|
77
|
+
1. [Principle] -- [What this means in practice]
|
|
78
|
+
2. [Principle] -- [What this means in practice]
|
|
79
|
+
3. [Principle] -- [What this means in practice]
|
|
80
|
+
|
|
81
|
+
## Aesthetic Direction
|
|
82
|
+
|
|
83
|
+
- **Philosophy**: [Named philosophy or described vibe. See /frontend-design skill for reference.]
|
|
84
|
+
- **Tone**: [Emotional register]
|
|
85
|
+
- **Reference points**: [Existing products, sites, or styles this should feel like]
|
|
86
|
+
- **Anti-references**: [What this should NOT feel like]
|
|
87
|
+
|
|
88
|
+
## Existing Patterns
|
|
89
|
+
|
|
90
|
+
Components, tokens, and conventions already in the codebase that this design must respect or extend.
|
|
91
|
+
|
|
92
|
+
- Typography: [what is currently used]
|
|
93
|
+
- Colors: [current palette/variables]
|
|
94
|
+
- Spacing: [current scale]
|
|
95
|
+
- Components: [existing components that will be reused or extended]
|
|
96
|
+
|
|
97
|
+
## Component Inventory
|
|
98
|
+
|
|
99
|
+
A list of the UI components this feature requires. For each, note whether it exists already, needs modification, or is new.
|
|
100
|
+
|
|
101
|
+
| Component | Status | Notes |
|
|
102
|
+
| --------- | --------------------- | -------- |
|
|
103
|
+
| [name] | Exists / Modify / New | [detail] |
|
|
104
|
+
|
|
105
|
+
## Key Interactions
|
|
106
|
+
|
|
107
|
+
The critical interaction patterns. Describe what the user does and what the interface does in response. Focus on state changes, transitions, and feedback.
|
|
108
|
+
|
|
109
|
+
## Responsive Behavior
|
|
110
|
+
|
|
111
|
+
How the layout adapts across breakpoints. Note any components that change behavior (not just size) on mobile.
|
|
112
|
+
|
|
113
|
+
## Accessibility Requirements
|
|
114
|
+
|
|
115
|
+
Minimum requirements for this interface. Include contrast ratios, keyboard navigation, screen reader considerations, and focus management.
|
|
116
|
+
|
|
117
|
+
## Out of Scope
|
|
118
|
+
|
|
119
|
+
Things this brief explicitly does not cover. Be specific. This prevents scope creep during build.
|
|
120
|
+
```
|
|
@@ -1,124 +1,124 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: design-flow
|
|
3
|
-
description: Run the full design-to-build workflow as a guided sequence. Orchestrates all designer skills in order, from grilling through review. Use when user wants to go through the complete design process, start a project from scratch, run the full flow, or mentions "design flow" or "full workflow".
|
|
4
|
-
---
|
|
5
|
-
|
|
6
|
-
This skill orchestrates the full designer workflow by running each skill in sequence. You are a guide walking the designer through each phase. Do not rush. Each phase must be completed and confirmed before moving to the next.
|
|
7
|
-
|
|
8
|
-
## Example prompts
|
|
9
|
-
|
|
10
|
-
- "Run the full design flow"
|
|
11
|
-
- "Walk me through the complete process for a new project"
|
|
12
|
-
- "Start from scratch and take me through everything"
|
|
13
|
-
- "Design flow for a dashboard app"
|
|
14
|
-
|
|
15
|
-
## The Sequence
|
|
16
|
-
|
|
17
|
-
```
|
|
18
|
-
1. Grill Me → Clarify thinking
|
|
19
|
-
2. Design Brief → Document intent
|
|
20
|
-
3. Info Architecture → Define structure
|
|
21
|
-
4. Design Tokens → Establish visual system
|
|
22
|
-
5. Brief to Tasks → Plan the build
|
|
23
|
-
6. Frontend Design → Build it
|
|
24
|
-
—
|
|
25
|
-
7. Design Review → Run separately when ready
|
|
26
|
-
```
|
|
27
|
-
|
|
28
|
-
## Rules
|
|
29
|
-
|
|
30
|
-
1. **At the start**, tell the designer what the full sequence looks like (phases 1-6, with review available separately) and ask if they want to skip any phases. Common skip patterns:
|
|
31
|
-
- Already have a clear idea → skip grill-me
|
|
32
|
-
- Single component, not a full page → skip information-architecture
|
|
33
|
-
- Existing project with tokens → skip design-tokens
|
|
34
|
-
|
|
35
|
-
2. **Before each phase**, announce which phase you are entering and what it will produce. Example: "Phase 2: Design Brief. I'll interview you about the project and produce a DESIGN_BRIEF.md file. Ready?"
|
|
36
|
-
|
|
37
|
-
3. **During each phase**, read the corresponding SKILL.md file and follow its full instructions. Do not summarize or abbreviate the skill. Run it properly.
|
|
38
|
-
|
|
39
|
-
4. **After each phase**, summarize what was produced (the file name, the key decisions, any open questions) and ask: "Ready to move to the next phase?" Wait for confirmation.
|
|
40
|
-
|
|
41
|
-
5. **Between phases**, check if the output from the previous phase changes anything about the next phase. For example, if the brief names a philosophy, mention that the tokens phase will use it.
|
|
42
|
-
|
|
43
|
-
6. **The designer can stop at any point.** If they say "that's enough for now," summarize where they are in the sequence and what the next phase would be when they return.
|
|
44
|
-
|
|
45
|
-
## Phase Details
|
|
46
|
-
|
|
47
|
-
### Phase 1: Grill Me
|
|
48
|
-
|
|
49
|
-
Read the `grill-me` skill (grill-me/SKILL.md) and follow its instructions.
|
|
50
|
-
**Produces**: Shared understanding of the project. No file output.
|
|
51
|
-
**Transition**: "We've resolved the key decisions. Ready to capture this as a design brief?"
|
|
52
|
-
|
|
53
|
-
### Phase 2: Design Brief
|
|
54
|
-
|
|
55
|
-
Read the `design-brief` skill (design-brief/SKILL.md) and follow its instructions.
|
|
56
|
-
**Produces**: `.design/<feature-slug>/DESIGN_BRIEF.md`.
|
|
57
|
-
**Transition**: "The brief is saved. Next is information architecture, where we'll define the page structure and navigation. Skip this if you're building a single component. Continue?"
|
|
58
|
-
|
|
59
|
-
### Phase 3: Information Architecture
|
|
60
|
-
|
|
61
|
-
Read the `information-architecture` skill (information-architecture/SKILL.md) and follow its instructions.
|
|
62
|
-
**Produces**: `.design/<feature-slug>/INFORMATION_ARCHITECTURE.md`.
|
|
63
|
-
**Transition**: "IA is defined. Next we'll generate design tokens (colors, spacing, typography) based on the philosophy from the brief. Continue?"
|
|
64
|
-
|
|
65
|
-
### Phase 4: Design Tokens
|
|
66
|
-
|
|
67
|
-
Read the `design-tokens` skill (design-tokens/SKILL.md) and follow its instructions.
|
|
68
|
-
**Produces**: Token file (CSS variables, Tailwind config, or theme file depending on stack).
|
|
69
|
-
**Transition**: "Tokens are set. Next I'll break the brief into a task list so we can build in order. Continue?"
|
|
70
|
-
|
|
71
|
-
### Phase 5: Brief to Tasks
|
|
72
|
-
|
|
73
|
-
Read the `brief-to-tasks` skill (brief-to-tasks/SKILL.md) and follow its instructions.
|
|
74
|
-
**Produces**: `.design/<feature-slug>/TASKS.md`.
|
|
75
|
-
**Transition**: "Tasks are ready. Now we build. I'll start with the first task on the list. Continue?"
|
|
76
|
-
|
|
77
|
-
### Phase 6: Frontend Design
|
|
78
|
-
|
|
79
|
-
Read the `frontend-design` skill (frontend-design/SKILL.md) and follow its instructions.
|
|
80
|
-
Work through the tasks from `TASKS.md` in order. After completing each task, check it off and confirm with the designer before moving to the next task.
|
|
81
|
-
**Produces**: Built components and pages.
|
|
82
|
-
**Transition**: "The flow is complete. Your brief, IA, tokens, and tasks are all saved in the project. When you're ready for a design review, run `/design-review` and I'll critique the build against the brief."
|
|
83
|
-
|
|
84
|
-
**The flow ends here.** Phase 7 is not automatic.
|
|
85
|
-
|
|
86
|
-
### Phase 7: Design Review (on request only)
|
|
87
|
-
|
|
88
|
-
This phase does NOT run automatically. It only runs if:
|
|
89
|
-
|
|
90
|
-
- The designer explicitly asks for a review during the flow
|
|
91
|
-
- The designer runs `/design-review` separately after building
|
|
92
|
-
|
|
93
|
-
The review requires built code to examine. If no components or pages have been built yet, do not run this phase. Instead, remind the designer: "Run `/design-review` once you have something built. It will check the output against the brief."
|
|
94
|
-
|
|
95
|
-
When triggered, read the `design-review` skill (design-review/SKILL.md) and follow its instructions. The review will capture screenshots of the running application using Playwright MCP (preferred), the Cursor IDE Browser (fallback), or by asking the user to provide them manually if no browser tool is available.
|
|
96
|
-
|
|
97
|
-
**Produces**: `.design/<feature-slug>/DESIGN_REVIEW.md` + screenshots saved in `.design/<feature-slug>/screenshots/`.
|
|
98
|
-
**Transition**: "Review is done. Screenshots are saved in `.design/<feature-slug>/screenshots/`. If there are must-fix items, I can address them now."
|
|
99
|
-
|
|
100
|
-
## Project Files Structure
|
|
101
|
-
|
|
102
|
-
All design flow artifacts are saved under `.design/<feature-slug>/` where `<feature-slug>` is a short, lowercase, hyphenated name derived from the feature being designed. This ensures multiple features can be designed independently without overwriting each other.
|
|
103
|
-
|
|
104
|
-
```
|
|
105
|
-
.design/
|
|
106
|
-
└── <feature-slug>/
|
|
107
|
-
├── DESIGN_BRIEF.md ← Phase 2: Project intent, goals, aesthetic direction
|
|
108
|
-
├── INFORMATION_ARCHITECTURE.md ← Phase 3: Navigation, page structure, user flows
|
|
109
|
-
├── DESIGN_TOKENS.* ← Phase 4: Colors, spacing, typography, shadows (CSS/Tailwind/theme)
|
|
110
|
-
├── TASKS.md ← Phase 5: Ordered build checklist from the brief
|
|
111
|
-
├── DESIGN_REVIEW.md ← Phase 7: Prioritized critique against the brief
|
|
112
|
-
└── screenshots/ ← Phase 7: Visual evidence from the running app
|
|
113
|
-
├── review-[page]-desktop-1280.png
|
|
114
|
-
├── review-[page]-tablet-768.png
|
|
115
|
-
├── review-[page]-mobile-375.png
|
|
116
|
-
├── review-[page]-dark-mode-*.png
|
|
117
|
-
└── review-[component]-[state].png
|
|
118
|
-
```
|
|
119
|
-
|
|
120
|
-
The `screenshots/` subfolder is created during the design review phase. All visual evidence of the review (responsive breakpoints, interactive states, dark mode) is saved here with descriptive filenames so findings in `DESIGN_REVIEW.md` are traceable.
|
|
121
|
-
|
|
122
|
-
## If the Designer Returns Mid-Flow
|
|
123
|
-
|
|
124
|
-
Check the `.design/` folder for existing feature subfolders. If files from earlier phases exist (DESIGN_BRIEF.md, INFORMATION_ARCHITECTURE.md, TASKS.md) inside a feature folder, read them to understand where the designer left off. Ask which feature to resume if multiple folders exist. Resume from the next incomplete phase.
|
|
1
|
+
---
|
|
2
|
+
name: design-flow
|
|
3
|
+
description: Run the full design-to-build workflow as a guided sequence. Orchestrates all designer skills in order, from grilling through review. Use when user wants to go through the complete design process, start a project from scratch, run the full flow, or mentions "design flow" or "full workflow".
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
This skill orchestrates the full designer workflow by running each skill in sequence. You are a guide walking the designer through each phase. Do not rush. Each phase must be completed and confirmed before moving to the next.
|
|
7
|
+
|
|
8
|
+
## Example prompts
|
|
9
|
+
|
|
10
|
+
- "Run the full design flow"
|
|
11
|
+
- "Walk me through the complete process for a new project"
|
|
12
|
+
- "Start from scratch and take me through everything"
|
|
13
|
+
- "Design flow for a dashboard app"
|
|
14
|
+
|
|
15
|
+
## The Sequence
|
|
16
|
+
|
|
17
|
+
```
|
|
18
|
+
1. Grill Me → Clarify thinking
|
|
19
|
+
2. Design Brief → Document intent
|
|
20
|
+
3. Info Architecture → Define structure
|
|
21
|
+
4. Design Tokens → Establish visual system
|
|
22
|
+
5. Brief to Tasks → Plan the build
|
|
23
|
+
6. Frontend Design → Build it
|
|
24
|
+
—
|
|
25
|
+
7. Design Review → Run separately when ready
|
|
26
|
+
```
|
|
27
|
+
|
|
28
|
+
## Rules
|
|
29
|
+
|
|
30
|
+
1. **At the start**, tell the designer what the full sequence looks like (phases 1-6, with review available separately) and ask if they want to skip any phases. Common skip patterns:
|
|
31
|
+
- Already have a clear idea → skip grill-me
|
|
32
|
+
- Single component, not a full page → skip information-architecture
|
|
33
|
+
- Existing project with tokens → skip design-tokens
|
|
34
|
+
|
|
35
|
+
2. **Before each phase**, announce which phase you are entering and what it will produce. Example: "Phase 2: Design Brief. I'll interview you about the project and produce a DESIGN_BRIEF.md file. Ready?"
|
|
36
|
+
|
|
37
|
+
3. **During each phase**, read the corresponding SKILL.md file and follow its full instructions. Do not summarize or abbreviate the skill. Run it properly.
|
|
38
|
+
|
|
39
|
+
4. **After each phase**, summarize what was produced (the file name, the key decisions, any open questions) and ask: "Ready to move to the next phase?" Wait for confirmation.
|
|
40
|
+
|
|
41
|
+
5. **Between phases**, check if the output from the previous phase changes anything about the next phase. For example, if the brief names a philosophy, mention that the tokens phase will use it.
|
|
42
|
+
|
|
43
|
+
6. **The designer can stop at any point.** If they say "that's enough for now," summarize where they are in the sequence and what the next phase would be when they return.
|
|
44
|
+
|
|
45
|
+
## Phase Details
|
|
46
|
+
|
|
47
|
+
### Phase 1: Grill Me
|
|
48
|
+
|
|
49
|
+
Read the `grill-me` skill (grill-me/SKILL.md) and follow its instructions.
|
|
50
|
+
**Produces**: Shared understanding of the project. No file output.
|
|
51
|
+
**Transition**: "We've resolved the key decisions. Ready to capture this as a design brief?"
|
|
52
|
+
|
|
53
|
+
### Phase 2: Design Brief
|
|
54
|
+
|
|
55
|
+
Read the `design-brief` skill (design-brief/SKILL.md) and follow its instructions.
|
|
56
|
+
**Produces**: `.design/<feature-slug>/DESIGN_BRIEF.md`.
|
|
57
|
+
**Transition**: "The brief is saved. Next is information architecture, where we'll define the page structure and navigation. Skip this if you're building a single component. Continue?"
|
|
58
|
+
|
|
59
|
+
### Phase 3: Information Architecture
|
|
60
|
+
|
|
61
|
+
Read the `information-architecture` skill (information-architecture/SKILL.md) and follow its instructions.
|
|
62
|
+
**Produces**: `.design/<feature-slug>/INFORMATION_ARCHITECTURE.md`.
|
|
63
|
+
**Transition**: "IA is defined. Next we'll generate design tokens (colors, spacing, typography) based on the philosophy from the brief. Continue?"
|
|
64
|
+
|
|
65
|
+
### Phase 4: Design Tokens
|
|
66
|
+
|
|
67
|
+
Read the `design-tokens` skill (design-tokens/SKILL.md) and follow its instructions.
|
|
68
|
+
**Produces**: Token file (CSS variables, Tailwind config, or theme file depending on stack).
|
|
69
|
+
**Transition**: "Tokens are set. Next I'll break the brief into a task list so we can build in order. Continue?"
|
|
70
|
+
|
|
71
|
+
### Phase 5: Brief to Tasks
|
|
72
|
+
|
|
73
|
+
Read the `brief-to-tasks` skill (brief-to-tasks/SKILL.md) and follow its instructions.
|
|
74
|
+
**Produces**: `.design/<feature-slug>/TASKS.md`.
|
|
75
|
+
**Transition**: "Tasks are ready. Now we build. I'll start with the first task on the list. Continue?"
|
|
76
|
+
|
|
77
|
+
### Phase 6: Frontend Design
|
|
78
|
+
|
|
79
|
+
Read the `frontend-design` skill (frontend-design/SKILL.md) and follow its instructions.
|
|
80
|
+
Work through the tasks from `TASKS.md` in order. After completing each task, check it off and confirm with the designer before moving to the next task.
|
|
81
|
+
**Produces**: Built components and pages.
|
|
82
|
+
**Transition**: "The flow is complete. Your brief, IA, tokens, and tasks are all saved in the project. When you're ready for a design review, run `/design-review` and I'll critique the build against the brief."
|
|
83
|
+
|
|
84
|
+
**The flow ends here.** Phase 7 is not automatic.
|
|
85
|
+
|
|
86
|
+
### Phase 7: Design Review (on request only)
|
|
87
|
+
|
|
88
|
+
This phase does NOT run automatically. It only runs if:
|
|
89
|
+
|
|
90
|
+
- The designer explicitly asks for a review during the flow
|
|
91
|
+
- The designer runs `/design-review` separately after building
|
|
92
|
+
|
|
93
|
+
The review requires built code to examine. If no components or pages have been built yet, do not run this phase. Instead, remind the designer: "Run `/design-review` once you have something built. It will check the output against the brief."
|
|
94
|
+
|
|
95
|
+
When triggered, read the `design-review` skill (design-review/SKILL.md) and follow its instructions. The review will capture screenshots of the running application using Playwright MCP (preferred), the Cursor IDE Browser (fallback), or by asking the user to provide them manually if no browser tool is available.
|
|
96
|
+
|
|
97
|
+
**Produces**: `.design/<feature-slug>/DESIGN_REVIEW.md` + screenshots saved in `.design/<feature-slug>/screenshots/`.
|
|
98
|
+
**Transition**: "Review is done. Screenshots are saved in `.design/<feature-slug>/screenshots/`. If there are must-fix items, I can address them now."
|
|
99
|
+
|
|
100
|
+
## Project Files Structure
|
|
101
|
+
|
|
102
|
+
All design flow artifacts are saved under `.design/<feature-slug>/` where `<feature-slug>` is a short, lowercase, hyphenated name derived from the feature being designed. This ensures multiple features can be designed independently without overwriting each other.
|
|
103
|
+
|
|
104
|
+
```
|
|
105
|
+
.design/
|
|
106
|
+
└── <feature-slug>/
|
|
107
|
+
├── DESIGN_BRIEF.md ← Phase 2: Project intent, goals, aesthetic direction
|
|
108
|
+
├── INFORMATION_ARCHITECTURE.md ← Phase 3: Navigation, page structure, user flows
|
|
109
|
+
├── DESIGN_TOKENS.* ← Phase 4: Colors, spacing, typography, shadows (CSS/Tailwind/theme)
|
|
110
|
+
├── TASKS.md ← Phase 5: Ordered build checklist from the brief
|
|
111
|
+
├── DESIGN_REVIEW.md ← Phase 7: Prioritized critique against the brief
|
|
112
|
+
└── screenshots/ ← Phase 7: Visual evidence from the running app
|
|
113
|
+
├── review-[page]-desktop-1280.png
|
|
114
|
+
├── review-[page]-tablet-768.png
|
|
115
|
+
├── review-[page]-mobile-375.png
|
|
116
|
+
├── review-[page]-dark-mode-*.png
|
|
117
|
+
└── review-[component]-[state].png
|
|
118
|
+
```
|
|
119
|
+
|
|
120
|
+
The `screenshots/` subfolder is created during the design review phase. All visual evidence of the review (responsive breakpoints, interactive states, dark mode) is saved here with descriptive filenames so findings in `DESIGN_REVIEW.md` are traceable.
|
|
121
|
+
|
|
122
|
+
## If the Designer Returns Mid-Flow
|
|
123
|
+
|
|
124
|
+
Check the `.design/` folder for existing feature subfolders. If files from earlier phases exist (DESIGN_BRIEF.md, INFORMATION_ARCHITECTURE.md, TASKS.md) inside a feature folder, read them to understand where the designer left off. Ask which feature to resume if multiple folders exist. Resume from the next incomplete phase.
|