symfony-ux-skills
AGENTS.md0 starsChanged 9 months agoMITView on GitHub
This project uses the Symfony UX frontend stack. Five agent skills are installed to help you work with it.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 33,315 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository7 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- live-componentSkill
- stimulusSkill
- symfony-uxSkill
- turboSkill
- twig-componentSkill
The file
We split this AGENTS.md into the rules it gives an agent
6 rules. About 0 are common, 1 is distinctive, and 5 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.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Always render {{ attributes }} on the root element of a LiveComponent
- Very specific: line 16
Prefer HTML syntax (<twig:Alert />) over Twig syntax ({% component 'Alert' %})
- Very specific: line 17
Use data-model="debounce(300)|field" for text inputs in LiveComponents
- Distinctive: line 20
Use Turbo Streams when updating multiple page sections.
- Very specific: line 25
Run php bin/phpunit for PHP tests
- Very specific: line 26
Run npx vitest for JavaScript tests if applicable
≈ “Common” is an estimate: at least 1 in 5 of the 42,283 AGENTS.md 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
Symfony UX Frontend Stack
This project uses the Symfony UX frontend stack. Five agent skills are installed to help you work with it.
Which tool to use
- Pure JS behavior, no server round-trip -- use the
stimulusskill - Navigation, partial page updates -- use the
turboskill - Reusable static UI component -- use the
twig-componentskill - Reactive component that re-renders on user input -- use the
live-componentskill - Not sure which one fits -- use the
symfony-uxskill (orchestrator / decision tree)
Key rules
- Always render
{{ attributes }}on the root element of a LiveComponent - Prefer HTML syntax (
<twig:Alert />) over Twig syntax ({% component 'Alert' %}) - Use
data-model="debounce(300)|field"for text inputs in LiveComponents - Stimulus controllers must clean up listeners and observers in
disconnect() - Turbo Frame IDs must match between the page and the server response
- Use Turbo Streams when updating multiple page sections; use Frames for a single section
<twig:Turbo:Stream:Append>syntax is available since Symfony UX 2.22+
Testing
- Run
php bin/phpunitfor PHP tests - Run
npx vitestfor JavaScript tests if applicable
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.

