make-crud
Skill4 starsChanged 2 months agoMITView on GitHub
Use when an entity needs the full set of list, show, create, edit and delete actions.
In this repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- cli-conventionsSkill
- componentsSkill
- configurationSkill
- discoverSkill
- make-ciSkill
- make-commandSkill
- make-controllerSkill
- make-decoratorSkill
- make-entitySkill
- make-formSkill
- make-listenerSkill
- make-migrationSkill
- make-registration-formSkill
- make-reset-passwordSkill
- make-security-customSkill
- make-security-form-loginSkill
- make-testSkill
- make-twig-extensionSkill
- make-userSkill
- make-voterSkill
- make-webhookSkill
- servicesSkill
- templatesSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 33
Create and edit each render and process the form in a single action.
≈ “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.
Files
CRUD for an entity
symfony console make:crud BlogPost --controller-class=BlogPostControllerThe entity is the argument and --controller-class names the controller; without it the name
is derived from the entity. The maker also writes the form type and the Twig templates.
Install it first if it is missing: symfony composer require --dev symfony/maker-bundle.
Before running it
make:crud generates a lot — a controller with five actions, a form type, five templates. On
an entity that only needs a list and a detail page, most of that is dead code someone has to
read later. Generate it when the entity really is edited through a full admin-style interface,
and write the one or two actions by hand when it is not.
What to keep
The generated controller extends AbstractController and routes through attributes, with
route names prefixed by the entity. Actions take the entity as a type-hinted argument and let
the value resolver load it, which is why a missing record 404s without any code.
Create and edit each render and process the form in a single action. That is the convention, not an accident of the generator.
The delete action checks a CSRF token. Removing that check because it is inconvenient makes every listing page a deletion link away from a cross-site request.
What to change
The templates are a starting point and look it. Field types in the generated form are guessed from the mapping — an entity property is not always the widget a user should see.
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.