opsfuse-ui 0.1.0
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/settings.local.json +8 -0
- package/.claude/skills/brief-to-tasks/SKILL.md +74 -0
- package/.claude/skills/design-brief/SKILL.md +120 -0
- package/.claude/skills/design-flow/SKILL.md +124 -0
- package/.claude/skills/design-review/SKILL.md +249 -0
- package/.claude/skills/design-tokens/SKILL.md +198 -0
- package/.claude/skills/frontend-design/SKILL.md +144 -0
- package/.claude/skills/grill-me/SKILL.md +21 -0
- package/.claude/skills/information-architecture/SKILL.md +111 -0
- package/.claude/skills/opsfuse-color-theme/SKILL.md +251 -0
- package/.claude/skills/opsfuse-components/SKILL.md +1439 -0
- package/.claude/skills/opsfuse-setup/SKILL.md +548 -0
- package/.claude/skills/opsfuse-ui-consistency/SKILL.md +160 -0
- package/README.md +356 -0
- package/dist/chunk-BdsCSvBP.js +20 -0
- package/dist/clsx-D7D_XZ_-.js +16 -0
- package/dist/components/logo/LogoMaker.d.ts +43 -0
- package/dist/components/logo/LogoMaker.d.ts.map +1 -0
- package/dist/components/logo/RecruitSmartly.d.ts +4 -0
- package/dist/components/logo/RecruitSmartly.d.ts.map +1 -0
- package/dist/components/logo/SkillReady.d.ts +4 -0
- package/dist/components/logo/SkillReady.d.ts.map +1 -0
- package/dist/components/logo/TalentScan.d.ts +4 -0
- package/dist/components/logo/TalentScan.d.ts.map +1 -0
- package/dist/components/logo/Verity.d.ts +4 -0
- package/dist/components/logo/Verity.d.ts.map +1 -0
- package/dist/components/logo/WorkLog.d.ts +4 -0
- package/dist/components/logo/WorkLog.d.ts.map +1 -0
- package/dist/components/opsfuse-root.d.ts +7 -0
- package/dist/components/opsfuse-root.d.ts.map +1 -0
- package/dist/components/opsfuse-theme-provider.d.ts +15 -0
- package/dist/components/opsfuse-theme-provider.d.ts.map +1 -0
- package/dist/components/ui/Header.d.ts +17 -0
- package/dist/components/ui/Header.d.ts.map +1 -0
- package/dist/components/ui/accordion.d.ts +20 -0
- package/dist/components/ui/accordion.d.ts.map +1 -0
- package/dist/components/ui/alert-dialog.d.ts +15 -0
- package/dist/components/ui/alert-dialog.d.ts.map +1 -0
- package/dist/components/ui/alert.d.ts +26 -0
- package/dist/components/ui/alert.d.ts.map +1 -0
- package/dist/components/ui/aspect-ratio.d.ts +4 -0
- package/dist/components/ui/aspect-ratio.d.ts.map +1 -0
- package/dist/components/ui/autocomplete.d.ts +24 -0
- package/dist/components/ui/autocomplete.d.ts.map +1 -0
- package/dist/components/ui/avatar.d.ts +9 -0
- package/dist/components/ui/avatar.d.ts.map +1 -0
- package/dist/components/ui/badge.d.ts +10 -0
- package/dist/components/ui/badge.d.ts.map +1 -0
- package/dist/components/ui/breadcrumb.d.ts +12 -0
- package/dist/components/ui/breadcrumb.d.ts.map +1 -0
- package/dist/components/ui/button-group.d.ts +12 -0
- package/dist/components/ui/button-group.d.ts.map +1 -0
- package/dist/components/ui/button.d.ts +14 -0
- package/dist/components/ui/button.d.ts.map +1 -0
- package/dist/components/ui/calendar.d.ts +11 -0
- package/dist/components/ui/calendar.d.ts.map +1 -0
- package/dist/components/ui/card.d.ts +14 -0
- package/dist/components/ui/card.d.ts.map +1 -0
- package/dist/components/ui/carousel.d.ts +29 -0
- package/dist/components/ui/carousel.d.ts.map +1 -0
- package/dist/components/ui/chart.d.ts +45 -0
- package/dist/components/ui/chart.d.ts.map +1 -0
- package/dist/components/ui/checkbox.d.ts +10 -0
- package/dist/components/ui/checkbox.d.ts.map +1 -0
- package/dist/components/ui/collapsible.d.ts +6 -0
- package/dist/components/ui/collapsible.d.ts.map +1 -0
- package/dist/components/ui/combobox.d.ts +40 -0
- package/dist/components/ui/combobox.d.ts.map +1 -0
- package/dist/components/ui/command.d.ts +19 -0
- package/dist/components/ui/command.d.ts.map +1 -0
- package/dist/components/ui/context-menu.d.ts +32 -0
- package/dist/components/ui/context-menu.d.ts.map +1 -0
- package/dist/components/ui/dialog.d.ts +30 -0
- package/dist/components/ui/dialog.d.ts.map +1 -0
- package/dist/components/ui/direction.d.ts +8 -0
- package/dist/components/ui/direction.d.ts.map +1 -0
- package/dist/components/ui/drawer.d.ts +14 -0
- package/dist/components/ui/drawer.d.ts.map +1 -0
- package/dist/components/ui/dropdown-menu.d.ts +30 -0
- package/dist/components/ui/dropdown-menu.d.ts.map +1 -0
- package/dist/components/ui/empty.d.ts +12 -0
- package/dist/components/ui/empty.d.ts.map +1 -0
- package/dist/components/ui/field.d.ts +25 -0
- package/dist/components/ui/field.d.ts.map +1 -0
- package/dist/components/ui/form.d.ts +27 -0
- package/dist/components/ui/form.d.ts.map +1 -0
- package/dist/components/ui/hover-card.d.ts +7 -0
- package/dist/components/ui/hover-card.d.ts.map +1 -0
- package/dist/components/ui/input-group.d.ts +18 -0
- package/dist/components/ui/input-group.d.ts.map +1 -0
- package/dist/components/ui/input-otp.d.ts +12 -0
- package/dist/components/ui/input-otp.d.ts.map +1 -0
- package/dist/components/ui/input.d.ts +12 -0
- package/dist/components/ui/input.d.ts.map +1 -0
- package/dist/components/ui/item.d.ts +24 -0
- package/dist/components/ui/item.d.ts.map +1 -0
- package/dist/components/ui/kbd.d.ts +4 -0
- package/dist/components/ui/kbd.d.ts.map +1 -0
- package/dist/components/ui/label.d.ts +5 -0
- package/dist/components/ui/label.d.ts.map +1 -0
- package/dist/components/ui/menubar.d.ts +31 -0
- package/dist/components/ui/menubar.d.ts.map +1 -0
- package/dist/components/ui/navigation-menu.d.ts +15 -0
- package/dist/components/ui/navigation-menu.d.ts.map +1 -0
- package/dist/components/ui/pagination.d.ts +15 -0
- package/dist/components/ui/pagination.d.ts.map +1 -0
- package/dist/components/ui/popover.d.ts +11 -0
- package/dist/components/ui/popover.d.ts.map +1 -0
- package/dist/components/ui/progress.d.ts +19 -0
- package/dist/components/ui/progress.d.ts.map +1 -0
- package/dist/components/ui/radio-group.d.ts +11 -0
- package/dist/components/ui/radio-group.d.ts.map +1 -0
- package/dist/components/ui/resizable.d.ts +8 -0
- package/dist/components/ui/resizable.d.ts.map +1 -0
- package/dist/components/ui/scroll-area.d.ts +6 -0
- package/dist/components/ui/scroll-area.d.ts.map +1 -0
- package/dist/components/ui/select.d.ts +27 -0
- package/dist/components/ui/select.d.ts.map +1 -0
- package/dist/components/ui/separator.d.ts +5 -0
- package/dist/components/ui/separator.d.ts.map +1 -0
- package/dist/components/ui/shadcn/shadcn-accordion.d.ts +8 -0
- package/dist/components/ui/shadcn/shadcn-accordion.d.ts.map +1 -0
- package/dist/components/ui/shadcn/shadcn-alert-dialog.d.ts +19 -0
- package/dist/components/ui/shadcn/shadcn-alert-dialog.d.ts.map +1 -0
- package/dist/components/ui/shadcn/shadcn-avatar.d.ts +12 -0
- package/dist/components/ui/shadcn/shadcn-avatar.d.ts.map +1 -0
- package/dist/components/ui/shadcn/shadcn-combobox.d.ts +33 -0
- package/dist/components/ui/shadcn/shadcn-combobox.d.ts.map +1 -0
- package/dist/components/ui/shadcn/shadcn-dropdown-menu.d.ts +30 -0
- package/dist/components/ui/shadcn/shadcn-dropdown-menu.d.ts.map +1 -0
- package/dist/components/ui/shadcn/shadcn-empty.d.ts +12 -0
- package/dist/components/ui/shadcn/shadcn-empty.d.ts.map +1 -0
- package/dist/components/ui/shadcn/shadcn-pagination.d.ts +18 -0
- package/dist/components/ui/shadcn/shadcn-pagination.d.ts.map +1 -0
- package/dist/components/ui/shadcn/shadcn-select.d.ts +24 -0
- package/dist/components/ui/shadcn/shadcn-select.d.ts.map +1 -0
- package/dist/components/ui/shadcn/shadcn-tabs.d.ts +12 -0
- package/dist/components/ui/shadcn/shadcn-tabs.d.ts.map +1 -0
- package/dist/components/ui/shadcn/shadcn-tooltip.d.ts +11 -0
- package/dist/components/ui/shadcn/shadcn-tooltip.d.ts.map +1 -0
- package/dist/components/ui/sheet.d.ts +28 -0
- package/dist/components/ui/sheet.d.ts.map +1 -0
- package/dist/components/ui/sidebar.d.ts +70 -0
- package/dist/components/ui/sidebar.d.ts.map +1 -0
- package/dist/components/ui/skeleton.d.ts +3 -0
- package/dist/components/ui/skeleton.d.ts.map +1 -0
- package/dist/components/ui/slider.d.ts +22 -0
- package/dist/components/ui/slider.d.ts.map +1 -0
- package/dist/components/ui/sonner.d.ts +5 -0
- package/dist/components/ui/sonner.d.ts.map +1 -0
- package/dist/components/ui/spinner.d.ts +3 -0
- package/dist/components/ui/spinner.d.ts.map +1 -0
- package/dist/components/ui/switch.d.ts +12 -0
- package/dist/components/ui/switch.d.ts.map +1 -0
- package/dist/components/ui/table.d.ts +11 -0
- package/dist/components/ui/table.d.ts.map +1 -0
- package/dist/components/ui/tabs.d.ts +22 -0
- package/dist/components/ui/tabs.d.ts.map +1 -0
- package/dist/components/ui/textarea.d.ts +9 -0
- package/dist/components/ui/textarea.d.ts.map +1 -0
- package/dist/components/ui/toggle-group.d.ts +11 -0
- package/dist/components/ui/toggle-group.d.ts.map +1 -0
- package/dist/components/ui/toggle.d.ts +10 -0
- package/dist/components/ui/toggle.d.ts.map +1 -0
- package/dist/components/ui/tooltip.d.ts +15 -0
- package/dist/components/ui/tooltip.d.ts.map +1 -0
- package/dist/core.d.ts +2 -0
- package/dist/core.d.ts.map +1 -0
- package/dist/core.js +3 -0
- package/dist/es6-D-3xKXBT.js +24045 -0
- package/dist/extended.d.ts +2 -0
- package/dist/extended.d.ts.map +1 -0
- package/dist/extended.js +3 -0
- package/dist/hooks/use-mobile.d.ts +2 -0
- package/dist/hooks/use-mobile.d.ts.map +1 -0
- package/dist/icons.d.ts +2 -0
- package/dist/icons.d.ts.map +1 -0
- package/dist/icons.js +2 -0
- package/dist/index.d.ts +2 -0
- package/dist/index.d.ts.map +1 -0
- package/dist/index.js +2194 -0
- package/dist/input-group-DIfVGMYe.js +5196 -0
- package/dist/input-otp-DwLGFwVo.js +11879 -0
- package/dist/lib/brand-theme.d.ts +4 -0
- package/dist/lib/brand-theme.d.ts.map +1 -0
- package/dist/lib/document-dark-mode.d.ts +8 -0
- package/dist/lib/document-dark-mode.d.ts.map +1 -0
- package/dist/lib/opsfuse-portal-theme.d.ts +21 -0
- package/dist/lib/opsfuse-portal-theme.d.ts.map +1 -0
- package/dist/lib/theme-scope.d.ts +3 -0
- package/dist/lib/theme-scope.d.ts.map +1 -0
- package/dist/lib/utils.d.ts +3 -0
- package/dist/lib/utils.d.ts.map +1 -0
- package/dist/lucide-react-DLVJK_zM.js +38405 -0
- package/dist/public-api-core.d.ts +61 -0
- package/dist/public-api-core.d.ts.map +1 -0
- package/dist/public-api-extended.d.ts +9 -0
- package/dist/public-api-extended.d.ts.map +1 -0
- package/dist/public-api.d.ts +73 -0
- package/dist/public-api.d.ts.map +1 -0
- package/dist/recharts.d.ts +2 -0
- package/dist/recharts.d.ts.map +1 -0
- package/dist/recharts.js +2 -0
- package/dist/style.css +3 -0
- package/dist/style.layered.css +3 -0
- package/dist/toggle-group-D21Ul2kd.js +10171 -0
- package/package.json +113 -0
- package/scripts/postinstall.mjs +67 -0
- package/scripts/unwrap-css-layers.mjs +36 -0
|
@@ -0,0 +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.
|
|
@@ -0,0 +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
|
+
```
|
|
@@ -0,0 +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.
|
|
@@ -0,0 +1,249 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: design-review
|
|
3
|
+
description: Run a structured design critique against the brief and codebase. Checks visual hierarchy, consistency, responsiveness, accessibility, and aesthetic fidelity. Use when user wants a design review, critique, QA pass, polish pass, or mentions "review" after building.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
This skill runs a structured design review of what has been built, measured against the design brief and the chosen aesthetic philosophy.
|
|
7
|
+
|
|
8
|
+
> **CRITICAL — Visual Screenshot Capture**
|
|
9
|
+
>
|
|
10
|
+
> You MUST capture screenshots of the running application as part of every design review. Code review alone is insufficient — you need to see what the user sees. Follow the screenshot capture protocol in Step 3 below. This is not optional.
|
|
11
|
+
|
|
12
|
+
## Example prompts
|
|
13
|
+
|
|
14
|
+
- "Review what I just built"
|
|
15
|
+
- "Run a design critique on the landing page"
|
|
16
|
+
- "Check this against the brief"
|
|
17
|
+
- "Here's a screenshot. How does it look?" [paste screenshot]
|
|
18
|
+
- "QA pass before I ship this"
|
|
19
|
+
|
|
20
|
+
## Process
|
|
21
|
+
|
|
22
|
+
1. **Read the brief.** Look for the active feature's brief at `.design/<feature-slug>/DESIGN_BRIEF.md`. If multiple feature folders exist under `.design/`, ask the user which feature to review. If no `.design/` folder exists, fall back to `DESIGN_BRIEF.md` in the project root. If neither exists, ask the user what the intended design direction was.
|
|
23
|
+
|
|
24
|
+
2. **Explore the built code.** Examine every component, page, and style file that was created or modified. Scan specifically for:
|
|
25
|
+
- All new or modified components and their relationship to pre-existing components
|
|
26
|
+
- Token/variable usage: are components using shared tokens or hardcoding values?
|
|
27
|
+
- Duplicate components that should be consolidated
|
|
28
|
+
- File naming and organization: do new files follow the project's conventions?
|
|
29
|
+
- Understand what was actually built, not what was planned.
|
|
30
|
+
|
|
31
|
+
3. **Capture screenshots of the running application.**
|
|
32
|
+
|
|
33
|
+
This step is **mandatory**. Do not skip it. Do not rely only on user-provided screenshots.
|
|
34
|
+
|
|
35
|
+
### Screenshot Tool Priority
|
|
36
|
+
|
|
37
|
+
Try each option in order. Use the first one that is available:
|
|
38
|
+
1. **Playwright MCP (preferred).** Check if the `plugin-playwright-playwright` MCP server is available. If it is, use it — it gives you precise control over viewport sizing, full-page captures, and file naming.
|
|
39
|
+
2. **Cursor IDE Browser (second choice).** If Playwright MCP is not available, use the `cursor-ide-browser` MCP server's `browser_take_screenshot` tool instead. It has the same core capabilities.
|
|
40
|
+
3. **Ask the user (last resort).** If neither MCP server nor in-app browser is available, you MUST ask the user to provide screenshots manually. Be specific about what you need:
|
|
41
|
+
- "I don't have access to a browser tool. To complete the visual review I need screenshots of the running application. Please provide:"
|
|
42
|
+
- A full-page screenshot at **desktop** width (1280px)
|
|
43
|
+
- A full-page screenshot at **tablet** width (768px)
|
|
44
|
+
- A full-page screenshot at **mobile** width (375px)
|
|
45
|
+
- Dark mode variants (if applicable)
|
|
46
|
+
- Any specific component or interactive state you want reviewed
|
|
47
|
+
- Ask the user to paste/attach the images directly in chat, or to save them into the `screenshots/` folder themselves.
|
|
48
|
+
- **Do not skip the visual review.** Wait for the user to provide screenshots before proceeding with the checklist.
|
|
49
|
+
|
|
50
|
+
### Screenshot Save Location
|
|
51
|
+
|
|
52
|
+
All screenshots MUST be saved to a `screenshots/` subfolder inside the feature's `.design/` directory — the same folder where `DESIGN_BRIEF.md` and other design flow files live.
|
|
53
|
+
|
|
54
|
+
Path pattern: `.design/<feature-slug>/screenshots/`
|
|
55
|
+
|
|
56
|
+
If the brief lives at `.design/onboarding-flow/DESIGN_BRIEF.md`, screenshots go to `.design/onboarding-flow/screenshots/`. Create the folder if it does not exist.
|
|
57
|
+
|
|
58
|
+
If no `.design/` folder exists (legacy project or standalone review), fall back to a `screenshots/` folder in the project root.
|
|
59
|
+
|
|
60
|
+
Use descriptive filenames that encode what was captured:
|
|
61
|
+
|
|
62
|
+
```
|
|
63
|
+
.design/
|
|
64
|
+
└── onboarding-flow/
|
|
65
|
+
├── DESIGN_BRIEF.md
|
|
66
|
+
├── DESIGN_REVIEW.md
|
|
67
|
+
└── screenshots/
|
|
68
|
+
├── review-homepage-desktop-1280.png
|
|
69
|
+
├── review-homepage-tablet-768.png
|
|
70
|
+
├── review-homepage-mobile-375.png
|
|
71
|
+
├── review-homepage-dark-mode-desktop-1280.png
|
|
72
|
+
└── review-card-component-hover.png
|
|
73
|
+
```
|
|
74
|
+
|
|
75
|
+
### Screenshot Capture Protocol
|
|
76
|
+
|
|
77
|
+
**a. Navigate to the application.** Ask the user for the URL if not obvious from the project (e.g., `http://localhost:3000`). Use `browser_navigate` to open it.
|
|
78
|
+
|
|
79
|
+
**b. Capture responsive breakpoints.** At minimum, capture these three viewports for every key page/view:
|
|
80
|
+
|
|
81
|
+
| Breakpoint | Width × Height | Filename suffix |
|
|
82
|
+
| ---------- | -------------- | --------------- |
|
|
83
|
+
| Mobile | 375 × 812 | `-mobile-375` |
|
|
84
|
+
| Tablet | 768 × 1024 | `-tablet-768` |
|
|
85
|
+
| Desktop | 1280 × 800 | `-desktop-1280` |
|
|
86
|
+
|
|
87
|
+
Use `browser_resize` to set the viewport before each screenshot. Use `browser_take_screenshot` with `fullPage: true` to capture the entire scrollable page, and save with the `filename` parameter pointing to the `screenshots/` folder.
|
|
88
|
+
|
|
89
|
+
**Playwright MCP example sequence** (assuming feature slug is `onboarding-flow`):
|
|
90
|
+
|
|
91
|
+
```
|
|
92
|
+
1. browser_navigate → { url: "http://localhost:3000" }
|
|
93
|
+
2. browser_resize → { width: 1280, height: 800 }
|
|
94
|
+
3. browser_take_screenshot → { type: "png", filename: ".design/onboarding-flow/screenshots/review-homepage-desktop-1280.png", fullPage: true }
|
|
95
|
+
4. browser_resize → { width: 768, height: 1024 }
|
|
96
|
+
5. browser_take_screenshot → { type: "png", filename: ".design/onboarding-flow/screenshots/review-homepage-tablet-768.png", fullPage: true }
|
|
97
|
+
6. browser_resize → { width: 375, height: 812 }
|
|
98
|
+
7. browser_take_screenshot → { type: "png", filename: ".design/onboarding-flow/screenshots/review-homepage-mobile-375.png", fullPage: true }
|
|
99
|
+
```
|
|
100
|
+
|
|
101
|
+
**c. Capture interactive states (when relevant).**
|
|
102
|
+
- Hover states on buttons, cards, links
|
|
103
|
+
- Focus states on form fields
|
|
104
|
+
- Open states on dropdowns, modals, menus
|
|
105
|
+
- Error/success states on forms
|
|
106
|
+
- Loading and empty states
|
|
107
|
+
|
|
108
|
+
**d. Capture dark mode (if the project supports it).** Toggle dark mode and repeat the responsive breakpoint captures with `-dark-mode` in the filename.
|
|
109
|
+
|
|
110
|
+
**e. Capture specific components.** If the review focuses on a particular component, use the `element` and `ref` parameters to screenshot just that element.
|
|
111
|
+
|
|
112
|
+
### Analyze Every Screenshot
|
|
113
|
+
|
|
114
|
+
After capturing, visually analyze each screenshot against the design brief. For each screenshot:
|
|
115
|
+
- Compare against the brief's aesthetic direction
|
|
116
|
+
- Check visual hierarchy: is the most important element the most prominent?
|
|
117
|
+
- Check spacing consistency: do margins and padding look even and intentional?
|
|
118
|
+
- Check color: does the palette match the brief's direction?
|
|
119
|
+
- Check typography: are font sizes, weights, and spacing visually correct?
|
|
120
|
+
- Check responsive adaptation: does the layout properly reorganize (not just shrink)?
|
|
121
|
+
- Note rendering issues that code review alone would miss (font loading failures, broken images, layout overflow, z-index problems, incorrect border-radius, color mismatches)
|
|
122
|
+
|
|
123
|
+
Reference specific screenshots by filename in the review output so findings are traceable.
|
|
124
|
+
|
|
125
|
+
4. **Run the review checklist below.** For each category, note what passes and what needs refinement. Be specific. Reference exact components, files, line numbers, and screenshot filenames.
|
|
126
|
+
|
|
127
|
+
5. **Produce a prioritized refinement list.** Group issues by severity:
|
|
128
|
+
- **Must fix**: Broken functionality, accessibility failures, major deviations from the brief.
|
|
129
|
+
- **Should fix**: Inconsistencies, missing states, responsive issues.
|
|
130
|
+
- **Could improve**: Polish, animation refinement, typography fine-tuning.
|
|
131
|
+
|
|
132
|
+
6. Save the review as `DESIGN_REVIEW.md` inside the feature's `.design/<feature-slug>/` folder (next to `DESIGN_BRIEF.md`). If no `.design/` folder exists, save to the project root. Include a "Screenshots Captured" section listing all screenshots taken with their paths. Present the review directly as well if the user prefers.
|
|
133
|
+
|
|
134
|
+
## Review Checklist
|
|
135
|
+
|
|
136
|
+
### Visual Hierarchy
|
|
137
|
+
|
|
138
|
+
- Is the most important content the most visually prominent on each page/view?
|
|
139
|
+
- Does the type scale create clear levels of importance (heading, subheading, body, caption)?
|
|
140
|
+
- Do interactive elements (buttons, links, inputs) have enough visual weight to be found without hunting?
|
|
141
|
+
- Is there a clear reading order? Can you trace where the eye goes first, second, third?
|
|
142
|
+
|
|
143
|
+
### Consistency
|
|
144
|
+
|
|
145
|
+
- Are spacing values consistent? Check padding and margins against the established scale (4px/8px base or whatever the project uses).
|
|
146
|
+
- Are colors used consistently? Check that the same semantic meaning always maps to the same color (primary actions, errors, success states, disabled states).
|
|
147
|
+
- Are border radii, shadow values, and font sizes reused from a shared set, or are there one-off values?
|
|
148
|
+
- Do similar components look and behave similarly? (e.g., all cards, all form fields, all buttons within a category.)
|
|
149
|
+
|
|
150
|
+
### Aesthetic Fidelity
|
|
151
|
+
|
|
152
|
+
- Does the implementation match the named philosophy from the brief?
|
|
153
|
+
- Would someone looking at this immediately recognize the intended aesthetic direction?
|
|
154
|
+
- Are there elements that break the aesthetic (a generic component in an otherwise distinctive interface, a conflicting font, an out-of-place color)?
|
|
155
|
+
- Does the level of detail match the philosophy? (Minimalist designs should not have unnecessary decoration. Maximalist designs should not have empty, unfinished areas.)
|
|
156
|
+
|
|
157
|
+
### Component Quality
|
|
158
|
+
|
|
159
|
+
- Do existing components from the codebase appear correctly, or were they reimplemented?
|
|
160
|
+
- Are new components following the same API patterns (props, naming, file organization) as existing ones?
|
|
161
|
+
- Are there duplicate components that should be consolidated?
|
|
162
|
+
|
|
163
|
+
### States and Interactions
|
|
164
|
+
|
|
165
|
+
- Do interactive elements have all necessary states: default, hover, focus, active, disabled?
|
|
166
|
+
- Do form fields have states for: empty, filled, error, success, disabled?
|
|
167
|
+
- Are loading states handled? Empty states?
|
|
168
|
+
- Do transitions and animations match the philosophy's motion guidelines?
|
|
169
|
+
- Is there visual feedback for every user action?
|
|
170
|
+
|
|
171
|
+
### Responsive Behavior
|
|
172
|
+
|
|
173
|
+
- Does the layout work at mobile (375px), tablet (768px), and desktop (1280px+)?
|
|
174
|
+
- Do components adapt appropriately? (Not just shrink, but reorganize when needed.)
|
|
175
|
+
- Is touch target size adequate on mobile (minimum 44x44px)?
|
|
176
|
+
- Does text remain readable at all breakpoints? No text too small, no lines too wide (max 65-75 characters).
|
|
177
|
+
|
|
178
|
+
### Accessibility
|
|
179
|
+
|
|
180
|
+
- Color contrast: Do text/background combinations meet WCAG AA (4.5:1 for body text, 3:1 for large text)?
|
|
181
|
+
- Keyboard navigation: Can every interactive element be reached and activated with keyboard alone?
|
|
182
|
+
- Focus indicators: Are focus rings visible and styled consistently?
|
|
183
|
+
- Semantic HTML: Are headings in order? Are landmarks used (main, nav, header, footer)? Are form labels associated?
|
|
184
|
+
- Screen reader: Do images have alt text? Do icons have labels? Are decorative elements hidden from assistive technology?
|
|
185
|
+
- Motion: Is there a reduced-motion media query for users who need it?
|
|
186
|
+
|
|
187
|
+
### Typography
|
|
188
|
+
|
|
189
|
+
- Is the font actually loading? (Check for FOIT/FOUT flash.)
|
|
190
|
+
- Are line lengths comfortable for reading (45-75 characters on body text)?
|
|
191
|
+
- Is line height appropriate (1.4-1.6 for body, tighter for headings)?
|
|
192
|
+
- Is the type scale intentional, or are there arbitrary sizes?
|
|
193
|
+
|
|
194
|
+
### Dark Mode
|
|
195
|
+
|
|
196
|
+
- If the project has dark mode tokens, are they applied correctly?
|
|
197
|
+
- Are all color values using CSS variables (not hardcoded hex values that won't switch)?
|
|
198
|
+
- Does the dark palette feel intentional for the chosen philosophy, or is it a simple inversion?
|
|
199
|
+
- Are shadows adjusted for dark mode (darker, more transparent)?
|
|
200
|
+
- Do accent colors maintain sufficient contrast against dark backgrounds?
|
|
201
|
+
- Is there a working toggle mechanism or `prefers-color-scheme` support?
|
|
202
|
+
|
|
203
|
+
### Mobile-First
|
|
204
|
+
|
|
205
|
+
- Was the layout built mobile-first (using `min-width` media queries, not `max-width`)?
|
|
206
|
+
- Does the mobile layout work at 375px without horizontal scrolling?
|
|
207
|
+
- Is navigation adapted for mobile (not just a desktop nav that overflows)?
|
|
208
|
+
- Are touch targets at least 44x44px?
|
|
209
|
+
- Is body text at least 16px on mobile?
|
|
210
|
+
|
|
211
|
+
## Output Format
|
|
212
|
+
|
|
213
|
+
```markdown
|
|
214
|
+
# Design Review: [Feature/Page Name]
|
|
215
|
+
|
|
216
|
+
Reviewed against: DESIGN_BRIEF.md
|
|
217
|
+
Philosophy: [named philosophy]
|
|
218
|
+
Date: [date]
|
|
219
|
+
|
|
220
|
+
## Screenshots Captured
|
|
221
|
+
|
|
222
|
+
| Screenshot | Breakpoint | Description |
|
|
223
|
+
| -------------------------------------------- | ------------------ | --------------- |
|
|
224
|
+
| `screenshots/review-[page]-desktop-1280.png` | Desktop (1280×800) | [what it shows] |
|
|
225
|
+
| `screenshots/review-[page]-tablet-768.png` | Tablet (768×1024) | [what it shows] |
|
|
226
|
+
| `screenshots/review-[page]-mobile-375.png` | Mobile (375×812) | [what it shows] |
|
|
227
|
+
|
|
228
|
+
> All screenshots are in `.design/<feature-slug>/screenshots/`.
|
|
229
|
+
|
|
230
|
+
## Summary
|
|
231
|
+
|
|
232
|
+
[2-3 sentences on overall quality and the biggest finding.]
|
|
233
|
+
|
|
234
|
+
## Must Fix
|
|
235
|
+
|
|
236
|
+
1. **[Issue]**: [Specific description with file/component reference]. See [`screenshots/[relevant-screenshot].png`]. _Fix: [concrete suggestion]._
|
|
237
|
+
|
|
238
|
+
## Should Fix
|
|
239
|
+
|
|
240
|
+
1. **[Issue]**: [Description]. See [`screenshots/[relevant-screenshot].png`]. _Fix: [suggestion]._
|
|
241
|
+
|
|
242
|
+
## Could Improve
|
|
243
|
+
|
|
244
|
+
1. **[Issue]**: [Description]. _Suggestion: [idea]._
|
|
245
|
+
|
|
246
|
+
## What Works Well
|
|
247
|
+
|
|
248
|
+
[Note the strongest aspects of the implementation. This is not padding. Designers need to know what to keep doing.]
|
|
249
|
+
```
|