← EngineeringSuiteCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to EngineeringSuite
Snapshot Sep 30, 2026 · 23:16 UTC · version 1.1.1
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "stitch-design-taste",
"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.",
"included_files": [
{
"relative_path": "DESIGN.md",
"size_in_bytes": 12053
}
],
"skill_md_contents": "---\nname: stitch-design-taste\ndescription: 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.\n---\n\n# Stitch Design Taste — Semantic Design System Skill\n\n## Overview\nThis 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.\n\nThe 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.\n\n## Prerequisites\n- Access to Google Stitch via [labs.google/stitch](https://labs.google/stitch)\n- Optionally: Stitch MCP Server for programmatic integration with Cursor, Antigravity, or Gemini CLI\n\n## The Goal\nGenerate a `DESIGN.md` file that encodes:\n1. **Visual atmosphere** — the mood, density, and design philosophy\n2. **Color calibration** — neutrals, accents, and banned patterns with hex codes\n3. **Typographic architecture** — font stacks, scale hierarchy, and anti-patterns\n4. **Component behaviors** — buttons, cards, inputs with interaction states\n5. **Layout principles** — grid systems, spacing philosophy, responsive strategy\n6. **Motion philosophy** — animation engine specs, spring physics, perpetual micro-interactions\n7. **Anti-patterns** — explicit list of banned AI design clichés\n\n## Analysis & Synthesis Instructions\n\n### 1. Define the Atmosphere\nEvaluate the target project's intent. Use evocative adjectives from the taste spectrum:\n- **Density:** \"Art Gallery Airy\" (1–3) → \"Daily App Balanced\" (4–7) → \"Cockpit Dense\" (8–10)\n- **Variance:** \"Predictable Symmetric\" (1–3) → \"Offset Asymmetric\" (4–7) → \"Artsy Chaotic\" (8–10)\n- **Motion:** \"Static Restrained\" (1–3) → \"Fluid CSS\" (4–7) → \"Cinematic Choreography\" (8–10)\n\nDefault baseline: Variance 8, Motion 6, Density 4. Adapt dynamically based on user's vibe description.\n\n### 2. Map the Color Palette\nFor each color provide: **Descriptive Name** + **Hex Code** + **Functional Role**.\n\n**Mandatory constraints:**\n- Maximum 1 accent color. Saturation below 80%\n- The \"AI Purple/Blue Neon\" aesthetic is strictly BANNED — no purple button glows, no neon gradients\n- Use absolute neutral bases (Zinc/Slate) with high-contrast singular accents\n- Stick to one palette for the entire output — no warm/cool gray fluctuation\n- Never use pure black (`#000000`) — use Off-Black, Zinc-950, or Charcoal\n\n### 3. Establish Typography Rules\n- **Display/Headlines:** Track-tight, controlled scale. Not screaming. Hierarchy through weight and color, not just massive size\n- **Body:** Relaxed leading, max 65 characters per line\n- **Font Selection:** `Inter` is BANNED for premium/creative contexts. Force unique character: `Geist`, `Outfit`, `Cabinet Grotesk`, or `Satoshi`\n- **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\n- **Dashboard Constraint:** Use Sans-Serif pairings exclusively (`Geist` + `Geist Mono` or `Satoshi` + `JetBrains Mono`)\n- **High-Density Override:** When density exceeds 7, all numbers must use Monospace\n\n### 4. Define the Hero Section\nThe Hero is the first impression and must be creative, striking, and never generic:\n- **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\n- **No Overlapping:** Text must never overlap images or other text. Every element occupies its own clean spatial zone\n- **No Filler Text:** \"Scroll to explore\", \"Swipe down\", scroll arrow icons, bouncing chevrons are BANNED. The content should pull users in naturally\n- **Asymmetric Structure:** Centered Hero layouts BANNED when variance exceeds 4\n- **CTA Restraint:** Maximum one primary CTA. No secondary \"Learn more\" links\n\n### 5. Describe Component Stylings\nFor each component type, describe shape, color, shadow depth, and interaction behavior:\n- **Buttons:** Tactile push feedback on active state. No neon outer glows. No custom mouse cursors\n- **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\n- **Inputs/Forms:** Label above input, helper text optional, error text below. Standard gap spacing\n- **Loading States:** Skeletal loaders matching layout dimensions — no generic circular spinners\n- **Empty States:** Composed compositions indicating how to populate data\n- **Error States:** Clear, inline error reporting\n\n### 6. Define Layout Principles\n- No overlapping elements — every element occupies its own clear spatial zone. No absolute-positioned content stacking\n- Centered Hero sections are BANNED when variance exceeds 4 — force Split Screen, Left-Aligned, or Asymmetric Whitespace\n- The generic \"3 equal cards horizontally\" feature row is BANNED — use 2-column Zig-Zag, asymmetric grid, or horizontal scroll\n- CSS Grid over Flexbox math — never use `calc()` percentage hacks\n- Contain layouts using max-width constraints (e.g., 1400px centered)\n- Full-height sections must use `min-h-[100dvh]` — never `h-screen` (iOS Safari catastrophic jump)\n\n### 7. Define Responsive Rules\nEvery design must work across all viewports:\n- **Mobile-First Collapse (< 768px):** All multi-column layouts collapse to single column. No exceptions\n- **No Horizontal Scroll:** Horizontal overflow on mobile is a critical failure\n- **Typography Scaling:** Headlines scale via `clamp()`. Body text minimum `1rem`/`14px`\n- **Touch Targets:** All interactive elements minimum `44px` tap target\n- **Image Behavior:** Inline typography images (photos between words) stack below headline on mobile\n- **Navigation:** Desktop horizontal nav collapses to clean mobile menu\n- **Spacing:** Vertical section gaps reduce proportionally (`clamp(3rem, 8vw, 6rem)`)\n\n### 8. Encode Motion Philosophy\n- **Spring Physics default:** `stiffness: 100, damping: 20` — premium, weighty feel. No linear easing\n- **Perpetual Micro-Interactions:** Every active component should have an infinite loop state (Pulse, Typewriter, Float, Shimmer)\n- **Staggered Orchestration:** Never mount lists instantly — use cascade delays for waterfall reveals\n- **Performance:** Animate exclusively via `transform` and `opacity`. Never animate `top`, `left`, `width`, `height`. Grain/noise filters on fixed pseudo-elements only\n\n### 9. List Anti-Patterns (AI Tells)\nEncode these as explicit \"NEVER DO\" rules in the DESIGN.md:\n- No emojis anywhere\n- No `Inter` font\n- No generic serif fonts (`Times New Roman`, `Georgia`, `Garamond`) — distinctive modern serifs only if needed\n- No pure black (`#000000`)\n- No neon/outer glow shadows\n- No oversaturated accents\n- No excessive gradient text on large headers\n- No custom mouse cursors\n- No overlapping elements — clean spatial separation always\n- No 3-column equal card layouts\n- No generic names (\"John Doe\", \"Acme\", \"Nexus\")\n- No fake round numbers (`99.99%`, `50%`)\n- No AI copywriting clichés (\"Elevate\", \"Seamless\", \"Unleash\", \"Next-Gen\")\n- No filler UI text: \"Scroll to explore\", \"Swipe down\", scroll arrows, bouncing chevrons\n- No broken Unsplash links — use `picsum.photos` or SVG avatars\n- No centered Hero sections (for high-variance projects)\n\n## Output Format (DESIGN.md Structure)\n\n```markdown\n# Design System: [Project Title]\n\n## 1. Visual Theme & Atmosphere\n(Evocative description of the mood, density, variance, and motion intensity.\nExample: \"A restrained, gallery-airy interface with confident asymmetric layouts\nand fluid spring-physics motion. The atmosphere is clinical yet warm — like a\nwell-lit architecture studio.\")\n\n## 2. Color Palette & Roles\n- **Canvas White** (#F9FAFB) — Primary background surface\n- **Pure Surface** (#FFFFFF) — Card and container fill\n- **Charcoal Ink** (#18181B) — Primary text, Zinc-950 depth\n- **Muted Steel** (#71717A) — Secondary text, descriptions, metadata\n- **Whisper Border** (rgba(226,232,240,0.5)) — Card borders, 1px structural lines\n- **[Accent Name]** (#XXXXXX) — Single accent for CTAs, active states, focus rings\n(Max 1 accent. Saturation < 80%. No purple/neon.)\n\n## 3. Typography Rules\n- **Display:** [Font Name] — Track-tight, controlled scale, weight-driven hierarchy\n- **Body:** [Font Name] — Relaxed leading, 65ch max-width, neutral secondary color\n- **Mono:** [Font Name] — For code, metadata, timestamps, high-density numbers\n- **Banned:** Inter, generic system fonts for premium contexts. Serif fonts banned in dashboards.\n\n## 4. Component Stylings\n* **Buttons:** Flat, no outer glow. Tactile -1px translate on active. Accent fill for primary, ghost/outline for secondary.\n* **Cards:** Generously rounded corners (2.5rem). Diffused whisper shadow. Used only when elevation serves hierarchy. High-density: replace with border-top dividers.\n* **Inputs:** Label above, error below. Focus ring in accent color. No floating labels.\n* **Loaders:** Skeletal shimmer matching exact layout dimensions. No circular spinners.\n* **Empty States:** Composed, illustrated compositions — not just \"No data\" text.\n\n## 5. Layout Principles\n(Grid-first responsive architecture. Asymmetric splits for Hero sections.\nStrict single-column collapse below 768px. Max-width containment.\nNo flexbox percentage math. Generous internal padding.)\n\n## 6. Motion & Interaction\n(Spring physics for all interactive elements. Staggered cascade reveals.\nPerpetual micro-loops on active dashboard components. Hardware-accelerated\ntransforms only. Isolated Client Components for CPU-heavy animations.)\n\n## 7. Anti-Patterns (Banned)\n(Explicit list of forbidden patterns: no emojis, no Inter, no pure black,\nno neon glows, no 3-column equal grids, no AI copywriting clichés,\nno generic placeholder names, no broken image links.)\n```\n\n## Best Practices\n- **Be Descriptive:** \"Deep Charcoal Ink (#18181B)\" — not just \"dark text\"\n- **Be Functional:** Explain what each element is used for\n- **Be Consistent:** Same terminology throughout the document\n- **Be Precise:** Include exact hex codes, rem values, pixel values in parentheses\n- **Be Opinionated:** This is not a neutral template — it enforces a specific, premium aesthetic\n\n## Tips for Success\n1. Start with the atmosphere — understand the vibe before detailing tokens\n2. Look for patterns — identify consistent spacing, sizing, and styling\n3. Think semantically — name colors by purpose, not just appearance\n4. Consider hierarchy — document how visual weight communicates importance\n5. Encode the bans — anti-patterns are as important as the rules themselves\n\n## Common Pitfalls to Avoid\n- Using technical jargon without translation (\"rounded-xl\" instead of \"generously rounded corners\")\n- Omitting hex codes or using only descriptive names\n- Forgetting functional roles of design elements\n- Being too vague in atmosphere descriptions\n- Ignoring the anti-pattern list — these are what make the output premium\n- Defaulting to generic \"safe\" designs instead of enforcing the curated aesthetic\n"
}SHA-256: ea15a0818620d825eba826c8321a52443b43ea19810f93680e9c3ae4b5134a56