Fix skill invocation and make ask instruction more prominent

- 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>

dist/claude-code-prefixed/.claude/commands/i-animate.md

@@ -7,7 +7,7 @@ args:
     required: false
 ---
 
-→ *Apply the frontend-design skill for design principles, if not already in context.*
+**First**: Use the frontend-design skill for design principles and anti-patterns.
 
 Analyze a feature and strategically add animations and micro-interactions that enhance understanding, provide feedback, and create delight.
 

dist/claude-code-prefixed/.claude/commands/i-bolder.md

@@ -7,7 +7,7 @@ args:
     required: false
 ---
 
-→ *Apply the frontend-design skill for design principles, if not already in context.*
+**First**: Use the frontend-design skill for design principles and anti-patterns.
 
 Increase visual impact and personality in designs that are too safe, generic, or visually underwhelming, creating more engaging and memorable experiences.
 
@@ -29,6 +29,8 @@ Analyze what makes the design feel too safe or boring:
    - Who's the audience? (What will resonate?)
    - What are the constraints? (Brand guidelines, accessibility, performance)
 
+If any of these are unclear from the codebase, STOP and call the AskUserQuestionTool to clarify.
+
 **CRITICAL**: "Bolder" doesn't mean chaotic or garish. It means distinctive, memorable, and confident. Think intentional drama, not random chaos.
 
 ## Plan Amplification

dist/claude-code-prefixed/.claude/commands/i-colorize.md

@@ -7,7 +7,7 @@ args:
     required: false
 ---
 
-→ *Apply the frontend-design skill for design principles, if not already in context.*
+**First**: Use the frontend-design skill for design principles and anti-patterns.
 
 Strategically introduce color to designs that are too monochromatic, gray, or lacking in visual warmth and personality.
 

dist/claude-code-prefixed/.claude/commands/i-critique.md

@@ -10,7 +10,7 @@ args:
 
 Conduct a holistic design critique, evaluating whether the interface actually works—not just technically, but as a designed experience. Think like a design director giving feedback.
 
-→ *Apply the frontend-design skill for design principles, if not already in context.*
+**First**: Use the frontend-design skill for design principles and anti-patterns.
 
 ## Design Critique
 

dist/claude-code-prefixed/.claude/commands/i-delight.md

@@ -7,7 +7,7 @@ args:
     required: false
 ---
 
-→ *Apply the frontend-design skill for design principles, if not already in context.*
+**First**: Use the frontend-design skill for design principles and anti-patterns.
 
 Identify opportunities to add moments of joy, personality, and unexpected polish that transform functional interfaces into delightful experiences.
 

dist/claude-code-prefixed/.claude/commands/i-polish.md

@@ -7,7 +7,7 @@ args:
     required: false
 ---
 
-→ *Apply the frontend-design skill for design principles, if not already in context.*
+**First**: Use the frontend-design skill for design principles and anti-patterns.
 
 Perform a meticulous final pass to catch all the small details that separate good work from great work. The difference between shipped and polished.
 

dist/claude-code-prefixed/.claude/commands/i-quieter.md

@@ -7,7 +7,7 @@ args:
     required: false
 ---
 
-→ *Apply the frontend-design skill for design principles, if not already in context.*
+**First**: Use the frontend-design skill for design principles and anti-patterns.
 
 Reduce visual intensity in designs that are too bold, aggressive, or overstimulating, creating a more refined and approachable aesthetic without losing effectiveness.
 

dist/claude-code-prefixed/.claude/commands/i-simplify.md

@@ -7,7 +7,7 @@ args:
     required: false
 ---
 
-→ *Apply the frontend-design skill for design principles, if not already in context.*
+**First**: Use the frontend-design skill for design principles and anti-patterns.
 
 Remove unnecessary complexity from designs, revealing the essential elements and creating clarity through ruthless simplification.
 

dist/claude-code-prefixed/.claude/skills/frontend-design/SKILL.md

@@ -8,7 +8,14 @@ This skill guides creation of distinctive, production-grade frontend interfaces
 
 ## Design Thinking
 
-Great design requires understanding. First, scan available context—README, existing components, brand guidelines, design tokens—to infer purpose, audience, and constraints. If critical context is missing, STOP and call the AskUserQuestionTool to clarify. Don't guess on fundamentals.
+Great design requires understanding. First, scan available context—README, existing components, brand guidelines, design tokens—to infer purpose, audience, and constraints.
+
+**BEFORE writing any code**, you MUST know:
+- Who is the target audience?
+- What is the brand personality or tone?
+- Are there existing design tokens, colors, or fonts to use?
+
+If ANY of these are unclear from the codebase, STOP and call the AskUserQuestionTool to clarify. Don't guess on fundamentals—wrong assumptions lead to generic output.
 
 Then commit to a BOLD aesthetic direction:
 - **Purpose**: What problem does this interface solve? Who uses it?