⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
absence-audit
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.
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
Taste-Skills
Agent skills for design taste and visual judgment. Help AI coding agents evaluate hierarchy, typography, color, spacing, interaction quality, and the invisible decisions that separate good design from great design before they ship.
⚠️ Experimental Software. This project is in active development. Skills may change or break without notice. Not professional advice. All output requires human review. Do your own research. Read full disclaimer → | Full terms →
Why
Agents can build interfaces. They can't tell if the interface is any good. They don't notice when the hierarchy is flat, the spacing is inconsistent, or the typography sends the wrong signal. These skills fill that gap.
Each skill is a set of opinionated constraints and patterns. When an agent uses them, it checks its own output against taste principles before shipping anything.
This is not a design system. Not a component library. This is the judgment layer.
Install
# Add all skills
npx github:0xDragoon/taste-skills add --all
# Add a specific skill
npx github:0xDragoon/taste-skills add hierarchy-principles
# Add multiple skills
npx github:0xDragoon/taste-skills add critique-vocabulary type-selection spatial-rhythm
# List available skills
npx github:0xDragoon/taste-skills list
# Show skill details
npx github:0xDragoon/taste-skills info hierarchy-principles
# Custom directory
npx github:0xDragoon/taste-skills add --all --dir ./agent-skills
Skills are installed to .taste-skills/ by default. Point your agent to this directory.
Compatibility
Works with any agent that supports SKILL.md files:
- Claude Code
- Cursor
- Windsurf
- OpenCode
- Cline
- Codex
- Aider
- Continue
Skills
Perception (5)
| Skill | Description |
|---|---|
visual-audit | The 10-second audit. Look at any design and name what's working and what's not, fast. |
detail-observation | Micro-decision analysis. Catalog the border radii, spacing scales, and type sizes nobody else notices. |
cross-domain-seeing | Pull design principles from architecture, fashion, film, and physical spaces into screen design. |
screenshot-surgery | Annotate and map the anatomy of any design. Hierarchy, spacing, color roles, tension points. |
consumption-discipline | Structured exposure habits for building taste. Consume more than you create, actively and across domains. |
Judgment (6)
| Skill | Description |
|---|---|
design-ranking | Rank multiple solutions and explain why. Separate preference from quality. |
taste-vs-trends | Tell the difference between decisions that age well and decisions that follow the crowd. |
constraint-evaluation | Understand the constraints a design was built under and evaluate quality within that context. |
tradeoff-assessment | Name what was prioritized, what was sacrificed, and whether the tradeoff was right. |
taste-gap | Navigate the gap between what you can see and what you can make. The Ira Glass gap. |
taste-as-strategy | Use taste as a competitive moat. In the AI era, execution is commoditized. Taste is the edge. |
Analysis (4)
| Skill | Description |
|---|---|
decision-tracing | Reverse-engineer why a design decision was made. Observation to inference. |
absence-audit | Notice what's deliberately missing. Restraint is a taste signal. |
version-archaeology | Study how products evolve over time. The decisions that survive redesigns are the taste decisions. |
system-deconstruction | Break a design system into its constituent decisions and evaluate each one. |
Articulation (4)
| Skill | Description |
|---|---|
critique-vocabulary | Precise language for design feedback. Ban vague words. Name what you actually see. |
design-rationale | Defend a design decision to skeptical stakeholders with structure and evidence. |
audience-translation | Explain the same design observation to a designer, a developer, and a non-technical stakeholder. |
written-critique | Write a structured design review that someone can act on without follow-up questions. |
Visual Language (4)
| Skill | Description |
|---|---|
hierarchy-principles | Visual weight, attention order, and the decisions that guide the eye. |
color-systems | Palette roles, restraint, semantic consistency, and when fewer colors means better design. |
spatial-rhythm | Density, whitespace, rhythm, and how space communicates relationships. |
craft-signals | Consistent radii, pixel-perfect alignment, state coverage, and the details that signal quality. |
Typography (3)
| Skill | Description |
|---|---|
type-selection | Choose typefaces based on voice and context, not trends. |
type-systems | Scale, weight, line height, and tracking as a coherent system. |
type-as-signal | Read a designer's taste through their typography decisions alone. |
Interaction (3)
| Skill | Description |
|---|---|
timing-feedback | Response timing, acknowledgment, and making the interface feel alive. |
flow-patterns | Task sequences, progressive disclosure, and the pacing of an experience. |
motion-design | Animation as communication. Feedback, orientation, emphasis, delight. |
Reference Building (3)
| Skill | Description |
|---|---|
principle-tagging | Tag references by principle, not aesthetic. Build a library you can actually search. |
library-architecture | Build a reference system that returns the right reference in under 60 seconds. |
cross-pollination | Draw from architecture, fashion, music, food, and industrial design to expand your taste range. |
Team Practice (3)
| Skill | Description |
|---|---|
design-critique | Run taste-informed design reviews using Observation → Principle → Question. |
daily-routines | 15-minute daily taste exercises. Monday through Friday. Compound over time. |
teaching-taste | Help other designers develop judgment without imposing your style. |
Evaluation (4)
| Skill | Description |
|---|---|
self-assessment | Diagnose your taste gaps across six skill areas. Know what to practice. |
quality-checklist | Systematic design quality evaluation. Hierarchy, type, color, space, craft, system. |
field-notes | Structured taste breakdowns of real products. The format for making taste legible. |
learning-by-making | Build taste through volume, deliberate failure, and speed. Make things, even when they're bad. |
How skills work
Each skill is a markdown file (SKILL.md) containing constraints and patterns that an agent can follow. When you add a skill to your project, it becomes part of the agent's context and guides its output.
.taste-skills/
├── hierarchy-principles/
│ └── SKILL.md
├── critique-vocabulary/
│ └── SKILL.md
├── type-selection/
│ └── SKILL.md
├── design-critique/
│ └── SKILL.md
├── spatial-rhythm/
│ └── SKILL.md
└── ...
You can edit any skill to fit your specific context. They're just markdown files.
⚠️ Important Notices
Experimental Software
This project is experimental. It has not been independently audited, peer-reviewed, or formally verified. Skills, commands, and behaviors may change or break at any time without notice. Do not rely on this software for production-critical decisions without independent verification and qualified human oversight.
Do Your Own Research (DYOR)
These skills encode opinionated design heuristics, not universal truths. They reflect patterns observed across specific contexts and the subjective experience of the contributors. Every product, market, user base, and aesthetic context is different. Any benchmarks, numbers, or reference points are illustrative approximations only.
- Test all design decisions against your own context and users
- Validate with your own research and testing
- Consult qualified professionals for business-critical design decisions
- No AI-generated output should ship without h
// HOW IT'S BUILT
KEY FILES