Stitch Design Taste — Semantic Design System Skill
Overview
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.
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.
Prerequisites
- Access to Google Stitch via labs.google.com/stitch
- Optionally: Stitch MCP Server for programmatic integration with Cursor, Antigravity, or Gemini CLI
Project Constraints Take Precedence
Read the supplied brief and the project's existing design system before choosing values. Use its semantic tokens, components and motion contracts when present; these defaults do not replace an established theme or explicit user direction. If Stitch needs resolved values, obtain them from the inspected token source and record the mapping rather than inventing replacements. For Ceramic projects, follow the repository's manifest/search/inspection and semantic-motion workflow before selecting an adapter.
The Goal
Generate a DESIGN.md file that encodes:
- Visual atmosphere — the mood, density, and design philosophy
- Color calibration — neutrals, accents, and banned patterns with hex codes
- Typographic architecture — font stacks, scale hierarchy, and anti-patterns
- Component behaviors — buttons, cards, inputs with interaction states
- Layout principles — grid systems, spacing philosophy, responsive strategy
- Motion philosophy — purposeful state feedback, semantic motion, and reduced-motion behavior
- Anti-patterns — explicit list of banned AI design clichés
Analysis & Synthesis Instructions
1. Define the Atmosphere
Evaluate the target project's intent. Use evocative adjectives from the taste spectrum:
- Density: "Art Gallery Airy" (1–3) → "Daily App Balanced" (4–7) → "Cockpit Dense" (8–10)
- Variance: "Predictable Symmetric" (1–3) → "Offset Asymmetric" (4–7) → "Artsy Chaotic" (8–10)
- Motion: "Static Restrained" (1–3) → "Fluid CSS" (4–7) → "Cinematic Choreography" (8–10)
Default baseline: Variance 8, Motion 6, Density 4. Adapt dynamically based on user's vibe description.
2. Map the Color Palette
For each color provide: Descriptive Name + Hex Code + Functional Role.
Mandatory constraints:
- Maximum 1 accent color. Saturation below 80%
- The "AI Purple/Blue Neon" aesthetic is strictly BANNED — no purple button glows, no neon gradients
- Use absolute neutral bases (Zinc/Slate) with high-contrast singular accents
- Stick to one palette for the entire output — no warm/cool gray fluctuation
- Never use pure black (
#000000) — use Off-Black, Zinc-950, or Charcoal
3. Establish Typography Rules
- Display/Headlines: Track-tight, controlled scale. Not screaming. Hierarchy through weight and color, not just massive size
- Body: Relaxed leading, max 65 characters per line
- Font Selection:
Inter is BANNED for premium/creative contexts. Force unique character: Geist, Outfit, Cabinet Grotesk, or Satoshi
- 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
- Dashboard Constraint: Use Sans-Serif pairings exclusively (
Geist + Geist Mono or Satoshi + JetBrains Mono)
- High-Density Override: When density exceeds 7, all numbers must use Monospace
4. Define the Hero Section
The Hero is the first impression and must be creative, striking, and never generic:
- 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
- No Overlapping: Text must never overlap images or other text. Every element occupies its own clean spatial zone
- No Filler Text: "Scroll to explore", "Swipe down", scroll arrow icons, bouncing chevrons are BANNED. The content should pull users in naturally
- Asymmetric Structure: Centered Hero layouts BANNED when variance exceeds 4
- CTA Restraint: Maximum one primary CTA. No secondary "Learn more" links
5. Describe Component Stylings
For each component type, describe shape, color, shadow depth, and interaction behavior:
- Buttons: Tactile push feedback on active state. No neon outer glows. No custom mouse cursors
- 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
- Inputs/Forms: Label above input, helper text optional, error text below. Standard gap spacing
- Loading States: Skeletal loaders matching layout dimensions — no generic circular spinners
- Empty States: Composed compositions indicating how to populate data
- Error States: Clear, inline error reporting
6. Define Layout Principles
- No overlapping elements — every element occupies its own clear spatial zone. No absolute-positioned content stacking
- Centered Hero sections are BANNED when variance exceeds 4 — force Split Screen, Left-Aligned, or Asymmetric Whitespace
- The generic "3 equal cards horizontally" feature row is BANNED — use 2-column Zig-Zag, asymmetric grid, or horizontal scroll
- CSS Grid over Flexbox math — never use
calc() percentage hacks
- Contain layouts using max-width constraints (e.g., 1400px centered)
- Full-height sections must use
min-h-[100dvh] — never h-screen (iOS Safari catastrophic jump)
7. Define Responsive Rules
Every design must work across all viewports:
- Mobile-First Collapse (< 768px): All multi-column layouts collapse to single column. No exceptions
- No Horizontal Scroll: Horizontal overflow on mobile is a critical failure
- Typography Scaling: Headlines scale via
clamp(). Body text minimum 1rem/14px
- Touch Targets: All interactive elements minimum
44px tap target
- Image Behavior: Inline typography images (photos between words) stack below headline on mobile
- Navigation: Desktop horizontal nav collapses to clean mobile menu
- Spacing: Vertical section gaps reduce proportionally (
clamp(3rem, 8vw, 6rem))
8. Encode Motion Philosophy
- Motion choice: Use the project's semantic motion contracts. Where none exist, choose timing or springs appropriate to the interaction and the user's direction; do not introduce an animation runtime solely to follow this example.
- Purposeful feedback: An active button does not need an infinite loop. Use finite press/focus/state feedback; reserve persistent animation for a meaningful ongoing state, with an accessible static alternative.
- Reduced motion: Describe a
prefers-reduced-motion: reduce variant that removes nonessential movement and stagger while keeping content and state changes available. Preserve essential status information with text or static indicators.
- List behavior: Make content and controls available immediately. Optional entrance stagger must not delay keyboard access, long-list rendering, or completion of the user's task. Use immediate rendering for reduced motion and where a reveal would impede interaction.
- Performance: Animate exclusively via
transform and opacity. Never animate top, left, width, height. Grain/noise filters on fixed pseudo-elements only
9. List Anti-Patterns (AI Tells)
Encode these as explicit "NEVER DO" rules in the DESIGN.md:
- No emojis anywhere
- No
Inter font
- No generic serif fonts (
Times New Roman, Georgia, Garamond) — distinctive modern serifs only if needed
- No pure black (
#000000)
- No neon/outer glow shadows
- No oversaturated accents
- No excessive gradient text on large headers
- No custom mouse cursors
- No overlapping elements — clean spatial separation always
- No 3-column equal card layouts
- No generic names ("John Doe", "Acme", "Nexus")
- No fake round numbers (
99.99%, 50%)
- No AI copywriting clichés ("Elevate", "Seamless", "Unleash", "Next-Gen")
- No filler UI text: "Scroll to explore", "Swipe down", scroll arrows, bouncing chevrons
- No broken Unsplash links — use
picsum.photos or SVG avatars
- No centered Hero sections (for high-variance projects)
Output Format (DESIGN.md Structure)
# Design System: [Project Title]
## 1. Visual Theme & Atmosphere
(Evocative description of the mood, density, variance, and motion intensity.
Example: "A restrained, gallery-airy interface with confident asymmetric layouts
and fluid spring-physics motion. The atmosphere is clinical yet warm — like a
well-lit architecture studio.")
## 2. Color Palette & Roles
- **Canvas White** (#F9FAFB) — Primary background surface
- **Pure Surface** (#FFFFFF) — Card and container fill
- **Charcoal Ink** (#18181B) — Primary text, Zinc-950 depth
- **Muted Steel** (#71717A) — Secondary text, descriptions, metadata
- **Whisper Border** (rgba(226,232,240,0.5)) — Card borders, 1px structural lines
- **[Accent Name]** (#XXXXXX) — Single accent for CTAs, active states, focus rings
(Max 1 accent. Saturation < 80%. No purple/neon.)
## 3. Typography Rules
- **Display:** [Font Name] — Track-tight, controlled scale, weight-driven hierarchy
- **Body:** [Font Name] — Relaxed leading, 65ch max-width, neutral secondary color
- **Mono:** [Font Name] — For code, metadata, timestamps, high-density numbers
- **Banned:** Inter, generic system fonts for premium contexts. Serif fonts banned in dashboards.
## 4. Component Stylings
* **Buttons:** Flat, no outer glow. Tactile -1px translate on active. Accent fill for primary, ghost/outline for secondary.
* **Cards:** Generously rounded corners (2.5rem). Diffused whisper shadow. Used only when elevation serves hierarchy. High-density: replace with border-top dividers.
* **Inputs:** Label above, error below. Focus ring in accent color. No floating labels.
* **Loaders:** Skeletal shimmer matching exact layout dimensions. No circular spinners.
* **Empty States:** Composed, illustrated compositions — not just "No data" text.
## 5. Layout Principles
(Grid-first responsive architecture. Asymmetric splits for Hero sections.
Strict single-column collapse below 768px. Max-width containment.
No flexbox percentage math. Generous internal padding.)
## 6. Motion & Interaction
(Use inspected project semantic-motion contracts, finite state feedback, and a
reduced-motion variant. Content and controls remain immediately available;
optional stagger never delays interaction. No perpetual idle loops by default.)
## 7. Anti-Patterns (Banned)
(Explicit list of forbidden patterns: no emojis, no Inter, no pure black,
no neon glows, no 3-column equal grids, no AI copywriting clichés,
no generic placeholder names, no broken image links.)
Best Practices
- Be Descriptive: "Deep Charcoal Ink (#18181B)" — not just "dark text"
- Be Functional: Explain what each element is used for
- Be Consistent: Same terminology throughout the document
- Be Precise: Include exact hex codes, rem values, pixel values in parentheses
- Be Opinionated: This is not a neutral template — it enforces a specific, premium aesthetic
Tips for Success
- Start with the atmosphere — understand the vibe before detailing tokens
- Look for patterns — identify consistent spacing, sizing, and styling
- Think semantically — name colors by purpose, not just appearance
- Consider hierarchy — document how visual weight communicates importance
- Encode the bans — anti-patterns are as important as the rules themselves
Common Pitfalls to Avoid
- Using technical jargon without translation ("rounded-xl" instead of "generously rounded corners")
- Omitting hex codes or using only descriptive names
- Forgetting functional roles of design elements
- Being too vague in atmosphere descriptions
- Ignoring the anti-pattern list — these are what make the output premium
- Defaulting to generic "safe" designs instead of enforcing the curated aesthetic
1---2name: stitch-design-taste3description: >-4 Writes a DESIGN.md for Google Stitch: atmosphere, color palette with hex codes and roles,5 typography, component styles, layout and motion rules and banned AI patterns, in Stitch's6 natural-language format so it generates non-generic screens. Use when the user mentions Google7 Stitch or asks for a DESIGN.md for Stitch. Not for building UI code directly (use impeccable).8metadata:9 source: https://skillmd.com/skills/the-utopia-studio/stitch-design-taste10---1112# Stitch Design Taste — Semantic Design System Skill1314## Overview15This 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.1617The 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.1819## Prerequisites20- Access to Google Stitch via [labs.google.com/stitch](https://labs.google.com/stitch)21- Optionally: Stitch MCP Server for programmatic integration with Cursor, Antigravity, or Gemini CLI2223## Project Constraints Take Precedence2425Read the supplied brief and the project's existing design system before choosing values. Use its semantic tokens, components and motion contracts when present; these defaults do not replace an established theme or explicit user direction. If Stitch needs resolved values, obtain them from the inspected token source and record the mapping rather than inventing replacements. For Ceramic projects, follow the repository's manifest/search/inspection and semantic-motion workflow before selecting an adapter.2627## The Goal28Generate a `DESIGN.md` file that encodes:291. **Visual atmosphere** — the mood, density, and design philosophy302. **Color calibration** — neutrals, accents, and banned patterns with hex codes313. **Typographic architecture** — font stacks, scale hierarchy, and anti-patterns324. **Component behaviors** — buttons, cards, inputs with interaction states335. **Layout principles** — grid systems, spacing philosophy, responsive strategy346. **Motion philosophy** — purposeful state feedback, semantic motion, and reduced-motion behavior357. **Anti-patterns** — explicit list of banned AI design clichés3637## Analysis & Synthesis Instructions3839### 1. Define the Atmosphere40Evaluate the target project's intent. Use evocative adjectives from the taste spectrum:41- **Density:** "Art Gallery Airy" (1–3) → "Daily App Balanced" (4–7) → "Cockpit Dense" (8–10)42- **Variance:** "Predictable Symmetric" (1–3) → "Offset Asymmetric" (4–7) → "Artsy Chaotic" (8–10)43- **Motion:** "Static Restrained" (1–3) → "Fluid CSS" (4–7) → "Cinematic Choreography" (8–10)4445Default baseline: Variance 8, Motion 6, Density 4. Adapt dynamically based on user's vibe description.4647### 2. Map the Color Palette48For each color provide: **Descriptive Name** + **Hex Code** + **Functional Role**.4950**Mandatory constraints:**51- Maximum 1 accent color. Saturation below 80%52- The "AI Purple/Blue Neon" aesthetic is strictly BANNED — no purple button glows, no neon gradients53- Use absolute neutral bases (Zinc/Slate) with high-contrast singular accents54- Stick to one palette for the entire output — no warm/cool gray fluctuation55- Never use pure black (`#000000`) — use Off-Black, Zinc-950, or Charcoal5657### 3. Establish Typography Rules58- **Display/Headlines:** Track-tight, controlled scale. Not screaming. Hierarchy through weight and color, not just massive size59- **Body:** Relaxed leading, max 65 characters per line60- **Font Selection:** `Inter` is BANNED for premium/creative contexts. Force unique character: `Geist`, `Outfit`, `Cabinet Grotesk`, or `Satoshi`61- **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 UIs62- **Dashboard Constraint:** Use Sans-Serif pairings exclusively (`Geist` + `Geist Mono` or `Satoshi` + `JetBrains Mono`)63- **High-Density Override:** When density exceeds 7, all numbers must use Monospace6465### 4. Define the Hero Section66The Hero is the first impression and must be creative, striking, and never generic:67- **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 technique68- **No Overlapping:** Text must never overlap images or other text. Every element occupies its own clean spatial zone69- **No Filler Text:** "Scroll to explore", "Swipe down", scroll arrow icons, bouncing chevrons are BANNED. The content should pull users in naturally70- **Asymmetric Structure:** Centered Hero layouts BANNED when variance exceeds 471- **CTA Restraint:** Maximum one primary CTA. No secondary "Learn more" links7273### 5. Describe Component Stylings74For each component type, describe shape, color, shadow depth, and interaction behavior:75- **Buttons:** Tactile push feedback on active state. No neon outer glows. No custom mouse cursors76- **Cards:** Use ONLY when elevation communicates hierarchy. Tint shadows to background hue. For high-density layouts, replace cards with border-top dividers or negative space77- **Inputs/Forms:** Label above input, helper text optional, error text below. Standard gap spacing78- **Loading States:** Skeletal loaders matching layout dimensions — no generic circular spinners79- **Empty States:** Composed compositions indicating how to populate data80- **Error States:** Clear, inline error reporting8182### 6. Define Layout Principles83- No overlapping elements — every element occupies its own clear spatial zone. No absolute-positioned content stacking84- Centered Hero sections are BANNED when variance exceeds 4 — force Split Screen, Left-Aligned, or Asymmetric Whitespace85- The generic "3 equal cards horizontally" feature row is BANNED — use 2-column Zig-Zag, asymmetric grid, or horizontal scroll86- CSS Grid over Flexbox math — never use `calc()` percentage hacks87- Contain layouts using max-width constraints (e.g., 1400px centered)88- Full-height sections must use `min-h-[100dvh]` — never `h-screen` (iOS Safari catastrophic jump)8990### 7. Define Responsive Rules91Every design must work across all viewports:92- **Mobile-First Collapse (< 768px):** All multi-column layouts collapse to single column. No exceptions93- **No Horizontal Scroll:** Horizontal overflow on mobile is a critical failure94- **Typography Scaling:** Headlines scale via `clamp()`. Body text minimum `1rem`/`14px`95- **Touch Targets:** All interactive elements minimum `44px` tap target96- **Image Behavior:** Inline typography images (photos between words) stack below headline on mobile97- **Navigation:** Desktop horizontal nav collapses to clean mobile menu98- **Spacing:** Vertical section gaps reduce proportionally (`clamp(3rem, 8vw, 6rem)`)99100### 8. Encode Motion Philosophy101- **Motion choice:** Use the project's semantic motion contracts. Where none exist, choose timing or springs appropriate to the interaction and the user's direction; do not introduce an animation runtime solely to follow this example.102- **Purposeful feedback:** An active button does not need an infinite loop. Use finite press/focus/state feedback; reserve persistent animation for a meaningful ongoing state, with an accessible static alternative.103- **Reduced motion:** Describe a `prefers-reduced-motion: reduce` variant that removes nonessential movement and stagger while keeping content and state changes available. Preserve essential status information with text or static indicators.104- **List behavior:** Make content and controls available immediately. Optional entrance stagger must not delay keyboard access, long-list rendering, or completion of the user's task. Use immediate rendering for reduced motion and where a reveal would impede interaction.105- **Performance:** Animate exclusively via `transform` and `opacity`. Never animate `top`, `left`, `width`, `height`. Grain/noise filters on fixed pseudo-elements only106107### 9. List Anti-Patterns (AI Tells)108Encode these as explicit "NEVER DO" rules in the DESIGN.md:109- No emojis anywhere110- No `Inter` font111- No generic serif fonts (`Times New Roman`, `Georgia`, `Garamond`) — distinctive modern serifs only if needed112- No pure black (`#000000`)113- No neon/outer glow shadows114- No oversaturated accents115- No excessive gradient text on large headers116- No custom mouse cursors117- No overlapping elements — clean spatial separation always118- No 3-column equal card layouts119- No generic names ("John Doe", "Acme", "Nexus")120- No fake round numbers (`99.99%`, `50%`)121- No AI copywriting clichés ("Elevate", "Seamless", "Unleash", "Next-Gen")122- No filler UI text: "Scroll to explore", "Swipe down", scroll arrows, bouncing chevrons123- No broken Unsplash links — use `picsum.photos` or SVG avatars124- No centered Hero sections (for high-variance projects)125126## Output Format (DESIGN.md Structure)127128```markdown129# Design System: [Project Title]130131## 1. Visual Theme & Atmosphere132(Evocative description of the mood, density, variance, and motion intensity.133Example: "A restrained, gallery-airy interface with confident asymmetric layouts134and fluid spring-physics motion. The atmosphere is clinical yet warm — like a135well-lit architecture studio.")136137## 2. Color Palette & Roles138- **Canvas White** (#F9FAFB) — Primary background surface139- **Pure Surface** (#FFFFFF) — Card and container fill140- **Charcoal Ink** (#18181B) — Primary text, Zinc-950 depth141- **Muted Steel** (#71717A) — Secondary text, descriptions, metadata142- **Whisper Border** (rgba(226,232,240,0.5)) — Card borders, 1px structural lines143- **[Accent Name]** (#XXXXXX) — Single accent for CTAs, active states, focus rings144(Max 1 accent. Saturation < 80%. No purple/neon.)145146## 3. Typography Rules147- **Display:** [Font Name] — Track-tight, controlled scale, weight-driven hierarchy148- **Body:** [Font Name] — Relaxed leading, 65ch max-width, neutral secondary color149- **Mono:** [Font Name] — For code, metadata, timestamps, high-density numbers150- **Banned:** Inter, generic system fonts for premium contexts. Serif fonts banned in dashboards.151152## 4. Component Stylings153* **Buttons:** Flat, no outer glow. Tactile -1px translate on active. Accent fill for primary, ghost/outline for secondary.154* **Cards:** Generously rounded corners (2.5rem). Diffused whisper shadow. Used only when elevation serves hierarchy. High-density: replace with border-top dividers.155* **Inputs:** Label above, error below. Focus ring in accent color. No floating labels.156* **Loaders:** Skeletal shimmer matching exact layout dimensions. No circular spinners.157* **Empty States:** Composed, illustrated compositions — not just "No data" text.158159## 5. Layout Principles160(Grid-first responsive architecture. Asymmetric splits for Hero sections.161Strict single-column collapse below 768px. Max-width containment.162No flexbox percentage math. Generous internal padding.)163164## 6. Motion & Interaction165(Use inspected project semantic-motion contracts, finite state feedback, and a166reduced-motion variant. Content and controls remain immediately available;167optional stagger never delays interaction. No perpetual idle loops by default.)168169## 7. Anti-Patterns (Banned)170(Explicit list of forbidden patterns: no emojis, no Inter, no pure black,171no neon glows, no 3-column equal grids, no AI copywriting clichés,172no generic placeholder names, no broken image links.)173```174175## Best Practices176- **Be Descriptive:** "Deep Charcoal Ink (#18181B)" — not just "dark text"177- **Be Functional:** Explain what each element is used for178- **Be Consistent:** Same terminology throughout the document179- **Be Precise:** Include exact hex codes, rem values, pixel values in parentheses180- **Be Opinionated:** This is not a neutral template — it enforces a specific, premium aesthetic181182## Tips for Success1831. Start with the atmosphere — understand the vibe before detailing tokens1842. Look for patterns — identify consistent spacing, sizing, and styling1853. Think semantically — name colors by purpose, not just appearance1864. Consider hierarchy — document how visual weight communicates importance1875. Encode the bans — anti-patterns are as important as the rules themselves188189## Common Pitfalls to Avoid190- Using technical jargon without translation ("rounded-xl" instead of "generously rounded corners")191- Omitting hex codes or using only descriptive names192- Forgetting functional roles of design elements193- Being too vague in atmosphere descriptions194- Ignoring the anti-pattern list — these are what make the output premium195- Defaulting to generic "safe" designs instead of enforcing the curated aesthetic