From ee53ce13f2d8e38a8e7fbfbbebb44824b2d5cfb2 Mon Sep 17 00:00:00 2001 From: seomikewaltman Date: Mon, 2 Feb 2026 23:37:25 -0600 Subject: [PATCH 1/2] Update storage location instructions for design context in teach-impeccable --- .claude/commands/teach-impeccable.md | 25 ++++++++++++++++--- .../.claude/commands/teach-impeccable.md | 25 ++++++++++++++++--- source/commands/teach-impeccable.md | 25 ++++++++++++++++--- 3 files changed, 66 insertions(+), 9 deletions(-) diff --git a/.claude/commands/teach-impeccable.md b/.claude/commands/teach-impeccable.md index 82565a7..d4d7a06 100644 --- a/.claude/commands/teach-impeccable.md +++ b/.claude/commands/teach-impeccable.md @@ -43,7 +43,19 @@ STOP and call the AskUserQuestionTool to clarify. Focus only on what you couldn' Skip questions where the answer is already clear from the codebase exploration. -## Step 3: Write Design Context +## Step 3: Choose Storage Location + +Before writing the design context, ask the user where they'd prefer to store this information: + +STOP and call the AskUserQuestionTool to clarify. +**Where would you like to store the design guidelines?** + +1. **Direct integration**: Add to CLAUDE.md in the project root (immediately available to Claude) +2. **Laravel Boost integration**: Create separate guideline file in `.ai/guidelines/design-context.md` (Laravel Boost will merge into CLAUDE.md when you run `php artisan boost:update`) + +Always present the options in the order listed above. Option 1 is recommended for most projects. Option 2 is only for projects using Laravel Boost's guideline merging system. + +## Step 4: Write Design Context Synthesize your findings and the user's answers into a `## Design Context` section: @@ -63,6 +75,13 @@ Synthesize your findings and the user's answers into a `## Design Context` secti [3-5 principles derived from the conversation that should guide all design decisions] ``` -Write this section to CLAUDE.md in the project root. If the file exists, append or update the Design Context section. +**If user chose option 1**: Write this section to CLAUDE.md in the project root. If the file exists, append or update the Design Context section. + +**If user chose option 2 (Laravel Boost)**: +1. Create the `.ai/guidelines/` directory if it doesn't exist +2. Write the Design Context section to `.ai/guidelines/design-context.md` +3. Inform the user to run `php artisan boost:update` to merge this guideline into their CLAUDE.md + +Confirm completion and summarize the key design principles that will now guide all future work. -Confirm completion and summarize the key design principles that will now guide all future work. \ No newline at end of file +**For Laravel Boost users (option 2):** Remind them to run `php artisan boost:update` to merge the new guideline into their CLAUDE.md. \ No newline at end of file diff --git a/dist/claude-code/.claude/commands/teach-impeccable.md b/dist/claude-code/.claude/commands/teach-impeccable.md index 82565a7..d4d7a06 100644 --- a/dist/claude-code/.claude/commands/teach-impeccable.md +++ b/dist/claude-code/.claude/commands/teach-impeccable.md @@ -43,7 +43,19 @@ STOP and call the AskUserQuestionTool to clarify. Focus only on what you couldn' Skip questions where the answer is already clear from the codebase exploration. -## Step 3: Write Design Context +## Step 3: Choose Storage Location + +Before writing the design context, ask the user where they'd prefer to store this information: + +STOP and call the AskUserQuestionTool to clarify. +**Where would you like to store the design guidelines?** + +1. **Direct integration**: Add to CLAUDE.md in the project root (immediately available to Claude) +2. **Laravel Boost integration**: Create separate guideline file in `.ai/guidelines/design-context.md` (Laravel Boost will merge into CLAUDE.md when you run `php artisan boost:update`) + +Always present the options in the order listed above. Option 1 is recommended for most projects. Option 2 is only for projects using Laravel Boost's guideline merging system. + +## Step 4: Write Design Context Synthesize your findings and the user's answers into a `## Design Context` section: @@ -63,6 +75,13 @@ Synthesize your findings and the user's answers into a `## Design Context` secti [3-5 principles derived from the conversation that should guide all design decisions] ``` -Write this section to CLAUDE.md in the project root. If the file exists, append or update the Design Context section. +**If user chose option 1**: Write this section to CLAUDE.md in the project root. If the file exists, append or update the Design Context section. + +**If user chose option 2 (Laravel Boost)**: +1. Create the `.ai/guidelines/` directory if it doesn't exist +2. Write the Design Context section to `.ai/guidelines/design-context.md` +3. Inform the user to run `php artisan boost:update` to merge this guideline into their CLAUDE.md + +Confirm completion and summarize the key design principles that will now guide all future work. -Confirm completion and summarize the key design principles that will now guide all future work. \ No newline at end of file +**For Laravel Boost users (option 2):** Remind them to run `php artisan boost:update` to merge the new guideline into their CLAUDE.md. \ No newline at end of file diff --git a/source/commands/teach-impeccable.md b/source/commands/teach-impeccable.md index a1dc7b4..93c3c59 100644 --- a/source/commands/teach-impeccable.md +++ b/source/commands/teach-impeccable.md @@ -43,7 +43,19 @@ Note what you've learned and what remains unclear. Skip questions where the answer is already clear from the codebase exploration. -## Step 3: Write Design Context +## Step 3: Choose Storage Location + +Before writing the design context, ask the user where they'd prefer to store this information: + +{{ask_instruction}} +**Where would you like to store the design guidelines?** + +1. **Direct integration**: Add to {{config_file}} in the project root (immediately available to {{model}}) +2. **Laravel Boost integration**: Create separate guideline file in `.ai/guidelines/design-context.md` (Laravel Boost will merge into {{config_file}} when you run `php artisan boost:update`) + +Always present the options in the order listed above. Option 1 is recommended for most projects. Option 2 is only for projects using Laravel Boost's guideline merging system. + +## Step 4: Write Design Context Synthesize your findings and the user's answers into a `## Design Context` section: @@ -63,6 +75,13 @@ Synthesize your findings and the user's answers into a `## Design Context` secti [3-5 principles derived from the conversation that should guide all design decisions] ``` -Write this section to {{config_file}} in the project root. If the file exists, append or update the Design Context section. +**If user chose option 1**: Write this section to {{config_file}} in the project root. If the file exists, append or update the Design Context section. + +**If user chose option 2 (Laravel Boost)**: +1. Create the `.ai/guidelines/` directory if it doesn't exist +2. Write the Design Context section to `.ai/guidelines/design-context.md` +3. Inform the user to run `php artisan boost:update` to merge this guideline into their {{config_file}} + +Confirm completion and summarize the key design principles that will now guide all future work. -Confirm completion and summarize the key design principles that will now guide all future work. +**For Laravel Boost users (option 2):** Remind them to run `php artisan boost:update` to merge the new guideline into their {{config_file}}. \ No newline at end of file From e977d6dc54a9eda31335ac786311ae766cfe4da6 Mon Sep 17 00:00:00 2001 From: seomikewaltman Date: Fri, 13 Mar 2026 15:12:15 -0500 Subject: [PATCH 2/2] refactor: auto-detect Laravel Boost instead of asking user for storage location MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Replace the manual storage choice (Step 3/4) with automatic detection — checks composer.json for laravel/boost dependency. If found, writes to .ai/guidelines/design-context.md; otherwise writes to the AI config file. Keeps the skill at 3 steps with zero friction. --- .claude/skills/teach-impeccable/SKILL.md | 28 +++++++----------------- source/skills/teach-impeccable/SKILL.md | 26 ++++++---------------- 2 files changed, 15 insertions(+), 39 deletions(-) diff --git a/.claude/skills/teach-impeccable/SKILL.md b/.claude/skills/teach-impeccable/SKILL.md index ac519df..3874192 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: +{{ask_instruction}} Focus only on what you couldn't infer from the codebase: ### Users & Purpose - Who uses this? What's their context when using it? @@ -44,19 +44,12 @@ STOP and call the AskUserQuestionTool to clarify. Focus only on what you couldn' Skip questions where the answer is already clear from the codebase exploration. -## Step 3: Choose Storage Location +## Step 3: Write Design Context -Before writing the design context, ask the user where they'd prefer to store this information: +First, determine where to write. Check for `composer.json` in the project root. If it exists, look for `laravel/boost` in the `require` or `require-dev` dependencies. -STOP and call the AskUserQuestionTool to clarify. -**Where would you like to store the design guidelines?** - -1. **Direct integration**: Add to CLAUDE.md in the project root (immediately available to Claude) -2. **Laravel Boost integration**: Create separate guideline file in `.ai/guidelines/design-context.md` (Laravel Boost will merge into CLAUDE.md when you run `php artisan boost:update`) - -Always present the options in the order listed above. Option 1 is recommended for most projects. Option 2 is only for projects using Laravel Boost's guideline merging system. - -## Step 4: Write Design Context +- **If `laravel/boost` is found:** Write to `.ai/guidelines/design-context.md` (create the `.ai/guidelines/` directory if needed) +- **If not found (or no `composer.json`):** Write to {{config_file}} in the project root Synthesize your findings and the user's answers into a `## Design Context` section: @@ -76,13 +69,8 @@ Synthesize your findings and the user's answers into a `## Design Context` secti [3-5 principles derived from the conversation that should guide all design decisions] ``` -**If user chose option 1**: Write this section to CLAUDE.md in the project root. If the file exists, append or update the Design Context section. - -**If user chose option 2 (Laravel Boost)**: -1. Create the `.ai/guidelines/` directory if it doesn't exist -2. Write the Design Context section to `.ai/guidelines/design-context.md` -3. Inform the user to run `php artisan boost:update` to merge this guideline into their CLAUDE.md +If writing to {{config_file}} and the file already exists, append or update the Design Context section. -Confirm completion and summarize the key design principles that will now guide all future work. +If writing to `.ai/guidelines/design-context.md`, remind the user to run `php artisan boost:update` to merge the guideline into their {{config_file}}. -**For Laravel Boost users (option 2):** Remind them to run `php artisan boost:update` to merge the new guideline into their CLAUDE.md. \ No newline at end of file +Confirm completion and summarize the key design principles that will now guide all future work. diff --git a/source/skills/teach-impeccable/SKILL.md b/source/skills/teach-impeccable/SKILL.md index 4c86c2d..3874192 100644 --- a/source/skills/teach-impeccable/SKILL.md +++ b/source/skills/teach-impeccable/SKILL.md @@ -44,19 +44,12 @@ Note what you've learned and what remains unclear. Skip questions where the answer is already clear from the codebase exploration. -## Step 3: Choose Storage Location +## Step 3: Write Design Context -Before writing the design context, ask the user where they'd prefer to store this information: +First, determine where to write. Check for `composer.json` in the project root. If it exists, look for `laravel/boost` in the `require` or `require-dev` dependencies. -{{ask_instruction}} -**Where would you like to store the design guidelines?** - -1. **Direct integration**: Add to {{config_file}} in the project root (immediately available to {{model}}) -2. **Laravel Boost integration**: Create separate guideline file in `.ai/guidelines/design-context.md` (Laravel Boost will merge into {{config_file}} when you run `php artisan boost:update`) - -Always present the options in the order listed above. Option 1 is recommended for most projects. Option 2 is only for projects using Laravel Boost's guideline merging system. - -## Step 4: Write Design Context +- **If `laravel/boost` is found:** Write to `.ai/guidelines/design-context.md` (create the `.ai/guidelines/` directory if needed) +- **If not found (or no `composer.json`):** Write to {{config_file}} in the project root Synthesize your findings and the user's answers into a `## Design Context` section: @@ -76,13 +69,8 @@ Synthesize your findings and the user's answers into a `## Design Context` secti [3-5 principles derived from the conversation that should guide all design decisions] ``` -**If user chose option 1**: Write this section to {{config_file}} in the project root. If the file exists, append or update the Design Context section. - -**If user chose option 2 (Laravel Boost)**: -1. Create the `.ai/guidelines/` directory if it doesn't exist -2. Write the Design Context section to `.ai/guidelines/design-context.md` -3. Inform the user to run `php artisan boost:update` to merge this guideline into their {{config_file}} +If writing to {{config_file}} and the file already exists, append or update the Design Context section. -Confirm completion and summarize the key design principles that will now guide all future work. +If writing to `.ai/guidelines/design-context.md`, remind the user to run `php artisan boost:update` to merge the guideline into their {{config_file}}. -**For Laravel Boost users (option 2):** Remind them to run `php artisan boost:update` to merge the new guideline into their {{config_file}}. \ No newline at end of file +Confirm completion and summarize the key design principles that will now guide all future work.