<< All versions

Skill v1.0.1

currentAutomated scan100/100
techmefr/mentis/laravel-conventions

+15 new

──Details
PublishedOctober 25, 2026 at 10:16 PM
Content Hashsha256:5c11b8da16c350ee...
Git SHAf2a8e60bba80
Bump Typepatch
Compare with v1.0.0
──Files
Files (1 file, 5.4 KB)
SKILL.md5.4 KBactive
SKILL.md · 68 lines · 5.4 KB

version: "1.0.1" name: laravel-conventions description: "Use when writing or reviewing Laravel: where behaviour lives, authorisation, data model and queries, naming and typing, HTTP surface, config and commands, jobs, tests, architecture, failures, production configuration, safe migrations. The framework layer above skills/php-patterns."


laravel-conventions

Step 6 of the pipeline (WORKFLOW.md). Frames the writing and review of Laravel code. Sits above skills/php-patterns (which stays on the language: typing, error handling, OOP) and below the review agent for the stack. Every rule holds in a repo with nothing installed (CONVENTIONS.md, rule A).

Relation to an org skill catalogue. Where a company ships its own versioned catalogue for this stack, it is the authority on its house style — its approved package list, its architecture scaffold, its broadcaster, its MCP tooling — and overrides this block wherever the two differ. The rules below are the generic form, with the internal package and product names removed (rule C).

An applied override is recorded, not hidden. Write the code the governing rule actually requires, and leave one short neutral trace addressed to whoever can decide (a line in the PR description, the task summary or an ADR): which rule was overridden, by what, and that it is a resolved case. Never phrase it as "a conflict between mentis and the house rules" to a non-technical stakeholder — that framing reads as broken even when the case is a normal, resolved one, and has already caused a real project to get abandoned and restarted over nothing (the Inertia/REST-package case in §6 and skills/inertia-conventions is exactly that: a resolved case, not a real disagreement). Raise one specific, named question to the decider only when no rule anywhere actually resolves the case.

When

As soon as a controller, model, migration, job, listener, policy, FormRequest, command, seeder or factory is written or modified, during code (6) or tdd (5).

Steps

Read only the sections the task actually touches. The rules live one file per section under references/; loading all of them for a change that only renames a variable is waste, and a section read is a section that has to be applied. If you are reviewing a whole diff, pick the rows whose trigger the diff meets, not the whole table.

§CoversRead it whenFile
1Where behaviour livesa model, a controller, a listener or a service is written`01-where-behaviour-lives.md`
2Authorisationan endpoint, a policy or a permission check`02-authorisation.md`
3Data model and schemaa migration, a column, an enum, a soft delete`03-data-model-schema.md`
4Queriesan Eloquent query, a relation load, or anything inside a loop`04-queries.md`
5Naming, typing, stylea symbol has to be named, or a docblock written`05-naming-typing-style.md`
6HTTP surfacea route, a controller action, a FormRequest, a response shape`06-http-surface.md`
7Configuration and commandsconfig/, env(), an artisan command, a seeder or a factory`07-configuration-commands.md`
8Jobs, notifications and realtimea queued job, a scheduled task, a notification or mail, a broadcast`08-jobs-realtime.md`
9Tests and static analysistests are written, or Larastan/Pint is in play`09-tests-static-analysis.md`
10Architecturethe change spans layers, or a new one is proposed`10-architecture.md`
11Failuresan operation can fail, an exception is thrown, caught or mapped to a response`11-failures.md`
12Production configurationan environment file, a session, cache, queue or mail driver, the proxy and host settings, a debugging tool or the deploy steps`12-production-configuration.md`
13Safe migrations on a live databasea migration touches a table that holds data in production, renames, drops, indexes, constrains or backfills`13-safe-migrations.md`

Output / checkpoint

Code compliant with the sections above, formatter clean, and no new static-analysis finding introduced by the diff. Checked by gate (7) and review (8).

Guardrails

No comments in the code produced. These rules govern new code; existing fat models, observers and magic strings stay until migrated deliberately (skills/simplify, not this block). Never widen a permission or skip an authorisation check to make something work — that's a security decision, and it goes to skills/security-hardening. Where an org catalogue is installed and disagrees, it wins — apply it and leave the short neutral trace described at the top, never a silent override.

Origin

Rules mined from market catalogues, linters and internal review feedback, rewritten in the house voice; the full provenance, the source stamps and the refresh log are in `references/origin.md`. Read it when checking whether a rule is still current, not when applying one.

← v1.0.0All versions