stitch-design-taste

Generate DESIGN.md files encoding UI design language for Stitch projects.

4|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/fysoul17/one-query-v1 --skill stitch-design-taste-fysoul17
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stitch-design-taste
Source: https://github.com/fysoul17/one-query-v1/tree/main/.agents/skills/stitch-design-taste
Command: npx skills add https://github.com/fysoul17/one-query-v1 --skill stitch-design-taste-fysoul17

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill generates DESIGN.md files that codify a premium, non-generic UI design language for Stitch, ensuring consistent, high-agency interfaces.

Core Features & Use Cases

  • Design-language generation: Produces DESIGN.md containing atmosphere, color calibration, typography, component behaviors, layout principles, and motion philosophy.
  • Single source of truth: Provides a central design brief for Stitch-driven screen generation to avoid drift.
  • Use Case: When designing a dashboard or admin panel, generate DESIGN.md to lock in visual language before implementation.

Quick Start

Generate a DESIGN.md that encodes the target project's mood, color tokens, typography, and motion rules.

Frequently Asked Questions about stitch-design-taste

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

FAQPage Schema
How do I codify a UI design language for consistent screen generation?

A design system prevents visual drift by providing a central DESIGN.md brief. It locks in color calibration, typography, component behaviors, and motion philosophy before implementation, ensuring consistent, high-agency interfaces across dashboards and admin panels.

What is a DESIGN.md file and how does it define UI typography and color tokens?

A DESIGN.md file defines premium UI typography and color tokens by explicitly documenting atmosphere, color calibration, and typography architecture. It acts as a comprehensive design brief encoding visual rules for consistent interface generation.

How do I generate design system rules for dashboards and admin panels?

Generate dashboard design system rules by producing a DESIGN.md file specifying layout principles, component behaviors, and explicit anti-pattern prohibitions. This ensures premium, non-generic interfaces tailored for admin panel contexts.

Can I use a design brief to prevent UI drift across marketing pages and dashboards?

Yes, a design brief prevents UI drift across marketing pages and dashboards by serving as a single source of truth. It codifies motion philosophy and component behaviors so generated screens maintain a consistent visual language.

Does codifying UI motion philosophy require defining anti-pattern rules?

Codifying UI motion philosophy requires defining anti-pattern rules to establish explicit prohibitions. Including these constraints in the DESIGN.md ensures generated interfaces avoid generic behaviors and maintain the intended premium atmosphere.

When should I not use a single-source-of-truth design document for UI generation?

You should not use a single-source-of-truth design document when a project requires highly experimental, unconstrained visual exploration. The strict anti-pattern prohibitions and codified tokens limit spontaneous stylistic deviation during UI generation.