// MUST USE when creating, updating, or managing AI skills and guidelines. Activates when: creating a new skill, editing existing skills, updating coding guidelines, modifying AI instructions, working with .ai/ directory, or when user mentions: skill, CLAUDE.md, guidelines, AI configuration.
| name | ai-guidelines |
| description | MUST USE when creating, updating, or managing AI skills and guidelines. Activates when: creating a new skill, editing existing skills, updating coding guidelines, modifying AI instructions, working with .ai/ directory, or when user mentions: skill, CLAUDE.md, guidelines, AI configuration. |
These files are auto-generated by Laravel Boost. Any direct edits will be overwritten.
.ai/ # SOURCE - Edit files here
├── guidelines/ # Project-wide AI instructions
│ └── *.blade.php / *.md # Coding conventions
└── skills/ # Skill definitions
└── {skill-name}/SKILL.md # One folder per skill
.claude/skills/ # AUTO-GENERATED - Do not edit
└── {skill-name}/SKILL.md # Skills for Claude Code
.github/skills/ # AUTO-GENERATED - Do not edit
└── {skill-name}/SKILL.md # Skills for GitHub Copilot
Important: Only edit files in .ai/. The .claude/skills/ and .github/skills/ directories are auto-generated by vendor/bin/testbench boost:update and will be overwritten.
This package uses Laravel Boost via Orchestra Testbench:
.ai/guidelines/ define project-wide coding conventions.ai/skills/ provide domain-specific instructions activated on demandCLAUDE.md and AGENTS.mdvendor/bin/testbench instead of php artisanEdit files in .ai/guidelines/:
.blade.php): Use @verbatim blocks around code examples.md): Standard markdown formatSkills live in .ai/skills/{skill-name}/SKILL.md with frontmatter:
---
name: skill-name
description: When this skill activates. Include trigger words and scenarios.
---
# Skill Title
## When to use this skill
- Scenario 1
- Scenario 2
## Instructions
Detailed instructions for the skill...
my-new-skill/name in frontmatter should match the directory namedescription with activation triggersCRITICAL: Always run boost:update before committing any changes to .ai/ files.
vendor/bin/testbench boost:update
This command syncs your .ai/ changes to all generated locations:
| Generated File/Directory | Purpose |
|---|---|
CLAUDE.md | Main context file for Claude |
AGENTS.md | Main context file for Codex |
.claude/skills/ | Skills loaded by Claude Code |
.github/skills/ | Skills for GitHub Copilot |
.github/copilot-instructions.md | Instructions for GitHub Copilot |
All these files must be committed together — they are kept in sync by boost:update.
.ai/guidelines/ or .ai/skills/ (never edit generated files)@verbatim blocks in Blade files for code examplesvendor/bin/testbench boost:update (CRITICAL!)git status shows changes in: .ai/, .claude/, .github/, CLAUDE.md, AGENTS.mdProfile a slow request, command, or code path with sandermuller/stopwatch. Activate when the user mentions: slow request, slow endpoint, slow page, slow query, slow job, slow command, slow API call, slow HTTP, performance issue, profile this, why is this slow, where is the time going, optimize, bottleneck, latency, n+1, query count, memory usage, http calls, outbound requests, server-timing.
Pre-push / pre-release checklist. Runs Rector, Pint, Pest, PHPStan, audits README + `.ai/` docs for staleness, then commits + pushes, watches CI for green, and drafts release notes against the verified SHA. Activate before: pushing to remote, tagging a release, writing release notes, or when user mentions: pre-release, pre-push, release checklist, ship, cut release, release notes.
Runs backend code quality checks in two tiers: Pint + related tests (every change), PHPStan + full suite (completion only). Activate after making changes to PHP files, or when user mentions: phpstan, pint, code quality, static analysis, code style, run checks.
Requests an independent code review from OpenAI Codex CLI, critically evaluates its findings, and applies warranted fixes. Activates when: the user says /codex-review, asks for a Codex review, or wants an external AI review of changes.
Implements a specification file phase-by-phase with progress tracking. Activates when: implementing a spec, building from a spec, starting a spec phase, or when user mentions: implement spec, spec file, implement phase, build spec, start phase.
Writes implementation-ready specification files with progress-trackable phases. Activates when: writing a spec, creating a spec file, documenting a feature plan, or when user mentions: write spec, create spec, spec format, spec template.