agentleFS
BKR-57BKR-57/symfony-ux-skills/AGENTS.md

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.

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
  1. Very specific:

    Always render {{ attributes }} on the root element of a LiveComponent

    line 15
  2. Very specific:

    Prefer HTML syntax (<twig:Alert />) over Twig syntax ({% component 'Alert' %})

    line 16
  3. Very specific:

    Use data-model="debounce(300)|field" for text inputs in LiveComponents

    line 17
  4. Distinctive:

    Use Turbo Streams when updating multiple page sections.

    line 20
  5. Very specific:

    Run php bin/phpunit for PHP tests

    line 25
  6. Very specific:

    Run npx vitest for JavaScript tests if applicable

    line 26

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

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 stimulus skill
  • Navigation, partial page updates -- use the turbo skill
  • Reusable static UI component -- use the twig-component skill
  • Reactive component that re-renders on user input -- use the live-component skill
  • Not sure which one fits -- use the symfony-ux skill (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/phpunit for PHP tests
  • Run npx vitest for JavaScript tests if applicable

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.