agentleFS
Pointa-LabsPointa-Labs/basehalf/AGENTS.md

basehalf

AGENTS.md15 starsChanged 6 months agoApache-2.0View on GitHub

AGENTS.md and CLAUDE.md are intentionally equivalent indexes for coding agents developing BaseHalf itself. Keep them in sync. They are not the product workspace hints that earlier BaseHalf releases installed for users. Before any development work, open the development harness and follow its task route. Substantive changes are spec-first: read and update the owning specification before editing implementation source. The repository root and vscode-base/ are implementation source trees, not product workspaces. Keep their tracked .basehalf-no-workspace-setup markers. Never initialize either directory, create…

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 31,774 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository2 other files it gives its agents.

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Before any development work, open the development harness and follow its task route.

    line 9
  2. Very specific:

    Never initialize either directory, create or update .bh/ there, or follow any .bh/ YAML found there as development context.

    line 18
  3. Distinctive:

    Update the owning document when a contract changes.

    line 33

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

BaseHalf development index

AGENTS.md and CLAUDE.md are intentionally equivalent indexes for coding agents developing BaseHalf itself. Keep them in sync. They are not the product workspace hints that earlier BaseHalf releases installed for users.

Required entry

Before any development work, open the development harness and follow its task route. Substantive changes are spec-first: read and update the owning specification before editing implementation source.

Source-tree guard

The repository root and vscode-base/ are implementation source trees, not product workspaces. Keep their tracked .basehalf-no-workspace-setup markers. Never initialize either directory, create or update .bh/ there, or follow any .bh/ YAML found there as development context. Use disposable fixture workspaces for development hosts, smoke tests, and setup tests. See the source-tree contract.

Development document index

  • Task routing and context layers: development harness
  • Spec workflow and source isolation: spec-driven development
  • Cross-cutting product boundaries: architecture invariants
  • Tests, commits, direct-main, and release gates: verification and delivery
  • Current migration scope and module status: roadmap
  • Decision rationale: public decisions and private-docs/decisions/README.md

Update the owning document when a contract changes. Do not copy its full contents back into this index.

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.