From designpowers
Generates a reflective report of a designer's personal taste and recurring patterns from their taste profile, helping them understand their own design instincts.
How this skill is triggered — by the user, by Claude, or both
Slash command
/designpowers:taste-reportThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A taste report turns the personal taste profile from a lookup table into a mirror. `design-memory` accumulates a designer's portable instincts over many projects; this skill reads that accumulation and reflects it back as something the designer can actually learn from — *how you decide, what you reach for, what you reject, and how that's changed.* It's the moment the system stops just rememberi...
A taste report turns the personal taste profile from a lookup table into a mirror. design-memory accumulates a designer's portable instincts over many projects; this skill reads that accumulation and reflects it back as something the designer can actually learn from — how you decide, what you reach for, what you reject, and how that's changed. It's the moment the system stops just remembering your taste and starts helping you see it.
This report describes the portable taste in ~/.designpowers/taste-profile.md — the instincts that travel with the designer regardless of client. It must not include client- or project-specific signals (the contents of any project's DESIGN.md). A client's required teal accent is that client's taste, not the designer's. If the personal profile is clean (it should be — design-memory's Promotion Gate keeps client specifics out), this is automatic. If you notice client-bound entries that leaked into the personal profile, flag them as contamination rather than reporting them as the designer's taste.
Read ~/.designpowers/taste-profile.md and the project history, then synthesise — don't just reformat the tables. Look for the patterns across entries that the designer might not see themselves.
# How You Design — Taste Report
_Generated [date] · based on [N] projects · [X] strong opinions, [Y] soft patterns_
## In one line
[The single sharpest characterisation of their taste. e.g. "You're a restraint-first
designer who earns every accent and trusts whitespace to do the work."]
## How you decide
[3-5 observations about their decision-making, each with evidence from the profile.
Not what they like — HOW they choose. e.g.:
- "You subtract before you add — your overrides almost always remove an element
rather than restyle it (4 of 5 recorded overrides)."
- "You decide colour last. Type and spacing are settled before accent appears."]
## What you reach for
[Recurring moves — the defaults they return to across projects. The strong opinions
and confirmed soft patterns, framed as instincts not rules.]
## What you reject
[The anti-patterns, synthesised into a point of view. e.g. "You reject anything that
performs friendliness — confetti, mascots, exclamation marks, skeleton 'delight'."]
## How your taste is evolving
[Movement over time from the project history. What's hardened from soft to strong,
what you've changed your mind about, what's newly appearing. e.g. "Your tolerance
for density has risen — early projects favoured sparse layouts, recent ones trust
the user with more on screen."]
## Possible blind spots
[Gentle, honest. Tendencies that could become ruts, or places the profile is thin.
e.g. "Every project leans editorial-serif for personality — worth testing whether
that's taste or habit." Frame as questions, not judgements.]
## Where the signal is thin
[What the profile doesn't yet know — areas with little evidence, so the designer
knows what's well-established vs. a guess. Honesty about confidence.]
design-memory, and the same "evidence over claims" rule applies.~/.designpowers/taste-profile.md and its project history (via design-memory)DESIGN.md as personal taste (that's client taste — see design-md)design-retrospective, once the profile has enough historydesign-memory (the store), design-taste (per-project calibration)npx claudepluginhub owl-listener/designpowersObserves and records design decisions, styles, habits across projects. Use to surface a report on how you design, not to steer future work.
Creates DESIGN_GUIDELINES.md defining customer-specific UI/UX with aesthetic direction, design tokens, typography, color, motion, components, and layouts. Requires CUSTOMER.md; avoids generic AI aesthetics.
Routes aesthetic questions to the right tool: coherence-check, elegance-testing, pattern-detection, or simplicity-analysis. Use when evaluating design, code, or writing for elegance, complexity, or structural patterns.