agentleFS
Sign inStart free
igmarinigmarin/elixir-phoenix-skills/skills/elixir-essentials/SKILL.md

elixir-essentials

Skill4 starsChanged 4 months agoMITView on GitHub

Use for Elixir language and OTP work without a narrower domain skill. This is the shared baseline for the elixir-phoenix profile.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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
  1. Distinctive:

    Use the project's Elixir version, formatter, dependencies, and established module boundaries.

    line 11
  2. Very specific:

    Prefer pattern matching and with for expected branches.

    line 13
  3. Distinctive:

    Keep pure decisions and transformations separate from IO, Repo, HTTP, process, and framework effects.

    line 14
  4. Distinctive:

    Use processes for state or concurrency, not as a default wrapper around pure functions.

    line 17
  5. Distinctive:

    Add typespecs when they clarify a public boundary or support Dialyzer.

    line 18
  6. Distinctive:

    Add a focused test for changed behavior.

    line 19

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

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

Elixir Essentials

Use the project's Elixir version, formatter, dependencies, and established module boundaries. Verify library behavior against the checked-out version before relying on an API.

  • Prefer pattern matching and with for expected branches; use pipes for clear transformations.
  • Keep pure decisions and transformations separate from IO, Repo, HTTP, process, and framework effects.
  • Parse external maps, strings, and messages at the boundary into validated structs or changesets.
  • Return tagged tuples for expected failures. Let unexpected failures reach supervision or error reporting.
  • Use processes for state or concurrency, not as a default wrapper around pure functions.
  • Add typespecs when they clarify a public boundary or support Dialyzer; do not annotate trivial private code mechanically.
  • Add a focused test for changed behavior. Run the project's formatter and relevant tests; add Credo, Sobelow, or dependency audit checks when the change touches those concerns.

Domain skills in this profile inherit this baseline. Keep their instructions limited to domain-specific behavior.

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.

Check your setup, free