Skills real projects publish on GitHub, most starred first. Each one says what it will make an agent do before you copy it.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Dragoon0xSkillDragoon0x/taste-skills/skills/analysis/absence-audit/SKILL.md
Notice what's deliberately missing from a design. Restraint is a taste signal. Use when studying minimalist products, evaluating design maturity, or understanding the power of removal.
Dragoon0xSkillDragoon0x/taste-skills/skills/analysis/decision-tracing/SKILL.md
Reverse-engineer why a design decision was made. Move from observation to inference. Use when studying products you admire, learning from competitors, or building analytical design thinking.
Dragoon0xSkillDragoon0x/taste-skills/skills/analysis/system-deconstruction/SKILL.md
Break a design system into its constituent decisions and evaluate each one. Use when auditing design systems, evaluating consistency, or understanding how a product maintains quality at scale.
Dragoon0xSkillDragoon0x/taste-skills/skills/analysis/version-archaeology/SKILL.md
Study how products evolve over time using archived versions. The decisions that survive redesigns are the taste decisions. Use when understanding what's essential vs. cosmetic in a design, or learning from product evolution.
Dragoon0xSkillDragoon0x/taste-skills/skills/articulation/audience-translation/SKILL.md
Explain the same design observation to a designer, a developer, and a non-technical stakeholder. Same insight, three languages. Use when working cross-functionally or presenting design decisions to mixed audiences.
Dragoon0xSkillDragoon0x/taste-skills/skills/articulation/critique-vocabulary/SKILL.md
Precise language for design feedback. Ban vague words. Name what you actually see. Use when giving design feedback, running critiques, or training teams to communicate about quality.
Dragoon0xSkillDragoon0x/taste-skills/skills/articulation/design-rationale/SKILL.md
Defend a design decision to skeptical stakeholders with structure and evidence. Use when presenting design work, writing design documentation, or pushing back on requests to change something.
Dragoon0xSkillDragoon0x/taste-skills/skills/articulation/written-critique/SKILL.md
Write a structured design review that someone can act on without follow-up questions. Use when giving async design feedback, writing portfolio case studies, or documenting design decisions.
Dragoon0xSkillDragoon0x/taste-skills/skills/evaluation/field-notes/SKILL.md
Structured taste breakdowns of real products. The format for making taste observations legible and shareable. Use when analyzing products, writing case studies, documenting design observations, or teaching through example.
Dragoon0xSkillDragoon0x/taste-skills/skills/evaluation/learning-by-making/SKILL.md
Build taste through volume of output, deliberate failure, and speed. Taste cannot be developed by watching. It's sharpened by making, failing, and making again. Use when designing practice routines, breaking through creative blocks, or helping someone move from analysis to execution.
Dragoon0xSkillDragoon0x/taste-skills/skills/evaluation/quality-checklist/SKILL.md
Systematic design quality evaluation. Hierarchy, type, color, space, craft, system. Use when evaluating whether a design is ready to ship, running quality audits, or setting quality standards.
Dragoon0xSkillDragoon0x/taste-skills/skills/evaluation/self-assessment/SKILL.md
Diagnose your taste gaps across six skill areas. Know what to practice. Use when starting a taste development program, checking progress, or identifying specific areas to improve.
Often used withlesson-quiz
Dragoon0xSkillDragoon0x/taste-skills/skills/interaction/flow-patterns/SKILL.md
Task sequences, progressive disclosure, and the pacing of an experience over time. Use when designing multi-step flows, evaluating onboarding, or diagnosing why users get lost.
Dragoon0xSkillDragoon0x/taste-skills/skills/interaction/motion-design/SKILL.md
Animation as communication. Feedback, orientation, emphasis, delight. If motion doesn't serve one of these four purposes, it shouldn't exist. Use when evaluating animation quality, designing transitions, or deciding whether motion adds or subtracts.
Often used withgsap-reactgsap-scrolltriggerdesign-review
Dragoon0xSkillDragoon0x/taste-skills/skills/interaction/timing-feedback/SKILL.md
Response timing, acknowledgment, and making the interface feel alive. Every action deserves a response at the right speed. Use when designing interactions, evaluating responsiveness, or diagnosing why a product feels sluggish or dead.
Dragoon0xSkillDragoon0x/taste-skills/skills/judgment/constraint-evaluation/SKILL.md
Understand the constraints a design was built under and evaluate quality within that context. Use when reviewing work that had limited time, budget, or team size, or when assessing whether constraints were handled well.
Dragoon0xSkillDragoon0x/taste-skills/skills/judgment/design-ranking/SKILL.md
Rank multiple design solutions and explain why. Separate personal preference from quality judgment. Use when comparing design options, evaluating competing approaches, or making design decisions with clear reasoning.
Dragoon0xSkillDragoon0x/taste-skills/skills/judgment/taste-as-strategy/SKILL.md
Use taste as a competitive moat and business advantage. In the AI and vibe-coding era, execution is commoditized. Taste is the defensible edge. Use when advising founders on product differentiation, building product culture, evaluating why some products win despite fewer features, or understanding taste as a strategic asset.
Dragoon0xSkillDragoon0x/taste-skills/skills/judgment/taste-gap/SKILL.md
Navigate the gap between what you can see and what you can make. The Ira Glass gap. Use when a designer is frustrated by the distance between their taste and their output, when mentoring someone through a creative plateau, or when someone is considering quitting because their work doesn't match their vision.
Dragoon0xSkillDragoon0x/taste-skills/skills/judgment/taste-vs-trends/SKILL.md
Tell the difference between design decisions that age well and decisions that follow the crowd. Use when evaluating whether a design choice is principled or fashionable, or when a client asks to 'make it look modern.'
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Open a skill to see its discussion. Reports from people and their agents are coming.
