laravel-guidelines
Skill3 starsChanged 30 days agoNo licenceView on GitHub
Manages project-specific AI guidelines in `.ai/guidelines/` for Laravel projects. Use when the user says things like "record a convention", "note this for future agents", "document this pattern", or wants to record, update, or remove a non-obvious project convention, or tricky detail that agents wouldn't infer from standard Laravel patterns or CLAUDE.md. Also activate automatically after completing any Laravel implementation task that introduced new models, services, jobs, observers, or non-standard behaviour — to capture decisions future agents wouldn't easily infer. For formal architectural decisions with context, alternatives, and rationale, use the `adr` skill instead — guidelines are for terse, agent-facing conventions, not decision records.
In this repository24 other files it gives its agents.
- adrSkill
- coverSkill
- create-skillSkill
- grill-meSkill
- handoffSkill
- laravel-layered-architectureSkill
- mergeSkill
- mobile-ux-principlesSkill
- monitorSkill
- pipelineSkill
- polishSkill
- qaSkill
- reviewSkill
- show-meSkill
- skill-doctorSkill
- stepsSkill
- tackleSkill
- test-auditSkill
- testSkill
- to-specSkill
- to-tasksSkill
- ui-rulesSkill
- ux-principlesSkill
- wrap-upSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.