stitch-design-taste

Generate DESIGN.md files encoding design language for Google Stitch.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/cptunderpantsmoons/contract-hubv1 --skill stitch-design-taste-cptunderpantsmoons
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stitch-design-taste
Source: https://github.com/cptunderpantsmoons/contract-hubv1/tree/main/.agents/skills/stitch-design-taste
Command: npx skills add https://github.com/cptunderpantsmoons/contract-hubv1 --skill stitch-design-taste-cptunderpantsmoons

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Semantic Design prompts and DESIGN.md files often lack a machine-readable standard, leading to inconsistent UI language and slow handoffs. Stitch Design Taste generates DESIGN.md files that encode a premium, anti-generic design language for Google Stitch, providing a single source of truth for prompts and visuals.

Core Features & Use Cases

  • Automated DESIGN.md generation: produces a comprehensive, language-driven specification for UI screens.
  • Color, typography, and layout calibration: codifies tokens, hex values, font stacks, grid rules, and responsive constraints.
  • Agent-ready prompts: creates DESIGN.md optimized for Stitch prompts and downstream tooling.
  • Use Case: Teams can rapidly generate branded prompts for new features with consistent visuals.

Quick Start

Provide a formal DESIGN.md prompt that encodes the premium visual language and anti-generic UI rules described in this guide.

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.md file for Google Stitch?

To generate a DESIGN.md file for Google Stitch, provide a formal design prompt encoding your premium visual language and anti-generic UI rules. The Skill outputs a comprehensive specification covering typography, color tokens, layout, and motion.

What is a design prompt for UI specification and why is it needed?

A design prompt for UI specification encodes consistent typography, color, layout, and motion rules for agent-driven screen generation. It is needed to establish a single source of truth, preventing inconsistent UI language and slow handoffs.

Can I use this to codify a color palette and typography design system?

Yes, you can use it to codify a color palette and typography design system. It calibrates and documents exact hex values, font stacks, grid rules, and responsive constraints directly within the generated design specification.

Does the generated DESIGN.md include responsive constraints and motion philosophy?

Yes, the generated DESIGN.md includes responsive constraints and motion philosophy. It comprehensively documents atmosphere, tokens, component rules, and explicit anti-patterns to enforce a premium, non-generic design language.

What is the best way to document anti-patterns for agent-driven UI generation?

The best way to document anti-patterns for agent-driven UI generation is to encode them explicitly within a machine-readable DESIGN.md file. This ensures downstream programmatic rendering avoids generic visuals and enforces consistent design rules.