Backend change
Use when implementing any server-side change in the Laravel app — a controller, service, model, migration, queued job, command, or business rule. Enforces the project's structure, safety, and testing gates.From its SKILL.md
npx -y skills add yousefkadah/laravel-ai-kit --skill backend-changeAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.3 KB, 270 tokens by cl100k_base, as published. Nobody here has run it
Backend change
Before writing
- Read a sibling file in the same area and mirror its structure/naming/idioms.
- Check for an existing service/helper to reuse before adding one.
- For Laravel facts (APIs, signatures, schema), consult Boost — don't guess.
- If the change is more than a small edit, propose a short plan first.
While writing
-
declare(strict_types=1), typed params + return types, promoted constructor props. - Validate in Form Requests; authorize in Policies.
- No N+1 — eager-load. Push slow/external work to queued jobs.
- Multi-tenant: scope every query. A cross-tenant read/write is a security bug, not a nit.
- Use
php artisan make:*for new files. Never run migrations/destructive commands without approval.
Before done
- Add/update tests (happy path + a failure path); run them; paste evidence.
- Run the formatter (
vendor/bin/pint --dirty). - Self-review against
.ai/code-review.md. No secrets in the diff. - Keep the diff tight — no unrelated reformatting.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.