stitch-design-taste

Generate DESIGN.md files encoding UI language for Google Stitch screen generation.

27|1|Updated Feb 15, 2022
One-click install
npx skills add https://github.com/JoeyMckenzie/joeymckenzie.tech --skill stitch-design-taste-joeymckenzie
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: stitch-design-taste
Source: https://github.com/JoeyMckenzie/joeymckenzie.tech/tree/main/.agents/skills/stitch-design-taste
Command: npx skills add https://github.com/JoeyMckenzie/joeymckenzie.tech --skill stitch-design-taste-joeymckenzie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill generates DESIGN.md files that encode premium, non-generic UI language for Google Stitch screen generation, converting design briefs into a shareable, machine-readable design specification.

Core Features & Use Cases

  • Atmosphere & mood defines the visual atmosphere, density, variance, and motion for a design system.
  • Color calibration produces a single neutral palette with one accent color and explicit roles for backgrounds, surfaces, text, and borders.
  • Typography architecture prescribes font families, scales, line lengths, and accessibility constraints, with banned fonts clearly noted.
  • Component behaviors outlines button, card, input, loader, empty state, and error styles for consistent UI language.
  • Layout & motion documents grid, spacing, responsiveness, and spring-based motion philosophy with performance constraints.
  • Anti-patterns enumerates explicit Never Do rules to maintain premium quality.

Quick Start

Create a DESIGN.md for your project following the atmosphere, color, typography, components, layout, motion, and anti-pattern rules described above.

Frequently Asked Questions about stitch-design-taste

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a design system specification for Google Stitch UI generation?โ–ผ

Generate a design system specification for Google Stitch by creating a DESIGN.md file that encodes premium UI language across atmosphere, color, typography, components, layout, motion, and anti-patterns for screen generation.

What should a design system brief include for web app dashboards and editorial layouts?โ–ผ

A design system brief for web app dashboards and editorial layouts should include atmosphere description, color calibration, typography architecture, component behaviors, layout principles, motion philosophy, and anti-patterns to maintain premium quality.

How does color calibration work when defining a UI design palette?โ–ผ

Color calibration for UI design produces a single neutral palette with one accent color, defining explicit roles for backgrounds, surfaces, text, and borders to ensure consistent visual hierarchy.

Can I use this to enforce typography rules and ban specific fonts in my design system?โ–ผ

Yes, you can enforce typography rules and ban specific fonts. The typography architecture prescribes font families, scales, line lengths, and accessibility constraints, with banned fonts clearly noted in the output.

What are the anti-patterns to avoid when building a premium UI language?โ–ผ

Anti-patterns to avoid when building a premium UI language are explicitly enumerated as Never Do rules within the DESIGN.md file, ensuring the generated screen maintains high quality and avoids generic design outcomes.

Do I need any dependencies to write a DESIGN.md file for motion philosophy and component behaviors?โ–ผ

No dependencies are required to write a DESIGN.md file. It independently documents spring-based motion philosophy, performance constraints, and component behaviors like button, card, input, loader, empty state, and error styles.