agentleFS
igmarinigmarin/elixir-phoenix-skills/AGENTS.md

elixir-phoenix-skills

AGENTS.md4 starsChanged 4 months agoMITView on GitHub

The file

We split this AGENTS.md into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 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.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Verify version-dependent behavior against the app's mix.lock, generated code, or local dependency source.

    line 6
  2. Distinctive:

    Add focused tests for behavior changes.

    line 7
  3. Very specific:

    Keep Phoenix 1.7 current_user and Phoenix 1.8 Scope paths distinct in auth guidance.

    line 8
  4. Very specific:

    Run python3 scripts/validate-catalog.py and python3 -m unittest discover -s scripts -p 'test_*.py' after changes.

    line 9

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 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

Elixir Phoenix skills

  • directory.json is the registry; keep registered paths valid.
  • This is a flat, project-scoped skill pack. Use profiles.json in the shared planning repo to install it with the foundation.
  • elixir-essentials owns the shared Elixir/FCIS baseline. Domain cards contain only domain-specific rules.
  • Verify version-dependent behavior against the app's mix.lock, generated code, or local dependency source.
  • Add focused tests for behavior changes. Blocking checkpoints are for production data, auth/security, deployment, irreversible actions, and unverified external APIs.
  • Keep Phoenix 1.7 current_user and Phoenix 1.8 Scope paths distinct in auth guidance.
  • Run python3 scripts/validate-catalog.py and python3 -m unittest discover -s scripts -p 'test_*.py' after changes.

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.