make-user
Skill4 starsChanged 2 months agoMITView on GitHub
Use when a Symfony project needs a security user class — login, authentication, or stored accounts.
In this repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- cli-conventionsSkill
- componentsSkill
- configurationSkill
- discoverSkill
- make-ciSkill
- make-commandSkill
- make-controllerSkill
- make-crudSkill
- 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-voterSkill
- make-webhookSkill
- servicesSkill
- templatesSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Every question the maker asks has an option, so passing all three makes it run without prompting.
- Very specific: line 42
Never hash a password by hand.
≈ “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
Security user
symfony console make:user User \
--is-entity \
--identity-property-name=email \
--with-passwordEvery question the maker asks has an option, so passing all three makes it run without
prompting. Drop --is-entity for a user that does not live in the database, and
--with-password when another system checks credentials — a single sign-on server, for
instance.
Install the maker first if it is missing:
symfony composer require --dev symfony/maker-bundle.
What it does beyond the class
The maker implements UserInterface and, with --with-password,
PasswordAuthenticatedUserInterface, and it wires the provider and the password hasher into
config/packages/security.yaml. That edit is the part worth reading afterwards — it is
security configuration, and it is the file everything else about authentication hangs off.
What to keep
The identity property is what a user types to log in and what the provider looks up. It has to be unique in the database; the maker adds the constraint, and removing it breaks the lookup rather than merely allowing duplicates.
Roles are a json column holding strings. getRoles() always returns ROLE_USER in
addition to whatever is stored — leave that in, the security layer assumes it.
Never hash a password by hand. UserPasswordHasherInterface reads the algorithm from
security.yaml, so it stays correct when that configuration changes.
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.