agentleFS
syangasyanga/astack/AGENTS.md

astack

AGENTS.md0 starsChanged 53 days agoMITView on GitHub

Edit global instructions in instructions/. Root AGENTS.md and CLAUDE.md apply only to this repository. Before creating, importing, or modifying a skill, follow the repository-local author-skill workflow. Put reusable lessons in the applicable skill or principle, and change history in the PR. Keep adaptation records in the manifest and PR instead of separate adaptation reports. Discover skills through astack-help and installed metadata; do not maintain skill inventories in the README or other overview documents. Run python3 -m unittest discover -s tests…

The file

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

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

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before creating, importing, or modifying a skill, follow the repository-local author-skill workflow.

    line 8
  2. Very specific:

    Put reusable lessons in the applicable skill or principle, and change history in the PR.

    line 11
  3. Very specific:

    Run python3 -m unittest discover -s tests -v.

    line 18

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

astack repository instructions

Edit global instructions in instructions/. Root AGENTS.md and CLAUDE.md apply only to this repository.

Skills

Before creating, importing, or modifying a skill, follow the repository-local author-skill workflow.

Put reusable lessons in the applicable skill or principle, and change history in the PR. Keep adaptation records in the manifest and PR instead of separate adaptation reports. Discover skills through astack-help and installed metadata; do not maintain skill inventories in the README or other overview documents.

Verification

Run python3 -m unittest discover -s tests -v. Keep tests offline and confined to temporary directories. Use Python 3.10+, the standard library, and Git for scripts, with support for macOS and Linux.

The directly imported orchestration runtime retains Bun/TypeScript, and skills/show-me-your-work/scripts/log.sh retains Bash. These upstream imports are exceptions to the Python script convention. The background-job scripts in skills/run-job/, skills/claude-background-jobs/, and skills/codex-background-jobs/ also run on Python 3.9, because agents invoke them with the system python3, which is 3.9 on stock macOS. Follow the verification steps in CLI.md to run the orchestration tests offline in a temporary copy. The Python suite also tests the imported decision-log helper.

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.