opencodekit 0.19.0 → 0.19.1

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