agentleFS
fabioc-alohafabioc-aloha/Alex_ACT_ONE/skills/bootstrap-project/resources/AGENTS.md

Alex_ACT_ONE / resources

AGENTS.md0 starsChanged 9 days agoMITView on GitHub

Read HANDOFF.md for current state, blockers, verification, and the next action. Use the project's authoritative task list (default TODO.md) for open work and the project changelog (default CHANGELOG.md) for completed-change history. Follow these routes when the records exist; meditation creates missing continuity records only when authorized and consistent with project conventions. Keep this file a stable quick start. Handoff is not a changelog or a duplicate backlog. Preserve history before pruning active records, and keep unresolved tasks until evidence or…

The file

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

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

  • ≈1

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

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

    Read HANDOFF.md for current state, blockers, verification, and the next action.

    line 6
  2. Very specific:

    Use the project's authoritative task list (default TODO.md) for open work and the project changelog (default CHANGELOG.md) for …

    line 7
  3. Distinctive:

    Follow these routes when the records exist.

    line 9
  4. Distinctive:

    Keep this file a stable quick start.

    line 12
  5. Distinctive:

    Keep requested documents, plans, reports, code, useful one-off helpers, generated outputs, and required supporting evidence inside this …

    line 23
  6. Common:

    Before completion, verify final files, dependencies, repository links, Git ignore state, and actual Git state.

    line 27

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

Repository Agent Guidance

<!-- alex-act-continuity:start -->

Continuity

Read HANDOFF.md for current state, blockers, verification, and the next action. Use the project's authoritative task list (default TODO.md) for open work and the project changelog (default CHANGELOG.md) for completed-change history. Follow these routes when the records exist; meditation creates missing continuity records only when authorized and consistent with project conventions.

Keep this file a stable quick start. Handoff is not a changelog or a duplicate backlog. Preserve history before pruning active records, and keep unresolved tasks until evidence or an explicit decision closes them. Meditation recommends skills or automation for demonstrated needs; authoring, broader adoption, and Mall submission require separate approval. It does not write episodic or native memory. Existing episodes are historical evidence, not active guidance. Cross-project work stays explicit until separately authorized.

<!-- alex-act-continuity:end -->

Project artifact storage

Keep requested documents, plans, reports, code, useful one-off helpers, generated outputs, and required supporting evidence inside this repository. Respect explicitly approved destinations and existing project conventions. Session storage or a chat link is never the sole home of a project deliverable. Before completion, verify final files, dependencies, repository links, Git ignore state, and actual Git state. Exclude credentials, disposable runtime state, and unapproved sensitive or cross-project material. Storage requirements grant no additional implementation, installation, commit, push, or publication authority and do not constitute host-enforced filesystem isolation.

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.