Stitch Design Taste
Generates rigorous, non-generic DESIGN.md systems for premium Google Stitch screen generation.
The skill declares only StitchMCP, Read, and Write, giving it a relatively constrained permission surface. However, it does not explain data flows, pre-write confirmation, rollback, or review of generated content, and its core function depends on an external Stitch service. No malicious behavior or clear overreach red line is visible.
The SKILL.md and DESIGN.md are broadly self-consistent and describe inputs, output structure, and error-state guidance. However, there are no skill-specific tests, scripts, abnormal-input handling, or failure messages, and the static-screen limitation creates tension with perpetual-animation requirements. The score is capped below 10 by static calibration.
The target scenario and expected DESIGN.md artifact are clear, and configurable style dials are provided. Non-fit boundaries, semantic trigger conditions, Chinese-language support, and mainland-China reachability are not established; the core Stitch dependency may also be difficult to reach from mainland China.
Information architecture, prerequisites, resource template, Apache-2.0 licensing, and a basic security policy are present. The skill lacks dedicated versioning, changelog, named maintenance responsibility, update path, troubleshooting guidance, and input/output examples; the repository CI shown does not cover this skill.
The skill can turn explicit visual rules into a Stitch-oriented DESIGN.md, and the supplied template is directly usable. Its rules are highly subjective and prescriptive, with no real generated-output evidence or key-path validation for taste-design; manual correction is likely. Static calibration limits this score to 7 or below.
A revision-pinned source, complete skill and resource files, license, and repository-level CI provide some auditability. However, the CI does not cover this skill, and there is no independent test suite, third-party execution evidence, or cross-source corroboration, so evidence remains limited.
- The core function depends on Google Stitch/MCP; confirm service access, credentials, and network reachability in the target environment, particularly from mainland China.
- Although limited, Write access creates DESIGN.md files; confirm the destination and keep a backup before use to avoid overwriting user content.
- Perpetual animation and 60fps requirements are coding-phase guidance and may not be directly realizable when Stitch generates static screens.
- The bans and prescriptive style rules may conflict with accessibility needs, brand guidelines, content-heavy products, or projects requiring a neutral design system.
What does this skill do, and when should you use it?
taste-design is a design utility skill in the stitch-skills repository that generates DESIGN.md files for Google Stitch. It translates visual atmosphere, color, typography, component behavior, layout, responsive rules, motion, and anti-patterns into semantic instructions with precise values. Its approach is strongly opinionated toward premium, anti-generic interfaces, using asymmetric layouts, controlled typography, a single accent color, and hardware-accelerated motion. It requires access to Google Stitch and can optionally use the Stitch MCP Server.
Using StitchMCP, Read, and Write, the skill evaluates a project's intent and produces a DESIGN.md. The document specifies visual atmosphere, functional colors with hex values, typography hierarchy, hero structure, component interactions, grid and responsive behavior, spring-based motion, and explicit bans on common AI-generated design patterns. The resulting file acts as a design source of truth for prompting Stitch to generate new screens.
- A product designer using Google Stitch who wants a design language defined before generating new screens.
- A frontend team creating a marketing or creative site that needs asymmetric layouts, strict typography, and one calibrated accent color.
- A design-system maintainer trying to reduce template-like AI interface patterns.
- A developer integrating Stitch through Cursor, Antigravity, or Gemini CLI who needs a generated DESIGN.md specification.
What are this skill's strengths and limitations?
- Covers the full specification surface from atmosphere and tokens to components, responsiveness, motion, and anti-patterns.
- Includes concrete constraints such as hex colors, a 65ch body width, 44px touch targets, and spring parameters.
- Designed specifically for Google Stitch's semantic DESIGN.md workflow.
- Explicitly bans generic patterns including invented metrics, neon glows, and equal three-column card rows.
- Its usefulness depends on access to Google Stitch and, for MCP integration, a configured Stitch MCP Server.
- The source provides no test suite, success metrics, or cross-client validation evidence.
- It generates DESIGN.md rather than production code or a complete interface.
- Its strong aesthetic constraints may not suit projects requiring conventional, symmetrical, or highly dense visual systems.
How do you install this skill?
The skill is distributed through the stitch-utilities plugin in google-labs-code/stitch-skills. In Codex, the README provides this marketplace command: codex plugin marketplace add google-labs-code/stitch-skills --ref main --sparse .agents/plugins --sparse plugins/stitch-design --sparse plugins/stitch-build --sparse plugins/stitch-utilities, followed by installing stitch-utilities. The selective installation command is: npx skills add google-labs-code/stitch-skills. The source does not provide a dedicated command for installing only taste-design; selective installation may require related Stitch skill dependencies.
How do you use this skill?
Configure and run the Stitch MCP Server and ensure Google Stitch is accessible. After installing the skill in an Agent Skills-compatible client, use a prompt such as: "Generate a premium DESIGN.md with strict typography and calibrated colors." The skill generates DESIGN.md for use as the design specification when prompting Stitch to create screens. The source does not document a specific project-directory placement workflow.