opsfuse-ui 0.1.24 → 0.1.25
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/style.css +256 -253
- 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,144 +1,144 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: frontend-design
|
|
3
|
-
description: Build distinctive, production-grade frontend interfaces with high design quality, guided by named aesthetic philosophies. Use when building components, pages, or applications. Generates working code with exceptional attention to aesthetic details and creative choices that avoid generic AI output.
|
|
4
|
-
---
|
|
5
|
-
|
|
6
|
-
This skill guides creation of distinctive, production-grade frontend interfaces. Implement real working code with exceptional attention to aesthetic detail.
|
|
7
|
-
|
|
8
|
-
## Example prompts
|
|
9
|
-
|
|
10
|
-
- "Build the hero section from the brief"
|
|
11
|
-
- "Create a card component in a Scandinavian style"
|
|
12
|
-
- "I want this to feel like a Japanese magazine. Build the layout."
|
|
13
|
-
- "Build the settings page. Use whatever style fits."
|
|
14
|
-
|
|
15
|
-
## Before You Write Any Code
|
|
16
|
-
|
|
17
|
-
1. **Explore the existing codebase first.** Scan specifically for:
|
|
18
|
-
- **Component directories**: `components/`, `ui/`, `shared/` and list every component by name and its props/API
|
|
19
|
-
- **CSS variables / tokens**: files named `tokens.css`, `variables.css`, `theme.css`, or `:root` declarations with custom properties
|
|
20
|
-
- **Tailwind config**: `tailwind.config.js` or `tailwind.config.ts`, check `theme.extend` for custom values
|
|
21
|
-
- **UI framework themes**: Material UI `createTheme`, Chakra `extendTheme`, shadcn `globals.css` and `components.json`
|
|
22
|
-
- **Storybook**: `.storybook/` directory or `*.stories.*` files indicating documented components
|
|
23
|
-
- **Font loading**: Google Fonts links, `@font-face` declarations, font imports
|
|
24
|
-
- **Layout patterns**: how existing pages handle grid, containers, breakpoints, and spacing
|
|
25
|
-
- **Package.json UI dependencies**: tailwindcss, @mui/material, @chakra-ui/react, @radix-ui, lucide-react, framer-motion, etc.
|
|
26
|
-
- If components exist that match or partially match what you need to build, extend or compose them. Do not create duplicates.
|
|
27
|
-
|
|
28
|
-
2. **Understand the context:**
|
|
29
|
-
- What problem does this interface solve? Who uses it?
|
|
30
|
-
- What is the intended emotional tone?
|
|
31
|
-
- What are the hard constraints (framework, devices, performance, accessibility)?
|
|
32
|
-
|
|
33
|
-
3. **Commit to an aesthetic direction.** Either the user names one (see philosophies below) or you choose one that fits the context. State your choice and why before writing code.
|
|
34
|
-
|
|
35
|
-
## Aesthetic Philosophies
|
|
36
|
-
|
|
37
|
-
When the user names a philosophy or describes a vibe, use these as concrete implementation guides. Each philosophy defines typography, color, layout, spacing, motion, and detail treatment.
|
|
38
|
-
|
|
39
|
-
### Dieter Rams (Functionalist)
|
|
40
|
-
Less but better. Every element earns its place. Nothing decorative without function.
|
|
41
|
-
- **Typography**: Clean sans-serif (Helvetica Neue, Suisse Intl, Akkurat). Tight letterspacing on headings. Generous line height on body. One size scale, used strictly.
|
|
42
|
-
- **Color**: Restrained. Monochromatic with a single functional accent. White or light grey backgrounds. Color is information, not decoration.
|
|
43
|
-
- **Layout**: Strict grid. Clear functional hierarchy. Components aligned to a spatial system. No asymmetry for its own sake.
|
|
44
|
-
- **Spacing**: Consistent, mathematical scale (4px/8px base). Generous padding. Breathing room between elements.
|
|
45
|
-
- **Motion**: Minimal. Purposeful transitions only (state changes, reveals). No decorative animation.
|
|
46
|
-
- **Details**: Subtle borders and dividers over shadows. Precise alignment. Rounded corners used sparingly and consistently.
|
|
47
|
-
|
|
48
|
-
### Swiss / International Typographic
|
|
49
|
-
Objectivity through structure. The grid is sacred. Content is king.
|
|
50
|
-
- **Typography**: Strong sans-serifs (Neue Haas Grotesk, Univers, Aktiv Grotesk). Dramatic scale contrast between headings and body. All-caps subheadings with generous letterspacing.
|
|
51
|
-
- **Color**: High contrast. Black, white, and one primary color. Bold color blocks as compositional elements.
|
|
52
|
-
- **Layout**: Rigid multi-column grid. Asymmetric balance. Text and image in dialogue. Alignment across elements is non-negotiable.
|
|
53
|
-
- **Spacing**: Defined by the grid module. Gutters are part of the design, not afterthought.
|
|
54
|
-
- **Motion**: Page transitions and scroll-triggered reveals that respect the grid. No playful bounce.
|
|
55
|
-
- **Details**: Rules (horizontal lines) as structural elements. No gradients. No shadows. Flatness is the point.
|
|
56
|
-
|
|
57
|
-
### Japanese Minimalism (Ma)
|
|
58
|
-
Negative space is content. Restraint communicates sophistication. Quiet over loud.
|
|
59
|
-
- **Typography**: Thin-weight sans-serifs or elegant serifs (Noto Sans, Cormorant). Generous line height (1.8-2.0). Small body size with large whitespace margins.
|
|
60
|
-
- **Color**: Muted naturals (warm greys, stone, sage, washi). Subtle tonal shifts over hard contrasts. Near-monochrome.
|
|
61
|
-
- **Layout**: Asymmetric but balanced. Off-center content. Large empty areas are intentional. Content floats in space.
|
|
62
|
-
- **Spacing**: Extreme whitespace. Padding and margins 2-3x what feels "normal." Elements breathe.
|
|
63
|
-
- **Motion**: Slow, gentle fades (400-600ms). No bounce, no overshoot. Opacity transitions over position shifts.
|
|
64
|
-
- **Details**: Hairline borders. Subtle texture (paper grain, linen). No sharp shadows. Soft, diffused effects.
|
|
65
|
-
|
|
66
|
-
### Brutalist / Raw
|
|
67
|
-
Structure is visible. No polish. Anti-aesthetic is the aesthetic.
|
|
68
|
-
- **Typography**: System fonts, monospace (JetBrains Mono, IBM Plex Mono, Courier), or aggressive display faces. Mixed sizes. Text as texture.
|
|
69
|
-
- **Color**: Black and white primary. If color, it is raw and clashing (construction yellow, hazard orange, terminal green). No gradients.
|
|
70
|
-
- **Layout**: Visible borders. Box model exposed. Stacked blocks. Deliberate roughness. Content first, beauty never.
|
|
71
|
-
- **Spacing**: Tight or intentionally uneven. Padding that feels compressed.
|
|
72
|
-
- **Motion**: None, or jarring (instant state changes, hard cuts). No easing.
|
|
73
|
-
- **Details**: Visible outlines. Default browser form elements can be intentional. Text-only interfaces. No icons unless functional.
|
|
74
|
-
|
|
75
|
-
### Scandinavian
|
|
76
|
-
Warmth plus restraint. Functional beauty. Accessible by default.
|
|
77
|
-
- **Typography**: Rounded, friendly sans-serifs (Nunito, Poppins, Circular, Cera Pro). Medium weights. Comfortable reading sizes.
|
|
78
|
-
- **Color**: Natural palette. Warm whites, soft blues, muted greens, clay. Pastel accents. No pure black (use charcoal).
|
|
79
|
-
- **Layout**: Clean and open. Card-based. Rounded corners (8-12px). Comfortable, generous layouts.
|
|
80
|
-
- **Spacing**: Generous but not extreme. Everything feels approachable and uncluttered.
|
|
81
|
-
- **Motion**: Gentle, natural easing. Subtle hover lifts. Content that settles into place.
|
|
82
|
-
- **Details**: Soft shadows (large blur, low opacity). Rounded elements. Warm undertones in greys. Illustration-friendly.
|
|
83
|
-
|
|
84
|
-
### Art Deco / Geometric
|
|
85
|
-
Bold symmetry. Decorative precision. Statement and luxury.
|
|
86
|
-
- **Typography**: Geometric display faces (Futura, Poiret One, Josefin Sans). All-caps headlines with extreme letterspacing. Serif body text for contrast.
|
|
87
|
-
- **Color**: Rich and deep. Gold/champagne, emerald, navy, burgundy, black. Metallic accents (gold gradients, shimmer effects).
|
|
88
|
-
- **Layout**: Symmetrical and centered. Strong vertical axis. Decorative frames and borders. Layered depth.
|
|
89
|
-
- **Spacing**: Structured and formal. Padding is architectural.
|
|
90
|
-
- **Motion**: Elegant reveals. Staggered entrance animations. Parallax depth.
|
|
91
|
-
- **Details**: Geometric patterns (chevrons, sunbursts, fan shapes). Ornamental borders. Texture (marble, brushed metal). Statement typography at hero scale.
|
|
92
|
-
|
|
93
|
-
### Neo-Memphis
|
|
94
|
-
Playful chaos. Anti-corporate. Shapes as characters.
|
|
95
|
-
- **Typography**: Mix of weights and styles. Clashing fonts is intentional. Oversized headlines. Text at angles.
|
|
96
|
-
- **Color**: Bold primaries and neons. Clashing combinations (pink and yellow, blue and orange). No muted tones. Flat color, no gradients.
|
|
97
|
-
- **Layout**: Broken grid. Overlapping elements. Shapes (circles, triangles, squiggles) as compositional elements. Asymmetric on purpose.
|
|
98
|
-
- **Spacing**: Dense in some areas, empty in others. Rhythm is irregular.
|
|
99
|
-
- **Motion**: Bouncy, playful. Exaggerated hover effects. Elements that wiggle, rotate, or pop.
|
|
100
|
-
- **Details**: Thick borders. Geometric shapes as decoration. Patterns (dots, dashes, zigzags). Drop shadows with hard edges and bright colors.
|
|
101
|
-
|
|
102
|
-
### Editorial / Magazine
|
|
103
|
-
Content-led design. Typography does the heavy lifting. Every page is a spread.
|
|
104
|
-
- **Typography**: Display serif for headlines (Playfair Display, Fraunces, Instrument Serif). Clean sans for body (DM Sans, Source Sans). Dramatic scale (hero headlines at 72-120px). Pull quotes. Drop caps.
|
|
105
|
-
- **Color**: Minimal. Black and white with one accent. Color used editorially (to highlight, not decorate).
|
|
106
|
-
- **Layout**: Strong column grid (3-5 columns). Full-bleed images. Text wrapping. Mixed column widths. Vertical rhythm.
|
|
107
|
-
- **Spacing**: Generous margins. Tight leading on headlines, open on body. Whitespace as a compositional tool.
|
|
108
|
-
- **Motion**: Scroll-triggered reveals. Parallax on images. Smooth page transitions.
|
|
109
|
-
- **Details**: Thin rules as dividers. Caption typography. Issue/date metadata. Print-inspired details (folio numbers, running headers).
|
|
110
|
-
|
|
111
|
-
## Implementation Guidelines
|
|
112
|
-
|
|
113
|
-
- **Typography**: Choose distinctive fonts loaded via Google Fonts or CDN. Avoid generic defaults (Inter, Roboto, Arial, system fonts). Pair a display font with a body font.
|
|
114
|
-
- **Color**: Use CSS variables for consistency. Dominant color with sharp accents outperforms safe, evenly-distributed palettes.
|
|
115
|
-
- **Motion**: CSS transitions for HTML. Framer Motion / Motion library for React. Focus on high-impact moments (page load reveals, state changes) over scattered micro-interactions.
|
|
116
|
-
- **Spatial composition**: Unexpected layouts earn attention. Asymmetry, overlap, diagonal flow, grid-breaking elements. Or, if the philosophy demands it, strict grids executed with precision.
|
|
117
|
-
- **Backgrounds and depth**: Create atmosphere. Gradient meshes, noise textures, geometric patterns, layered transparencies, grain overlays. Match the chosen philosophy.
|
|
118
|
-
|
|
119
|
-
NEVER produce generic AI aesthetics: purple gradients on white, Inter font, predictable card grids, cookie-cutter component layouts. Every output should feel designed for its specific context.
|
|
120
|
-
|
|
121
|
-
Match implementation complexity to the aesthetic vision. A Dieter Rams interface is 50 lines of precise CSS. A Neo-Memphis interface is 300 lines of creative chaos. Both are correct.
|
|
122
|
-
|
|
123
|
-
## Mobile-First
|
|
124
|
-
|
|
125
|
-
Build mobile layout first, then scale up. This is non-negotiable.
|
|
126
|
-
|
|
127
|
-
- Start with a single-column layout at 375px width.
|
|
128
|
-
- Add complexity at each breakpoint (`min-width` media queries, not `max-width`).
|
|
129
|
-
- Touch targets must be at least 44x44px on mobile.
|
|
130
|
-
- Body text must be at least 16px on mobile (prevents iOS zoom on input focus).
|
|
131
|
-
- Navigation must have a mobile-specific pattern (hamburger, bottom tabs, or drawer). Do not rely on horizontal nav bars that overflow.
|
|
132
|
-
- Test that line lengths stay comfortable (45-75 characters) at every breakpoint.
|
|
133
|
-
|
|
134
|
-
## Dark Mode
|
|
135
|
-
|
|
136
|
-
If a design tokens file exists (from `/design-tokens`), use its dark mode palette. If not, generate dark mode support alongside the light theme.
|
|
137
|
-
|
|
138
|
-
- Use CSS custom properties so switching themes means changing variable values, not rewriting components.
|
|
139
|
-
- Support both `prefers-color-scheme` media query (system preference) and a `[data-theme="dark"]` attribute (manual toggle).
|
|
140
|
-
- Do not simply invert colors. Dark backgrounds should be warm or cool to match the philosophy (warm charcoal for Scandinavian, cool slate for Swiss, near-black for Brutalist).
|
|
141
|
-
- Reduce pure white text to off-white (e.g., `#E5E5E5` or `rgba(255,255,255,0.87)`) to reduce eye strain.
|
|
142
|
-
- Shadows in dark mode should be darker and more transparent, not the same values as light mode.
|
|
143
|
-
- Accent colors may need lightness adjustments to maintain WCAG contrast ratios against dark backgrounds.
|
|
144
|
-
- Include a `prefers-reduced-motion` media query for users who need it. Disable or simplify all animations and transitions within that query.
|
|
1
|
+
---
|
|
2
|
+
name: frontend-design
|
|
3
|
+
description: Build distinctive, production-grade frontend interfaces with high design quality, guided by named aesthetic philosophies. Use when building components, pages, or applications. Generates working code with exceptional attention to aesthetic details and creative choices that avoid generic AI output.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
This skill guides creation of distinctive, production-grade frontend interfaces. Implement real working code with exceptional attention to aesthetic detail.
|
|
7
|
+
|
|
8
|
+
## Example prompts
|
|
9
|
+
|
|
10
|
+
- "Build the hero section from the brief"
|
|
11
|
+
- "Create a card component in a Scandinavian style"
|
|
12
|
+
- "I want this to feel like a Japanese magazine. Build the layout."
|
|
13
|
+
- "Build the settings page. Use whatever style fits."
|
|
14
|
+
|
|
15
|
+
## Before You Write Any Code
|
|
16
|
+
|
|
17
|
+
1. **Explore the existing codebase first.** Scan specifically for:
|
|
18
|
+
- **Component directories**: `components/`, `ui/`, `shared/` and list every component by name and its props/API
|
|
19
|
+
- **CSS variables / tokens**: files named `tokens.css`, `variables.css`, `theme.css`, or `:root` declarations with custom properties
|
|
20
|
+
- **Tailwind config**: `tailwind.config.js` or `tailwind.config.ts`, check `theme.extend` for custom values
|
|
21
|
+
- **UI framework themes**: Material UI `createTheme`, Chakra `extendTheme`, shadcn `globals.css` and `components.json`
|
|
22
|
+
- **Storybook**: `.storybook/` directory or `*.stories.*` files indicating documented components
|
|
23
|
+
- **Font loading**: Google Fonts links, `@font-face` declarations, font imports
|
|
24
|
+
- **Layout patterns**: how existing pages handle grid, containers, breakpoints, and spacing
|
|
25
|
+
- **Package.json UI dependencies**: tailwindcss, @mui/material, @chakra-ui/react, @radix-ui, lucide-react, framer-motion, etc.
|
|
26
|
+
- If components exist that match or partially match what you need to build, extend or compose them. Do not create duplicates.
|
|
27
|
+
|
|
28
|
+
2. **Understand the context:**
|
|
29
|
+
- What problem does this interface solve? Who uses it?
|
|
30
|
+
- What is the intended emotional tone?
|
|
31
|
+
- What are the hard constraints (framework, devices, performance, accessibility)?
|
|
32
|
+
|
|
33
|
+
3. **Commit to an aesthetic direction.** Either the user names one (see philosophies below) or you choose one that fits the context. State your choice and why before writing code.
|
|
34
|
+
|
|
35
|
+
## Aesthetic Philosophies
|
|
36
|
+
|
|
37
|
+
When the user names a philosophy or describes a vibe, use these as concrete implementation guides. Each philosophy defines typography, color, layout, spacing, motion, and detail treatment.
|
|
38
|
+
|
|
39
|
+
### Dieter Rams (Functionalist)
|
|
40
|
+
Less but better. Every element earns its place. Nothing decorative without function.
|
|
41
|
+
- **Typography**: Clean sans-serif (Helvetica Neue, Suisse Intl, Akkurat). Tight letterspacing on headings. Generous line height on body. One size scale, used strictly.
|
|
42
|
+
- **Color**: Restrained. Monochromatic with a single functional accent. White or light grey backgrounds. Color is information, not decoration.
|
|
43
|
+
- **Layout**: Strict grid. Clear functional hierarchy. Components aligned to a spatial system. No asymmetry for its own sake.
|
|
44
|
+
- **Spacing**: Consistent, mathematical scale (4px/8px base). Generous padding. Breathing room between elements.
|
|
45
|
+
- **Motion**: Minimal. Purposeful transitions only (state changes, reveals). No decorative animation.
|
|
46
|
+
- **Details**: Subtle borders and dividers over shadows. Precise alignment. Rounded corners used sparingly and consistently.
|
|
47
|
+
|
|
48
|
+
### Swiss / International Typographic
|
|
49
|
+
Objectivity through structure. The grid is sacred. Content is king.
|
|
50
|
+
- **Typography**: Strong sans-serifs (Neue Haas Grotesk, Univers, Aktiv Grotesk). Dramatic scale contrast between headings and body. All-caps subheadings with generous letterspacing.
|
|
51
|
+
- **Color**: High contrast. Black, white, and one primary color. Bold color blocks as compositional elements.
|
|
52
|
+
- **Layout**: Rigid multi-column grid. Asymmetric balance. Text and image in dialogue. Alignment across elements is non-negotiable.
|
|
53
|
+
- **Spacing**: Defined by the grid module. Gutters are part of the design, not afterthought.
|
|
54
|
+
- **Motion**: Page transitions and scroll-triggered reveals that respect the grid. No playful bounce.
|
|
55
|
+
- **Details**: Rules (horizontal lines) as structural elements. No gradients. No shadows. Flatness is the point.
|
|
56
|
+
|
|
57
|
+
### Japanese Minimalism (Ma)
|
|
58
|
+
Negative space is content. Restraint communicates sophistication. Quiet over loud.
|
|
59
|
+
- **Typography**: Thin-weight sans-serifs or elegant serifs (Noto Sans, Cormorant). Generous line height (1.8-2.0). Small body size with large whitespace margins.
|
|
60
|
+
- **Color**: Muted naturals (warm greys, stone, sage, washi). Subtle tonal shifts over hard contrasts. Near-monochrome.
|
|
61
|
+
- **Layout**: Asymmetric but balanced. Off-center content. Large empty areas are intentional. Content floats in space.
|
|
62
|
+
- **Spacing**: Extreme whitespace. Padding and margins 2-3x what feels "normal." Elements breathe.
|
|
63
|
+
- **Motion**: Slow, gentle fades (400-600ms). No bounce, no overshoot. Opacity transitions over position shifts.
|
|
64
|
+
- **Details**: Hairline borders. Subtle texture (paper grain, linen). No sharp shadows. Soft, diffused effects.
|
|
65
|
+
|
|
66
|
+
### Brutalist / Raw
|
|
67
|
+
Structure is visible. No polish. Anti-aesthetic is the aesthetic.
|
|
68
|
+
- **Typography**: System fonts, monospace (JetBrains Mono, IBM Plex Mono, Courier), or aggressive display faces. Mixed sizes. Text as texture.
|
|
69
|
+
- **Color**: Black and white primary. If color, it is raw and clashing (construction yellow, hazard orange, terminal green). No gradients.
|
|
70
|
+
- **Layout**: Visible borders. Box model exposed. Stacked blocks. Deliberate roughness. Content first, beauty never.
|
|
71
|
+
- **Spacing**: Tight or intentionally uneven. Padding that feels compressed.
|
|
72
|
+
- **Motion**: None, or jarring (instant state changes, hard cuts). No easing.
|
|
73
|
+
- **Details**: Visible outlines. Default browser form elements can be intentional. Text-only interfaces. No icons unless functional.
|
|
74
|
+
|
|
75
|
+
### Scandinavian
|
|
76
|
+
Warmth plus restraint. Functional beauty. Accessible by default.
|
|
77
|
+
- **Typography**: Rounded, friendly sans-serifs (Nunito, Poppins, Circular, Cera Pro). Medium weights. Comfortable reading sizes.
|
|
78
|
+
- **Color**: Natural palette. Warm whites, soft blues, muted greens, clay. Pastel accents. No pure black (use charcoal).
|
|
79
|
+
- **Layout**: Clean and open. Card-based. Rounded corners (8-12px). Comfortable, generous layouts.
|
|
80
|
+
- **Spacing**: Generous but not extreme. Everything feels approachable and uncluttered.
|
|
81
|
+
- **Motion**: Gentle, natural easing. Subtle hover lifts. Content that settles into place.
|
|
82
|
+
- **Details**: Soft shadows (large blur, low opacity). Rounded elements. Warm undertones in greys. Illustration-friendly.
|
|
83
|
+
|
|
84
|
+
### Art Deco / Geometric
|
|
85
|
+
Bold symmetry. Decorative precision. Statement and luxury.
|
|
86
|
+
- **Typography**: Geometric display faces (Futura, Poiret One, Josefin Sans). All-caps headlines with extreme letterspacing. Serif body text for contrast.
|
|
87
|
+
- **Color**: Rich and deep. Gold/champagne, emerald, navy, burgundy, black. Metallic accents (gold gradients, shimmer effects).
|
|
88
|
+
- **Layout**: Symmetrical and centered. Strong vertical axis. Decorative frames and borders. Layered depth.
|
|
89
|
+
- **Spacing**: Structured and formal. Padding is architectural.
|
|
90
|
+
- **Motion**: Elegant reveals. Staggered entrance animations. Parallax depth.
|
|
91
|
+
- **Details**: Geometric patterns (chevrons, sunbursts, fan shapes). Ornamental borders. Texture (marble, brushed metal). Statement typography at hero scale.
|
|
92
|
+
|
|
93
|
+
### Neo-Memphis
|
|
94
|
+
Playful chaos. Anti-corporate. Shapes as characters.
|
|
95
|
+
- **Typography**: Mix of weights and styles. Clashing fonts is intentional. Oversized headlines. Text at angles.
|
|
96
|
+
- **Color**: Bold primaries and neons. Clashing combinations (pink and yellow, blue and orange). No muted tones. Flat color, no gradients.
|
|
97
|
+
- **Layout**: Broken grid. Overlapping elements. Shapes (circles, triangles, squiggles) as compositional elements. Asymmetric on purpose.
|
|
98
|
+
- **Spacing**: Dense in some areas, empty in others. Rhythm is irregular.
|
|
99
|
+
- **Motion**: Bouncy, playful. Exaggerated hover effects. Elements that wiggle, rotate, or pop.
|
|
100
|
+
- **Details**: Thick borders. Geometric shapes as decoration. Patterns (dots, dashes, zigzags). Drop shadows with hard edges and bright colors.
|
|
101
|
+
|
|
102
|
+
### Editorial / Magazine
|
|
103
|
+
Content-led design. Typography does the heavy lifting. Every page is a spread.
|
|
104
|
+
- **Typography**: Display serif for headlines (Playfair Display, Fraunces, Instrument Serif). Clean sans for body (DM Sans, Source Sans). Dramatic scale (hero headlines at 72-120px). Pull quotes. Drop caps.
|
|
105
|
+
- **Color**: Minimal. Black and white with one accent. Color used editorially (to highlight, not decorate).
|
|
106
|
+
- **Layout**: Strong column grid (3-5 columns). Full-bleed images. Text wrapping. Mixed column widths. Vertical rhythm.
|
|
107
|
+
- **Spacing**: Generous margins. Tight leading on headlines, open on body. Whitespace as a compositional tool.
|
|
108
|
+
- **Motion**: Scroll-triggered reveals. Parallax on images. Smooth page transitions.
|
|
109
|
+
- **Details**: Thin rules as dividers. Caption typography. Issue/date metadata. Print-inspired details (folio numbers, running headers).
|
|
110
|
+
|
|
111
|
+
## Implementation Guidelines
|
|
112
|
+
|
|
113
|
+
- **Typography**: Choose distinctive fonts loaded via Google Fonts or CDN. Avoid generic defaults (Inter, Roboto, Arial, system fonts). Pair a display font with a body font.
|
|
114
|
+
- **Color**: Use CSS variables for consistency. Dominant color with sharp accents outperforms safe, evenly-distributed palettes.
|
|
115
|
+
- **Motion**: CSS transitions for HTML. Framer Motion / Motion library for React. Focus on high-impact moments (page load reveals, state changes) over scattered micro-interactions.
|
|
116
|
+
- **Spatial composition**: Unexpected layouts earn attention. Asymmetry, overlap, diagonal flow, grid-breaking elements. Or, if the philosophy demands it, strict grids executed with precision.
|
|
117
|
+
- **Backgrounds and depth**: Create atmosphere. Gradient meshes, noise textures, geometric patterns, layered transparencies, grain overlays. Match the chosen philosophy.
|
|
118
|
+
|
|
119
|
+
NEVER produce generic AI aesthetics: purple gradients on white, Inter font, predictable card grids, cookie-cutter component layouts. Every output should feel designed for its specific context.
|
|
120
|
+
|
|
121
|
+
Match implementation complexity to the aesthetic vision. A Dieter Rams interface is 50 lines of precise CSS. A Neo-Memphis interface is 300 lines of creative chaos. Both are correct.
|
|
122
|
+
|
|
123
|
+
## Mobile-First
|
|
124
|
+
|
|
125
|
+
Build mobile layout first, then scale up. This is non-negotiable.
|
|
126
|
+
|
|
127
|
+
- Start with a single-column layout at 375px width.
|
|
128
|
+
- Add complexity at each breakpoint (`min-width` media queries, not `max-width`).
|
|
129
|
+
- Touch targets must be at least 44x44px on mobile.
|
|
130
|
+
- Body text must be at least 16px on mobile (prevents iOS zoom on input focus).
|
|
131
|
+
- Navigation must have a mobile-specific pattern (hamburger, bottom tabs, or drawer). Do not rely on horizontal nav bars that overflow.
|
|
132
|
+
- Test that line lengths stay comfortable (45-75 characters) at every breakpoint.
|
|
133
|
+
|
|
134
|
+
## Dark Mode
|
|
135
|
+
|
|
136
|
+
If a design tokens file exists (from `/design-tokens`), use its dark mode palette. If not, generate dark mode support alongside the light theme.
|
|
137
|
+
|
|
138
|
+
- Use CSS custom properties so switching themes means changing variable values, not rewriting components.
|
|
139
|
+
- Support both `prefers-color-scheme` media query (system preference) and a `[data-theme="dark"]` attribute (manual toggle).
|
|
140
|
+
- Do not simply invert colors. Dark backgrounds should be warm or cool to match the philosophy (warm charcoal for Scandinavian, cool slate for Swiss, near-black for Brutalist).
|
|
141
|
+
- Reduce pure white text to off-white (e.g., `#E5E5E5` or `rgba(255,255,255,0.87)`) to reduce eye strain.
|
|
142
|
+
- Shadows in dark mode should be darker and more transparent, not the same values as light mode.
|
|
143
|
+
- Accent colors may need lightness adjustments to maintain WCAG contrast ratios against dark backgrounds.
|
|
144
|
+
- Include a `prefers-reduced-motion` media query for users who need it. Disable or simplify all animations and transitions within that query.
|
|
@@ -1,21 +1,21 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: grill-me
|
|
3
|
-
description: Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, challenge an approach, or mentions "grill me".
|
|
4
|
-
---
|
|
5
|
-
|
|
6
|
-
## Example prompts
|
|
7
|
-
|
|
8
|
-
- "Grill me on this landing page idea"
|
|
9
|
-
- "I want to build a dashboard for tracking team metrics. Challenge my thinking."
|
|
10
|
-
- "Stress-test my approach to this settings page"
|
|
11
|
-
- "I have a rough idea for a portfolio site. Help me think it through."
|
|
12
|
-
|
|
13
|
-
## Instructions
|
|
14
|
-
|
|
15
|
-
Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one by one.
|
|
16
|
-
|
|
17
|
-
If a question can be answered by exploring the codebase, explore the codebase instead of asking me.
|
|
18
|
-
|
|
19
|
-
If a question can be answered by examining existing components, styles, or design tokens in the project, examine them instead of asking me.
|
|
20
|
-
|
|
21
|
-
For each question, provide your recommended answer.
|
|
1
|
+
---
|
|
2
|
+
name: grill-me
|
|
3
|
+
description: Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, challenge an approach, or mentions "grill me".
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
## Example prompts
|
|
7
|
+
|
|
8
|
+
- "Grill me on this landing page idea"
|
|
9
|
+
- "I want to build a dashboard for tracking team metrics. Challenge my thinking."
|
|
10
|
+
- "Stress-test my approach to this settings page"
|
|
11
|
+
- "I have a rough idea for a portfolio site. Help me think it through."
|
|
12
|
+
|
|
13
|
+
## Instructions
|
|
14
|
+
|
|
15
|
+
Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one by one.
|
|
16
|
+
|
|
17
|
+
If a question can be answered by exploring the codebase, explore the codebase instead of asking me.
|
|
18
|
+
|
|
19
|
+
If a question can be answered by examining existing components, styles, or design tokens in the project, examine them instead of asking me.
|
|
20
|
+
|
|
21
|
+
For each question, provide your recommended answer.
|
|
@@ -1,111 +1,111 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: information-architecture
|
|
3
|
-
description: Define the structural layer of a product or site before visual design begins. Covers navigation, content hierarchy, page structure, URL patterns, and user flows. Use when user wants to plan site structure, define navigation, map user flows, organize content, or mentions "IA" or "information architecture".
|
|
4
|
-
---
|
|
5
|
-
|
|
6
|
-
This skill defines the structural skeleton of a product or site. It sits between the design brief and the build. Run this after the brief is written and before tasks are created.
|
|
7
|
-
|
|
8
|
-
## Example prompts
|
|
9
|
-
|
|
10
|
-
- "Plan the IA for this app before I start building"
|
|
11
|
-
- "Map out the navigation and page structure"
|
|
12
|
-
- "I need to organize the content for a documentation site"
|
|
13
|
-
- "Define user flows for the onboarding experience"
|
|
14
|
-
|
|
15
|
-
## Process
|
|
16
|
-
|
|
17
|
-
1. Look for an existing design brief at `.design/*/DESIGN_BRIEF.md`. If multiple subfolders exist, use the most recently modified one, or ask the user which feature they are working on. If no brief exists, ask the user what they are building and for whom.
|
|
18
|
-
|
|
19
|
-
2. Explore the existing codebase to understand what structure already exists:
|
|
20
|
-
- **Routing**: Next.js `app/` or `pages/` directory, React Router config, Vue Router, SvelteKit routes, or static HTML page files
|
|
21
|
-
- **Navigation components**: header, sidebar, navbar, breadcrumb, footer components
|
|
22
|
-
- **Layout components**: root layouts, nested layouts, page wrappers, container components
|
|
23
|
-
- **Page directories**: how pages are currently organized in the file system
|
|
24
|
-
- **URL patterns**: existing slugs, dynamic segments, query parameter conventions
|
|
25
|
-
- **CMS or data layer**: content models, API routes, data fetching patterns, MDX/content directories
|
|
26
|
-
- If structure exists, this skill extends and improves it. Do not propose a new architecture that ignores what is already built.
|
|
27
|
-
|
|
28
|
-
3. Interview the user about structural decisions. For each question, provide your recommended answer.
|
|
29
|
-
|
|
30
|
-
Cover at minimum:
|
|
31
|
-
- What are the primary things a user needs to find or do? Rank by frequency.
|
|
32
|
-
- How many levels of navigation depth are acceptable?
|
|
33
|
-
- What content will grow over time vs. what is fixed?
|
|
34
|
-
- Are there distinct user types who need different entry points?
|
|
35
|
-
- What is the one page/view where the user spends 80% of their time?
|
|
36
|
-
|
|
37
|
-
4. Once you have a shared understanding, produce the IA document using the template below and save it as `INFORMATION_ARCHITECTURE.md` in the same `.design/<feature-slug>/` subfolder as the design brief.
|
|
38
|
-
|
|
39
|
-
## IA Document Template
|
|
40
|
-
|
|
41
|
-
```markdown
|
|
42
|
-
# Information Architecture: [Product/Site Name]
|
|
43
|
-
|
|
44
|
-
## Site Map
|
|
45
|
-
|
|
46
|
-
A hierarchical map of every page or view. Use indentation to show nesting. Include the URL pattern for each.
|
|
47
|
-
|
|
48
|
-
- Home `/`
|
|
49
|
-
- Feature A `/feature-a`
|
|
50
|
-
- Sub-page `/feature-a/detail`
|
|
51
|
-
- Feature B `/feature-b`
|
|
52
|
-
- Settings `/settings`
|
|
53
|
-
- Profile `/settings/profile`
|
|
54
|
-
|
|
55
|
-
## Navigation Model
|
|
56
|
-
|
|
57
|
-
Describe the navigation system:
|
|
58
|
-
- **Primary navigation**: What appears in the main nav? Maximum items.
|
|
59
|
-
- **Secondary navigation**: Sidebar, tabs, or contextual links within sections.
|
|
60
|
-
- **Utility navigation**: Account, settings, help, and anything outside the main content hierarchy.
|
|
61
|
-
- **Mobile navigation**: How navigation adapts. Hamburger, bottom tabs, or something else.
|
|
62
|
-
|
|
63
|
-
## Content Hierarchy
|
|
64
|
-
|
|
65
|
-
For each major page or view, define the content priority:
|
|
66
|
-
|
|
67
|
-
### [Page Name]
|
|
68
|
-
1. [Highest priority content] -- Why this comes first
|
|
69
|
-
2. [Second priority] -- Why this comes second
|
|
70
|
-
3. [Third priority] -- Rationale
|
|
71
|
-
4. [Below the fold / secondary]
|
|
72
|
-
|
|
73
|
-
## User Flows
|
|
74
|
-
|
|
75
|
-
The critical paths through the product. Each flow is a sequence of steps with decision points noted.
|
|
76
|
-
|
|
77
|
-
### [Flow Name] (e.g., "New user onboarding" or "Create a project")
|
|
78
|
-
1. User lands on [page]
|
|
79
|
-
2. User sees [content/prompt]
|
|
80
|
-
3. User takes action: [action]
|
|
81
|
-
- If [condition A] -> [outcome]
|
|
82
|
-
- If [condition B] -> [outcome]
|
|
83
|
-
4. User arrives at [destination]
|
|
84
|
-
|
|
85
|
-
## Naming Conventions
|
|
86
|
-
|
|
87
|
-
A glossary of terms used in the interface. Consistency matters. Pick one word and use it everywhere.
|
|
88
|
-
|
|
89
|
-
| Concept | Label in UI | Notes |
|
|
90
|
-
|---------|-------------|-------|
|
|
91
|
-
| [thing] | [what we call it] | [why this word] |
|
|
92
|
-
|
|
93
|
-
## Component Reuse Map
|
|
94
|
-
|
|
95
|
-
Which structural components (layouts, containers, navigation elements) are shared across pages.
|
|
96
|
-
|
|
97
|
-
| Component | Used on | Behavior differences |
|
|
98
|
-
|-----------|---------|---------------------|
|
|
99
|
-
| [layout/component] | [pages] | [any variations] |
|
|
100
|
-
|
|
101
|
-
## Content Growth Plan
|
|
102
|
-
|
|
103
|
-
Which sections of the site will accumulate content over time and how the IA accommodates that growth (pagination, filtering, search, archive patterns).
|
|
104
|
-
|
|
105
|
-
## URL Strategy
|
|
106
|
-
|
|
107
|
-
Rules for URL construction:
|
|
108
|
-
- Pattern: [e.g., `/section/subsection/item-slug`]
|
|
109
|
-
- Dynamic segments: [what is parameterized]
|
|
110
|
-
- Query parameters: [filtering, sorting, pagination]
|
|
111
|
-
```
|
|
1
|
+
---
|
|
2
|
+
name: information-architecture
|
|
3
|
+
description: Define the structural layer of a product or site before visual design begins. Covers navigation, content hierarchy, page structure, URL patterns, and user flows. Use when user wants to plan site structure, define navigation, map user flows, organize content, or mentions "IA" or "information architecture".
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
This skill defines the structural skeleton of a product or site. It sits between the design brief and the build. Run this after the brief is written and before tasks are created.
|
|
7
|
+
|
|
8
|
+
## Example prompts
|
|
9
|
+
|
|
10
|
+
- "Plan the IA for this app before I start building"
|
|
11
|
+
- "Map out the navigation and page structure"
|
|
12
|
+
- "I need to organize the content for a documentation site"
|
|
13
|
+
- "Define user flows for the onboarding experience"
|
|
14
|
+
|
|
15
|
+
## Process
|
|
16
|
+
|
|
17
|
+
1. Look for an existing design brief at `.design/*/DESIGN_BRIEF.md`. If multiple subfolders exist, use the most recently modified one, or ask the user which feature they are working on. If no brief exists, ask the user what they are building and for whom.
|
|
18
|
+
|
|
19
|
+
2. Explore the existing codebase to understand what structure already exists:
|
|
20
|
+
- **Routing**: Next.js `app/` or `pages/` directory, React Router config, Vue Router, SvelteKit routes, or static HTML page files
|
|
21
|
+
- **Navigation components**: header, sidebar, navbar, breadcrumb, footer components
|
|
22
|
+
- **Layout components**: root layouts, nested layouts, page wrappers, container components
|
|
23
|
+
- **Page directories**: how pages are currently organized in the file system
|
|
24
|
+
- **URL patterns**: existing slugs, dynamic segments, query parameter conventions
|
|
25
|
+
- **CMS or data layer**: content models, API routes, data fetching patterns, MDX/content directories
|
|
26
|
+
- If structure exists, this skill extends and improves it. Do not propose a new architecture that ignores what is already built.
|
|
27
|
+
|
|
28
|
+
3. Interview the user about structural decisions. For each question, provide your recommended answer.
|
|
29
|
+
|
|
30
|
+
Cover at minimum:
|
|
31
|
+
- What are the primary things a user needs to find or do? Rank by frequency.
|
|
32
|
+
- How many levels of navigation depth are acceptable?
|
|
33
|
+
- What content will grow over time vs. what is fixed?
|
|
34
|
+
- Are there distinct user types who need different entry points?
|
|
35
|
+
- What is the one page/view where the user spends 80% of their time?
|
|
36
|
+
|
|
37
|
+
4. Once you have a shared understanding, produce the IA document using the template below and save it as `INFORMATION_ARCHITECTURE.md` in the same `.design/<feature-slug>/` subfolder as the design brief.
|
|
38
|
+
|
|
39
|
+
## IA Document Template
|
|
40
|
+
|
|
41
|
+
```markdown
|
|
42
|
+
# Information Architecture: [Product/Site Name]
|
|
43
|
+
|
|
44
|
+
## Site Map
|
|
45
|
+
|
|
46
|
+
A hierarchical map of every page or view. Use indentation to show nesting. Include the URL pattern for each.
|
|
47
|
+
|
|
48
|
+
- Home `/`
|
|
49
|
+
- Feature A `/feature-a`
|
|
50
|
+
- Sub-page `/feature-a/detail`
|
|
51
|
+
- Feature B `/feature-b`
|
|
52
|
+
- Settings `/settings`
|
|
53
|
+
- Profile `/settings/profile`
|
|
54
|
+
|
|
55
|
+
## Navigation Model
|
|
56
|
+
|
|
57
|
+
Describe the navigation system:
|
|
58
|
+
- **Primary navigation**: What appears in the main nav? Maximum items.
|
|
59
|
+
- **Secondary navigation**: Sidebar, tabs, or contextual links within sections.
|
|
60
|
+
- **Utility navigation**: Account, settings, help, and anything outside the main content hierarchy.
|
|
61
|
+
- **Mobile navigation**: How navigation adapts. Hamburger, bottom tabs, or something else.
|
|
62
|
+
|
|
63
|
+
## Content Hierarchy
|
|
64
|
+
|
|
65
|
+
For each major page or view, define the content priority:
|
|
66
|
+
|
|
67
|
+
### [Page Name]
|
|
68
|
+
1. [Highest priority content] -- Why this comes first
|
|
69
|
+
2. [Second priority] -- Why this comes second
|
|
70
|
+
3. [Third priority] -- Rationale
|
|
71
|
+
4. [Below the fold / secondary]
|
|
72
|
+
|
|
73
|
+
## User Flows
|
|
74
|
+
|
|
75
|
+
The critical paths through the product. Each flow is a sequence of steps with decision points noted.
|
|
76
|
+
|
|
77
|
+
### [Flow Name] (e.g., "New user onboarding" or "Create a project")
|
|
78
|
+
1. User lands on [page]
|
|
79
|
+
2. User sees [content/prompt]
|
|
80
|
+
3. User takes action: [action]
|
|
81
|
+
- If [condition A] -> [outcome]
|
|
82
|
+
- If [condition B] -> [outcome]
|
|
83
|
+
4. User arrives at [destination]
|
|
84
|
+
|
|
85
|
+
## Naming Conventions
|
|
86
|
+
|
|
87
|
+
A glossary of terms used in the interface. Consistency matters. Pick one word and use it everywhere.
|
|
88
|
+
|
|
89
|
+
| Concept | Label in UI | Notes |
|
|
90
|
+
|---------|-------------|-------|
|
|
91
|
+
| [thing] | [what we call it] | [why this word] |
|
|
92
|
+
|
|
93
|
+
## Component Reuse Map
|
|
94
|
+
|
|
95
|
+
Which structural components (layouts, containers, navigation elements) are shared across pages.
|
|
96
|
+
|
|
97
|
+
| Component | Used on | Behavior differences |
|
|
98
|
+
|-----------|---------|---------------------|
|
|
99
|
+
| [layout/component] | [pages] | [any variations] |
|
|
100
|
+
|
|
101
|
+
## Content Growth Plan
|
|
102
|
+
|
|
103
|
+
Which sections of the site will accumulate content over time and how the IA accommodates that growth (pagination, filtering, search, archive patterns).
|
|
104
|
+
|
|
105
|
+
## URL Strategy
|
|
106
|
+
|
|
107
|
+
Rules for URL construction:
|
|
108
|
+
- Pattern: [e.g., `/section/subsection/item-slug`]
|
|
109
|
+
- Dynamic segments: [what is parameterized]
|
|
110
|
+
- Query parameters: [filtering, sorting, pagination]
|
|
111
|
+
```
|