--- name: stitch-design-taste description: "Stitch Design Taste \u2014 Semantic Design System Skill workflow skill. Use this skill when the user needs generating Google Stitch DESIGN.md systems for premium typography, color, layout, motion intent, and anti-generic UI rules and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off." version: "0.0.1" category: frontend tags: ["stitch", "design-system", "frontend", "ui", "stitch-design-taste", "generating", "google", "design"] complexity: advanced risk: safe tools: ["cursor", "antigravity", "codex-cli", "claude-code", "gemini-cli", "opencode"] source: community author: "Leonxlnx" date_added: "2026-04-18" date_updated: "2026-04-25" --- # Stitch Design Taste — Semantic Design System Skill ## Overview This public intake copy packages `plugins/antigravity-awesome-skills-claude/skills/stitch-design-taste` from `https://github.com/sickn33/antigravity-awesome-skills` into the native Omni Skills editorial shape without hiding its origin. Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow. This intake keeps the copied upstream files intact and uses the `external_source` block in `metadata.json` plus `ORIGIN.md` as the provenance anchor for review. # Stitch Design Taste — Semantic Design System Skill Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Limitations, Prerequisites, The Goal, Analysis & Synthesis Instructions, Output Format (DESIGN.md Structure), 1. Visual Theme & Atmosphere. ## When to Use This Skill Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request. - Use when the user wants a Google Stitch-compatible DESIGN.md or semantic design system for AI screen generation. - Use when translating premium frontend taste rules into Stitch-friendly visual descriptions, color roles, typography specs, and component behavior. - Use when the design system must prevent generic AI UI patterns before screens are generated. - Use when the request clearly matches the imported source intent: generating Google Stitch DESIGN.md systems for premium typography, color, layout, motion intent, and anti-generic UI rules. - Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch. - Use when provenance needs to stay visible in the answer, PR, or review packet. ## Operating Table | Situation | Start here | Why it matters | | --- | --- | --- | | First-time use | `metadata.json` | Confirms repository, branch, commit, and imported path through the `external_source` block before touching the copied workflow | | Provenance review | `ORIGIN.md` | Gives reviewers a plain-language audit trail for the imported source | | Workflow execution | `DESIGN.md` | Starts with the smallest copied file that materially changes execution | | Supporting context | `DESIGN.md` | Adds the next most relevant copied source file without loading the entire package | | Handoff decision | `## Related Skills` | Helps the operator switch to a stronger native skill when the task drifts | ## Workflow This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow. 1. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task. 2. Read the overview and provenance files before loading any copied upstream support files. 3. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request. 4. Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes. 5. Validate the result against the upstream expectations and the evidence you can point to in the copied files. 6. Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity. 7. Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify. ### Imported Workflow Notes #### Imported: 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. #### Imported: Limitations - This skill produces semantic design-system guidance for Stitch; it does not guarantee Stitch will render every constraint exactly. - Generated `DESIGN.md` files still require review against the actual product brief, brand constraints, accessibility needs, and screen content. - Motion sections document implementation intent for later coding agents because Stitch itself may generate static screens. ## Examples ### Example 1: Ask for the upstream workflow directly ```text Use @stitch-design-taste to handle . Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer. ``` **Explanation:** This is the safest starting point when the operator needs the imported workflow, but not the entire repository. ### Example 2: Ask for a provenance-grounded review ```text Review @stitch-design-taste against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why. ``` **Explanation:** Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection. ### Example 3: Narrow the copied support files before execution ```text Use @stitch-design-taste for . Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding. ``` **Explanation:** This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default. ### Example 4: Build a reviewer packet ```text Review @stitch-design-taste using the copied upstream files plus provenance, then summarize any gaps before merge. ``` **Explanation:** This is useful when the PR is waiting for human review and you want a repeatable audit packet. ## Best Practices Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution. - 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. - 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 ### Imported Operating Notes #### Imported: 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. #### Imported: 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.) #### Imported: 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 ## Troubleshooting ### Problem: The operator skipped the imported context and answered too generically **Symptoms:** The result ignores the upstream workflow in `plugins/antigravity-awesome-skills-claude/skills/stitch-design-taste`, fails to mention provenance, or does not use any copied source files at all. **Solution:** Re-open `metadata.json`, `ORIGIN.md`, and the most relevant copied upstream files. Check the `external_source` block first, then restate the provenance before continuing. ### Problem: The imported workflow feels incomplete during review **Symptoms:** Reviewers can see the generated `SKILL.md`, but they cannot quickly tell which references, examples, or scripts matter for the current task. **Solution:** Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it. ### Problem: The task drifted into a different specialization **Symptoms:** The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. **Solution:** Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind. ## Related Skills - `@00-andruia-consultant` - Use when the work is better handled by that native specialization after this imported skill establishes context. - `@00-andruia-consultant-v2` - Use when the work is better handled by that native specialization after this imported skill establishes context. - `@10-andruia-skill-smith` - Use when the work is better handled by that native specialization after this imported skill establishes context. - `@10-andruia-skill-smith-v2` - Use when the work is better handled by that native specialization after this imported skill establishes context. ## Additional Resources Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding. | Resource family | What it gives the reviewer | Example path | | --- | --- | --- | | `references` | copied reference notes, guides, or background material from upstream | `references/n/a` | | `examples` | worked examples or reusable prompts copied from upstream | `examples/n/a` | | `scripts` | upstream helper scripts that change execution or validation | `scripts/n/a` | | `agents` | routing or delegation notes that are genuinely part of the imported package | `agents/n/a` | | `assets` | supporting assets or schemas copied from the source package | `assets/n/a` | - [DESIGN.md](DESIGN.md) ### Imported Reference Notes #### Imported: Prerequisites - Access to Google Stitch via [labs.google.com/stitch](https://labs.google.com/stitch) - Optionally: Stitch MCP Server for programmatic integration with Cursor, Antigravity, or Gemini CLI #### Imported: The Goal Generate a `DESIGN.md` file that encodes: 1. **Visual atmosphere** — the mood, density, and design philosophy 2. **Color calibration** — neutrals, accents, and banned patterns with hex codes 3. **Typographic architecture** — font stacks, scale hierarchy, and anti-patterns 4. **Component behaviors** — buttons, cards, inputs with interaction states 5. **Layout principles** — grid systems, spacing philosophy, responsive strategy 6. **Motion philosophy** — animation engine specs, spring physics, perpetual micro-interactions 7. **Anti-patterns** — explicit list of banned AI design clichés #### Imported: 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 - **Spring Physics default:** `stiffness: 100, damping: 20` — premium, weighty feel. No linear easing - **Perpetual Micro-Interactions:** Every active component should have an infinite loop state (Pulse, Typewriter, Float, Shimmer) - **Staggered Orchestration:** Never mount lists instantly — use cascade delays for waterfall reveals - **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) #### Imported: Output Format (DESIGN.md Structure) ```markdown # Design System: [Project Title] #### Imported: 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.") #### Imported: 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.) #### Imported: 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. #### Imported: 6. Motion & Interaction (Spring physics for all interactive elements. Staggered cascade reveals. Perpetual micro-loops on active dashboard components. Hardware-accelerated transforms only. Isolated Client Components for CPU-heavy animations.) #### Imported: 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.) ``` #### Imported: Tips for Success 1. Start with the atmosphere — understand the vibe before detailing tokens 2. Look for patterns — identify consistent spacing, sizing, and styling 3. Think semantically — name colors by purpose, not just appearance 4. Consider hierarchy — document how visual weight communicates importance 5. Encode the bans — anti-patterns are as important as the rules themselves #### Imported: 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