agentleFS
e-reitbauere-reitbauer/habits/skills/units/SKILL.md

units

Skill1 starsChanged 6 days agoMITView on GitHub

Use when the user asks to load, list, show or check habits units, asks which guidance applies to the current project, or names a technology unit to pull in by hand. Examples: "load the maven unit", "what habits apply here?".

The file

We split this skill into the rules it gives an agent

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

  • 1

    Very specific

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

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

    Use the habits CLI whose path was given at session start (python3 "<plugin root>/habits" <command>):

    line 12
  2. Distinctive:

    When the user asks for a unit that doesn't exist, say so and list the closest ids.

    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

Habits units

Units are the granular guidance files for languages, tools, platforms, testing and workflows. Most load on their own when a matching file is touched, a matching command runs, or a marker exists in the project. This skill covers loading them by hand and reporting on them.

Use the habits CLI whose path was given at session start (python3 "<plugin root>/habits" <command>):

  • units: every unit with its triggers. Use it to find the right id.
  • load <id>: prints the unit. Follow its contents as project instructions for the rest of the session.
  • status: which units apply to this project and why, file types with no unit, missing LSPs, config.
  • config, config set autoLsp|autoCreate off|suggest, config set notify|autoTitle on|off, config disable|enable <id>: only when the user asks to change behaviour.

When the user asks for a unit that doesn't exist, say so and list the closest ids.

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.