taste-feedback
Live Taste Feedback
The standard Designpowers pipeline catches taste mismatches at critique — after the full build is done. That's expensive. A wrong colour palette discovered after 8 components are built means rebuilding all 8. This skill interrupts the build at strategic moments to show intermediate output and ask: "Is this heading in the right direction?"
When to Use
- During
design-builderexecution, at natural visual checkpoints - When the build involves subjective aesthetic decisions (colour, typography, spacing, tone)
- When the taste profile has soft patterns but no strong opinions for this decision
- When the project is new and the system has limited taste data for this user
- When the design-lead's direction was based on interpretation, not explicit user instruction
Do Not Use When
- The user is in auto mode and hasn't opted into taste checks
- The build is purely structural (data models, API integration, routing)
- The taste profile has strong opinions that already constrain this decision
- The user has explicitly said "just build it, I'll review at the end"
More from owl-listener/designpowers
adaptive-interfaces
Use when designing for user preferences — motion sensitivity, contrast needs, colour schemes, text sizing, information density, or any interface behaviour that should adapt to individual needs
6token-architecture
Use when building or restructuring design token systems — global tokens, semantic tokens, component tokens, naming conventions, theming, and multi-platform token distribution
6motion-choreography
Use when designing animation sequences, page transitions, micro-interactions, loading states, or any motion that communicates meaning — ensures motion is purposeful, performant, and safe for motion-sensitive users
6design-discovery
You MUST use this before any creative or design work — building features, creating components, designing interfaces, modifying user-facing behaviour. Explores intent, constraints, users, and context before any design decisions are made
6responsive-patterns
Use when designing complex responsive layouts — breakpoint strategy, layout shifts, content reflow, responsive typography, container queries, and ensuring the experience works across the full device spectrum
6design-memory
Use when starting a new project or when taste decisions are made — accumulates the user's aesthetic preferences, recurring patterns, and design instincts across projects so each new project starts with what the system already knows about their taste
6