From bac8696851eef0577243b7bac2335baac1217c70 Mon Sep 17 00:00:00 2001 From: Paul Bakaus Date: Sun, 15 Mar 2026 18:36:17 -0700 Subject: [PATCH] fix: correct AskUserQuestionTool to AskUserQuestion tool The Claude Code tool is called AskUserQuestion, not AskUserQuestionTool. Co-Authored-By: Claude Opus 4.6 (1M context) --- .claude/skills/animate/SKILL.md | 2 +- .claude/skills/bolder/SKILL.md | 2 +- .claude/skills/colorize/SKILL.md | 2 +- .claude/skills/delight/SKILL.md | 2 +- .claude/skills/distill/SKILL.md | 2 +- .claude/skills/quieter/SKILL.md | 2 +- .claude/skills/teach-impeccable/SKILL.md | 4 ++-- scripts/lib/utils.js | 2 +- tests/lib/utils.test.js | 4 ++-- 9 files changed, 11 insertions(+), 11 deletions(-) diff --git a/.claude/skills/animate/SKILL.md b/.claude/skills/animate/SKILL.md index bd49c3267..1a62f93ac 100644 --- a/.claude/skills/animate/SKILL.md +++ b/.claude/skills/animate/SKILL.md @@ -33,7 +33,7 @@ Analyze where motion would improve the experience: - Who's the audience? (Motion-sensitive users? Power users who want speed?) - What matters most? (One hero animation vs many micro-interactions?) -If any of these are unclear from the codebase, STOP and call the AskUserQuestionTool to clarify. +If any of these are unclear from the codebase, STOP and call the AskUserQuestion tool to clarify. **CRITICAL**: Respect `prefers-reduced-motion`. Always provide non-animated alternatives for users who need them. diff --git a/.claude/skills/bolder/SKILL.md b/.claude/skills/bolder/SKILL.md index 503041372..09968c2cb 100644 --- a/.claude/skills/bolder/SKILL.md +++ b/.claude/skills/bolder/SKILL.md @@ -34,7 +34,7 @@ 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. +If any of these are unclear from the codebase, STOP and call the AskUserQuestion tool to clarify. **CRITICAL**: "Bolder" doesn't mean chaotic or garish. It means distinctive, memorable, and confident. Think intentional drama, not random chaos. diff --git a/.claude/skills/colorize/SKILL.md b/.claude/skills/colorize/SKILL.md index 55d9914d8..497ee3ac3 100644 --- a/.claude/skills/colorize/SKILL.md +++ b/.claude/skills/colorize/SKILL.md @@ -34,7 +34,7 @@ Analyze the current state and identify opportunities: - **Wayfinding**: Helping users navigate and understand structure - **Delight**: Moments of visual interest and personality -If any of these are unclear from the codebase, STOP and call the AskUserQuestionTool to clarify. +If any of these are unclear from the codebase, STOP and call the AskUserQuestion tool to clarify. **CRITICAL**: More color ≠ better. Strategic color beats rainbow vomit every time. Every color should have a purpose. diff --git a/.claude/skills/delight/SKILL.md b/.claude/skills/delight/SKILL.md index 75e731268..0c762531d 100644 --- a/.claude/skills/delight/SKILL.md +++ b/.claude/skills/delight/SKILL.md @@ -41,7 +41,7 @@ Identify where delight would enhance (not distract from) the experience: - **Helpful surprises**: Anticipating needs before users ask (productivity tools) - **Sensory richness**: Satisfying sounds, smooth animations (creative tools) -If any of these are unclear from the codebase, STOP and call the AskUserQuestionTool to clarify. +If any of these are unclear from the codebase, STOP and call the AskUserQuestion tool to clarify. **CRITICAL**: Delight should enhance usability, never obscure it. If users notice the delight more than accomplishing their goal, you've gone too far. diff --git a/.claude/skills/distill/SKILL.md b/.claude/skills/distill/SKILL.md index 5f4ecce0e..8ebb43fb7 100644 --- a/.claude/skills/distill/SKILL.md +++ b/.claude/skills/distill/SKILL.md @@ -34,7 +34,7 @@ Analyze what makes the design feel complex or cluttered: - What can be removed, hidden, or combined? - What's the 20% that delivers 80% of value? -If any of these are unclear from the codebase, STOP and call the AskUserQuestionTool to clarify. +If any of these are unclear from the codebase, STOP and call the AskUserQuestion tool to clarify. **CRITICAL**: Simplicity is not about removing features - it's about removing obstacles between users and their goals. Every element should justify its existence. diff --git a/.claude/skills/quieter/SKILL.md b/.claude/skills/quieter/SKILL.md index 3e890074e..b9a8513dd 100644 --- a/.claude/skills/quieter/SKILL.md +++ b/.claude/skills/quieter/SKILL.md @@ -34,7 +34,7 @@ Analyze what makes the design feel too intense: - What's working? (Don't throw away good ideas) - What's the core message? (Preserve what matters) -If any of these are unclear from the codebase, STOP and call the AskUserQuestionTool to clarify. +If any of these are unclear from the codebase, STOP and call the AskUserQuestion tool to clarify. **CRITICAL**: "Quieter" doesn't mean boring or generic. It means refined, sophisticated, and easier on the eyes. Think luxury, not laziness. diff --git a/.claude/skills/teach-impeccable/SKILL.md b/.claude/skills/teach-impeccable/SKILL.md index 214c0041c..450f69675 100644 --- a/.claude/skills/teach-impeccable/SKILL.md +++ b/.claude/skills/teach-impeccable/SKILL.md @@ -21,7 +21,7 @@ Note what you've learned and what remains unclear. ## Step 2: Ask UX-Focused Questions -STOP and call the AskUserQuestionTool to clarify. Focus only on what you couldn't infer from the codebase: +STOP and call the AskUserQuestion tool to clarify. Focus only on what you couldn't infer from the codebase: ### Users & Purpose - Who uses this? What's their context when using it? @@ -66,6 +66,6 @@ Synthesize your findings and the user's answers into a `## Design Context` secti Write this section to `.impeccable.md` in the project root. If the file already exists, update the Design Context section in place. -Then STOP and call the AskUserQuestionTool to clarify. whether they'd also like the Design Context appended to CLAUDE.md. If yes, append or update the section there as well. +Then STOP and call the AskUserQuestion tool to clarify. whether they'd also like the Design Context appended to CLAUDE.md. If yes, append or update the section there as well. Confirm completion and summarize the key design principles that will now guide all future work. \ No newline at end of file diff --git a/scripts/lib/utils.js b/scripts/lib/utils.js index 5838ecf27..ba741dd7d 100644 --- a/scripts/lib/utils.js +++ b/scripts/lib/utils.js @@ -267,7 +267,7 @@ export const PROVIDER_PLACEHOLDERS = { 'claude-code': { model: 'Claude', config_file: 'CLAUDE.md', - ask_instruction: 'STOP and call the AskUserQuestionTool to clarify.' + ask_instruction: 'STOP and call the AskUserQuestion tool to clarify.' }, 'cursor': { model: 'the model', diff --git a/tests/lib/utils.test.js b/tests/lib/utils.test.js index ba8739d3e..5af8cbe99 100644 --- a/tests/lib/utils.test.js +++ b/tests/lib/utils.test.js @@ -620,7 +620,7 @@ describe('replacePlaceholders', () => { test('should replace {{ask_instruction}} with provider-specific value', () => { const result = replacePlaceholders('{{ask_instruction}}', 'claude-code'); - expect(result).toBe('STOP and call the AskUserQuestionTool to clarify.'); + expect(result).toBe('STOP and call the AskUserQuestion tool to clarify.'); const cursorResult = replacePlaceholders('{{ask_instruction}}', 'cursor'); expect(cursorResult).toBe('ask the user directly to clarify what you cannot infer.'); @@ -648,7 +648,7 @@ describe('replacePlaceholders', () => { test('should replace multiple placeholders in the same string', () => { const result = replacePlaceholders('{{model}} uses {{config_file}} and {{ask_instruction}}', 'claude-code'); - expect(result).toBe('Claude uses CLAUDE.md and STOP and call the AskUserQuestionTool to clarify.'); + expect(result).toBe('Claude uses CLAUDE.md and STOP and call the AskUserQuestion tool to clarify.'); }); test('should replace multiple occurrences of the same placeholder', () => {