diff --git a/.claude/skills/teach-impeccable/SKILL.md b/.claude/skills/teach-impeccable/SKILL.md index 2ac070a..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? @@ -46,6 +46,11 @@ Skip questions where the answer is already clear from the codebase exploration. ## Step 3: Write Design Context +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. + +- **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: ```markdown @@ -64,6 +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] ``` -Write this section to CLAUDE.md in the project root. If the file exists, append or update the Design Context section. +If writing to {{config_file}} and the file already exists, append or update the Design Context section. + +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}}. -Confirm completion and summarize the key design principles that will now guide all future work. \ 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 18f5479..3874192 100644 --- a/source/skills/teach-impeccable/SKILL.md +++ b/source/skills/teach-impeccable/SKILL.md @@ -46,6 +46,11 @@ Skip questions where the answer is already clear from the codebase exploration. ## Step 3: Write Design Context +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. + +- **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: ```markdown @@ -64,6 +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] ``` -Write this section to {{config_file}} in the project root. If the file exists, append or update the Design Context section. +If writing to {{config_file}} and the file already exists, append or update the Design Context section. + +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}}. Confirm completion and summarize the key design principles that will now guide all future work.