Commands now require context gathering before proceeding:
- bolder: target audience, use-cases, brand personality
- quieter: purpose, audience, what's working
- colorize: brand colors, audience, domain appropriateness
- animate: personality, performance budget, audience
- delight: brand personality, emotional context, appropriateness
- simplify: what's essential vs nice-to-have
Each command now:
1. Gathers context from thread/codebase first
2. MUST ask user if inference confidence is medium or lower
3. MUST use frontend-design skill before proceeding
4. Has visual separator (---) as hard gate before design work
This prevents AI slop by ensuring commands have proper context
before making design decisions.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Monospace is fine when used intentionally - the issue is lazy "dev tool"
defaults, not the typeface itself.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Added explicit AI SLOP TRAP warning before planning
- Removed "monospace as accent" suggestion (contradicts skill)
- Replaced glassmorphism with grain, halftone, duotone alternatives
- Added anti-slop caveats to shadows and borders suggestions
- Added "NOT AI slop" as first verification check
- Added "the test" to verify section
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Commands now say "Use the frontend-design skill" instead of passive note
- Skill's Design Thinking section now has explicit MUST-know checklist
- Added ask instruction to bolder command for context gathering
- AskUserQuestionTool instruction is now more prominent and imperative
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Paul BakausandClaude Opus 4.5