Decision tracing
Skill Dragoon0x/taste-skills/skills/analysis/decision-tracing
Agent skills for design taste and visual judgment. Hierarchy, typography, color, spacing, interaction quality, and the invisible decisions that separate good design from great design
npx -y skills add Dragoon0x/taste-skills --skill decision-tracingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
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.
SKILL.md
1.3 KB, as published. Nobody here has run it
Decision Tracing
Look at a decision. Figure out why it was made.
How to use
/decision-tracingApply decision-tracing analysis to any design in this conversation.
Constraints
Trace Structure
- MUST follow: Observation > Decision > Probable Reason
- "The primary font is Inter" > "They chose a geometric sans-serif" > "Data-heavy product needing maximum legibility at small sizes with neutral personality"
- MUST generate at least 5 traces per design screen
- SHOULD acknowledge uncertainty: "probable reason" not "the reason"
- NEVER state intent as fact unless you have insider knowledge
What to Trace
- Typeface selection and type system
- Color palette and color role assignments
- Layout structure and grid decisions
- Spacing and density choices
- Navigation architecture
- What's absent (what they chose NOT to include)
Anti-Patterns
- Assuming the most flattering interpretation of every decision
- Tracing only visual decisions and ignoring structural ones
- Stating reasons as facts without marking them as hypotheses