make-registration-form
Skill4 starsChanged 2 months agoMITView on GitHub
Use when the application needs self-service user registration.
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-reset-passwordSkill
- make-security-customSkill
- make-security-form-loginSkill
- make-testSkill
- make-twig-extensionSkill
- make-userSkill
- make-voterSkill
- make-webhookSkill
- servicesSkill
- templatesSkill
The file
Files
Registration form
symfony console make:registration-form --unique-entity --auto-login \
--redirect-route=app_home
symfony console make:registration-form --unique-entity \
--verify-email --from-email-address=noreply@example.com --from-email-name="Acme"Three flags are opt-in on the command line where the prompt would default to yes, so a
script states each one it wants: --unique-entity (a UniqueEntity constraint on the
user class — this is what prevents duplicate accounts), --verify-email (confirmation
mail before the account counts), --auto-login (sign the user in right after
registering; needs --authenticator when more than one exists). The identity fields
(--user-class, --username-field, --password-field, the getters) are guessed from
security.yaml and the class; an ambiguous guess aborts naming the option.
A user class must exist first (make:user). Install the maker if it is missing:
symfony composer require --dev symfony/maker-bundle.
What you get
A registration controller, the form type with the plain-password field mapped to
nothing, and the template. With --verify-email the maker installs
symfonycasts/verify-email-bundle and adds the signed-confirmation route and email;
that path needs a configured mailer and the two --from-email-* values.
What to check
- The password is hashed through the
UserPasswordHasherInterfacein the controller; the plain password never lands on the entity. Keep that shape. --verify-emailwithout a realMAILER_DSNproduces accounts nobody can activate.--unique-entitychanged the user class, so the constraint shows up in its diff, not only in the controller.
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.