opencodekit 0.21.1 → 0.21.2

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.
@@ -1,197 +0,0 @@
1
- ---
2
- name: stitch-design-taste
3
- description: Use when generating DESIGN.md files for Google Stitch projects to enforce premium, anti-generic UI standards. Load BEFORE stitch skill when design quality matters. Stitch-specific only — do not use for general web projects.
4
- ---
5
-
6
- ## When to Use
7
-
8
- - When generating DESIGN.md files for Google Stitch projects
9
- - Before loading the stitch skill when design quality matters
10
- - When enforcing premium, anti-generic UI standards in Stitch workflows
11
-
12
- ## When NOT to Use
13
-
14
- - For general web projects not using Google Stitch
15
- - When the stitch project already has a satisfactory DESIGN.md
16
- - For non-UI Stitch operations (data, API, backend)
17
-
18
-
19
- # Stitch Design Taste — Semantic Design System Skill
20
-
21
- ## Overview
22
- This skill generates `DESIGN.md` files optimized for Google Stitch screen generation. It translates the battle-tested anti-slop frontend engineering directives into Stitch's native semantic design language — descriptive, natural-language rules paired with precise values that Stitch's AI agent can interpret to produce premium, non-generic interfaces.
23
-
24
- The generated `DESIGN.md` serves as the **single source of truth** for prompting Stitch to generate new screens that align with a curated, high-agency design language. Stitch interprets design through **"Visual Descriptions"** supported by specific color values, typography specs, and component behaviors.
25
-
26
- ## Prerequisites
27
- - Access to Google Stitch via [labs.google.com/stitch](https://labs.google.com/stitch)
28
- - Optionally: Stitch MCP Server for programmatic integration with Cursor, Antigravity, or Gemini CLI
29
-
30
- ## The Goal
31
- Generate a `DESIGN.md` file that encodes:
32
- 1. **Visual atmosphere** — the mood, density, and design philosophy
33
- 2. **Color calibration** — neutrals, accents, and banned patterns with hex codes
34
- 3. **Typographic architecture** — font stacks, scale hierarchy, and anti-patterns
35
- 4. **Component behaviors** — buttons, cards, inputs with interaction states
36
- 5. **Layout principles** — grid systems, spacing philosophy, responsive strategy
37
- 6. **Motion philosophy** — animation engine specs, spring physics, perpetual micro-interactions
38
- 7. **Anti-patterns** — explicit list of banned AI design clichés
39
-
40
- ## Analysis & Synthesis Instructions
41
-
42
- ### 1. Define the Atmosphere
43
- Evaluate the target project's intent. Use evocative adjectives from the taste spectrum:
44
- - **Density:** "Art Gallery Airy" (1–3) → "Daily App Balanced" (4–7) → "Cockpit Dense" (8–10)
45
- - **Variance:** "Predictable Symmetric" (1–3) → "Offset Asymmetric" (4–7) → "Artsy Chaotic" (8–10)
46
- - **Motion:** "Static Restrained" (1–3) → "Fluid CSS" (4–7) → "Cinematic Choreography" (8–10)
47
-
48
- Default baseline: Variance 8, Motion 6, Density 4. Adapt dynamically based on user's vibe description.
49
-
50
- ### 2. Map the Color Palette
51
- For each color provide: **Descriptive Name** + **Hex Code** + **Functional Role**.
52
-
53
- **Mandatory constraints:**
54
- - Maximum 1 accent color. Saturation below 80%
55
- - The "AI Purple/Blue Neon" aesthetic is strictly BANNED — no purple button glows, no neon gradients
56
- - Use absolute neutral bases (Zinc/Slate) with high-contrast singular accents
57
- - Stick to one palette for the entire output — no warm/cool gray fluctuation
58
- - Never use pure black (`#000000`) — use Off-Black, Zinc-950, or Charcoal
59
-
60
- ### 3. Establish Typography Rules
61
- - **Display/Headlines:** Track-tight, controlled scale. Not screaming. Hierarchy through weight and color, not just massive size
62
- - **Body:** Relaxed leading, max 65 characters per line
63
- - **Font Selection:** `Inter` is BANNED for premium/creative contexts. Force unique character: `Geist`, `Outfit`, `Cabinet Grotesk`, or `Satoshi`
64
- - **Serif Ban:** Generic serif fonts (`Times New Roman`, `Georgia`, `Garamond`, `Palatino`) are BANNED. If serif is needed for editorial/creative contexts, use only distinctive modern serifs: `Fraunces`, `Gambarino`, `Editorial New`, or `Instrument Serif`. Serif is always BANNED in dashboards or software UIs
65
- - **Dashboard Constraint:** Use Sans-Serif pairings exclusively (`Geist` + `Geist Mono` or `Satoshi` + `JetBrains Mono`)
66
- - **High-Density Override:** When density exceeds 7, all numbers must use Monospace
67
-
68
- ### 4. Define the Hero Section
69
- The Hero is the first impression and must be creative, striking, and never generic:
70
- - **Inline Image Typography:** Embed small, contextual photos or visuals directly between words or letters in the headline. Images sit inline at type-height, rounded, acting as visual punctuation. This is the signature creative technique
71
- - **No Overlapping:** Text must never overlap images or other text. Every element occupies its own clean spatial zone
72
- - **No Filler Text:** "Scroll to explore", "Swipe down", scroll arrow icons, bouncing chevrons are BANNED. The content should pull users in naturally
73
- - **Asymmetric Structure:** Centered Hero layouts BANNED when variance exceeds 4
74
- - **CTA Restraint:** Maximum one primary CTA. No secondary "Learn more" links
75
-
76
- ### 5. Describe Component Stylings
77
- For each component type, describe shape, color, shadow depth, and interaction behavior:
78
- - **Buttons:** Tactile push feedback on active state. No neon outer glows. No custom mouse cursors
79
- - **Cards:** Use ONLY when elevation communicates hierarchy. Tint shadows to background hue. For high-density layouts, replace cards with border-top dividers or negative space
80
- - **Inputs/Forms:** Label above input, helper text optional, error text below. Standard gap spacing
81
- - **Loading States:** Skeletal loaders matching layout dimensions — no generic circular spinners
82
- - **Empty States:** Composed compositions indicating how to populate data
83
- - **Error States:** Clear, inline error reporting
84
-
85
- ### 6. Define Layout Principles
86
- - No overlapping elements — every element occupies its own clear spatial zone. No absolute-positioned content stacking
87
- - Centered Hero sections are BANNED when variance exceeds 4 — force Split Screen, Left-Aligned, or Asymmetric Whitespace
88
- - The generic "3 equal cards horizontally" feature row is BANNED — use 2-column Zig-Zag, asymmetric grid, or horizontal scroll
89
- - CSS Grid over Flexbox math — never use `calc()` percentage hacks
90
- - Contain layouts using max-width constraints (e.g., 1400px centered)
91
- - Full-height sections must use `min-h-[100dvh]` — never `h-screen` (iOS Safari catastrophic jump)
92
-
93
- ### 7. Define Responsive Rules
94
- Every design must work across all viewports:
95
- - **Mobile-First Collapse (< 768px):** All multi-column layouts collapse to single column. No exceptions
96
- - **No Horizontal Scroll:** Horizontal overflow on mobile is a critical failure
97
- - **Typography Scaling:** Headlines scale via `clamp()`. Body text minimum `1rem`/`14px`
98
- - **Touch Targets:** All interactive elements minimum `44px` tap target
99
- - **Image Behavior:** Inline typography images (photos between words) stack below headline on mobile
100
- - **Navigation:** Desktop horizontal nav collapses to clean mobile menu
101
- - **Spacing:** Vertical section gaps reduce proportionally (`clamp(3rem, 8vw, 6rem)`)
102
-
103
- ### 8. Encode Motion Philosophy
104
- - **Spring Physics default:** `stiffness: 100, damping: 20` — premium, weighty feel. No linear easing
105
- - **Perpetual Micro-Interactions:** Every active component should have an infinite loop state (Pulse, Typewriter, Float, Shimmer)
106
- - **Staggered Orchestration:** Never mount lists instantly — use cascade delays for waterfall reveals
107
- - **Performance:** Animate exclusively via `transform` and `opacity`. Never animate `top`, `left`, `width`, `height`. Grain/noise filters on fixed pseudo-elements only
108
-
109
- ### 9. List Anti-Patterns (AI Tells)
110
- Encode these as explicit "NEVER DO" rules in the DESIGN.md:
111
- - No emojis anywhere
112
- - No `Inter` font
113
- - No generic serif fonts (`Times New Roman`, `Georgia`, `Garamond`) — distinctive modern serifs only if needed
114
- - No pure black (`#000000`)
115
- - No neon/outer glow shadows
116
- - No oversaturated accents
117
- - No excessive gradient text on large headers
118
- - No custom mouse cursors
119
- - No overlapping elements — clean spatial separation always
120
- - No 3-column equal card layouts
121
- - No generic names ("John Doe", "Acme", "Nexus")
122
- - No fake round numbers (`99.99%`, `50%`)
123
- - No AI copywriting clichés ("Elevate", "Seamless", "Unleash", "Next-Gen")
124
- - No filler UI text: "Scroll to explore", "Swipe down", scroll arrows, bouncing chevrons
125
- - No broken Unsplash links — use `picsum.photos` or SVG avatars
126
- - No centered Hero sections (for high-variance projects)
127
-
128
- ## Output Format (DESIGN.md Structure)
129
-
130
- ```markdown
131
- # Design System: [Project Title]
132
-
133
- ## 1. Visual Theme & Atmosphere
134
- (Evocative description of the mood, density, variance, and motion intensity.
135
- Example: "A restrained, gallery-airy interface with confident asymmetric layouts
136
- and fluid spring-physics motion. The atmosphere is clinical yet warm — like a
137
- well-lit architecture studio.")
138
-
139
- ## 2. Color Palette & Roles
140
- - **Canvas White** (#F9FAFB) — Primary background surface
141
- - **Pure Surface** (#FFFFFF) — Card and container fill
142
- - **Charcoal Ink** (#18181B) — Primary text, Zinc-950 depth
143
- - **Muted Steel** (#71717A) — Secondary text, descriptions, metadata
144
- - **Whisper Border** (rgba(226,232,240,0.5)) — Card borders, 1px structural lines
145
- - **[Accent Name]** (#XXXXXX) — Single accent for CTAs, active states, focus rings
146
- (Max 1 accent. Saturation < 80%. No purple/neon.)
147
-
148
- ## 3. Typography Rules
149
- - **Display:** [Font Name] — Track-tight, controlled scale, weight-driven hierarchy
150
- - **Body:** [Font Name] — Relaxed leading, 65ch max-width, neutral secondary color
151
- - **Mono:** [Font Name] — For code, metadata, timestamps, high-density numbers
152
- - **Banned:** Inter, generic system fonts for premium contexts. Serif fonts banned in dashboards.
153
-
154
- ## 4. Component Stylings
155
- * **Buttons:** Flat, no outer glow. Tactile -1px translate on active. Accent fill for primary, ghost/outline for secondary.
156
- * **Cards:** Generously rounded corners (2.5rem). Diffused whisper shadow. Used only when elevation serves hierarchy. High-density: replace with border-top dividers.
157
- * **Inputs:** Label above, error below. Focus ring in accent color. No floating labels.
158
- * **Loaders:** Skeletal shimmer matching exact layout dimensions. No circular spinners.
159
- * **Empty States:** Composed, illustrated compositions — not just "No data" text.
160
-
161
- ## 5. Layout Principles
162
- (Grid-first responsive architecture. Asymmetric splits for Hero sections.
163
- Strict single-column collapse below 768px. Max-width containment.
164
- No flexbox percentage math. Generous internal padding.)
165
-
166
- ## 6. Motion & Interaction
167
- (Spring physics for all interactive elements. Staggered cascade reveals.
168
- Perpetual micro-loops on active dashboard components. Hardware-accelerated
169
- transforms only. Isolated Client Components for CPU-heavy animations.)
170
-
171
- ## 7. Anti-Patterns (Banned)
172
- (Explicit list of forbidden patterns: no emojis, no Inter, no pure black,
173
- no neon glows, no 3-column equal grids, no AI copywriting clichés,
174
- no generic placeholder names, no broken image links.)
175
- ```
176
-
177
- ## Best Practices
178
- - **Be Descriptive:** "Deep Charcoal Ink (#18181B)" — not just "dark text"
179
- - **Be Functional:** Explain what each element is used for
180
- - **Be Consistent:** Same terminology throughout the document
181
- - **Be Precise:** Include exact hex codes, rem values, pixel values in parentheses
182
- - **Be Opinionated:** This is not a neutral template — it enforces a specific, premium aesthetic
183
-
184
- ## Tips for Success
185
- 1. Start with the atmosphere — understand the vibe before detailing tokens
186
- 2. Look for patterns — identify consistent spacing, sizing, and styling
187
- 3. Think semantically — name colors by purpose, not just appearance
188
- 4. Consider hierarchy — document how visual weight communicates importance
189
- 5. Encode the bans — anti-patterns are as important as the rules themselves
190
-
191
- ## Common Pitfalls to Avoid
192
- - Using technical jargon without translation ("rounded-xl" instead of "generously rounded corners")
193
- - Omitting hex codes or using only descriptive names
194
- - Forgetting functional roles of design elements
195
- - Being too vague in atmosphere descriptions
196
- - Ignoring the anti-pattern list — these are what make the output premium
197
- - Defaulting to generic "safe" designs instead of enforcing the curated aesthetic