Stacks Documentation
SkillsChangelog
TeamSponsorsPartnersPostcardwareAwesome StacksContributing

Design taste

Copy page
Copy page as Markdown for LLMs
View as Markdown
View this page as plain text
Open in ChatGPT
Copy content and open ChatGPT
Open in Claude
Copy content and open Claude
Open in Perplexity
Search with Perplexity AI
On this page 3

stacks-design-taste · Design · model-invoked

The flagship design skill and the one to start from. It reads the brief, infers a direction, and ships stx and Crosswind interfaces that do not look templated, governed by three dials (variance, motion, density), an explicit list of AI tells to avoid, and a pre-flight check that has to be honestly tickable before the work is done.

Inside the skill

The sections an agent reads once the skill loads.

    1. BRIEF INFERENCE (Read the Room Before Anything Else)
    1. THE THREE DIALS (Core Configuration)
    1. BRIEF -> FOUNDATION MAP
    1. DEFAULT ARCHITECTURE & CONVENTIONS
    1. DESIGN ENGINEERING DIRECTIVES (Bias Correction)
    1. CONTEXT-AWARE PROACTIVITY (Motion in Stacks)
    1. PERFORMANCE & ACCESSIBILITY GUARDRAILS
    1. DIAL DEFINITIONS (Technical Reference)
    1. DARK MODE PROTOCOL
    1. AI TELLS (Forbidden Patterns)
    1. REFERENCE VOCABULARY (Pattern Names the Agent Should Know)
    1. REDESIGN PROTOCOL
    1. OUTPUT DISCIPLINE
    1. OUT OF SCOPE
    1. FINAL PRE-FLIGHT CHECK
  • Appendix A - Stacks foundation note
  • Appendix B - Glassmorphism: honest web approximation (pure CSS)

Using it

This one is model-invoked. Your agent reaches for it on its own when the task matches, and you can also call it by name:

/stacks-design-taste

Source: stacks-design-taste/SKILL.md. Shadow it for one project with app/Skills/stacks-design-taste/SKILL.md, then re-run buddy setup:ai. See Writing your own.