stitch-design-taste

Generates a DESIGN.md specifying semantic UI rules for Stitch screen generation workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of inconsistent, generic, or low-quality UI outputs by encoding an opinionated design system into an agent-readable DESIGN.md spec.

Core Features & Use Cases

  • Semantic design system generation: Produces an agent-friendly DESIGN.md that captures atmosphere, tokens, component behavior, and explicit bans to prevent “AI-slop” UI patterns.
  • Visual calibration with hard constraints: Defines precise color roles, typography rules, and layout/motion philosophies (including responsive breakpoints and interaction motion constraints).
  • Reusable taste enforcement: Acts as a single source of truth so future Stitch screen generations remain aligned to the same premium, asymmetric, no-overlap design language.

Quick Start

Use the stitch-design-taste skill to create a DESIGN.md tailored to your product vibe by specifying your desired density, variance, and motion intent.

Frequently Asked Questions about stitch-design-taste

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

FAQPage Schema
How do I prevent generic AI-slop UI patterns during screen generation?

To prevent generic UI generation, you need an opinionated design language encoding explicit bans and hard constraints. This skill generates a DESIGN.md spec enforcing premium visual rules to stop AI-slop patterns and ensure consistent screen outputs.

What is a semantic design system spec for agent interpretation?

A semantic design system spec for agents is a single source of truth capturing atmosphere, tokens, and component behavior. It provides deterministic guidance using exact functional role values so generation agents can apply consistent visual rules.

How do I enforce consistent typography architecture and responsive layout rules across new screens?

You enforce consistent typography architecture and responsive layout rules by defining a DESIGN.md single source of truth. This spec applies precise color calibration, motion philosophies, and deterministic guidance across all new screen generation workflows.

Can I specify density and motion intent for my design tokens?

Yes, you can specify your desired density, variance, and motion intent. The skill uses these inputs to produce a tailored DESIGN.md defining exact color roles, typography rules, and interaction motion constraints for your product vibe.

Does stitch-design-taste work without external UI component libraries?

Yes, this design taste skill works without external dependencies or UI component libraries. It operates as a standalone semantic layer generating a DESIGN.md to enforce premium, asymmetric, no-overlap design language directly within Stitch workflows.

What are the limitations of using a single source of truth for UI design rules?

A limitation of a single source of truth for UI design rules is that it requires strict adherence to prevent drift. If the generated DESIGN.md is not consistently applied across all new screens, the premium visual and behavioral constraints will degrade.