chalkline / harbor
AGENTS.md14 starsChanged 53 days agoApache-2.0View on GitHub
This instruction file applies only to examples/harbor/ and tasks explicitly using this fictional example. It does not configure the root writing system. - This is a self-contained, public synthetic demonstration, not a real setup. Do not run setup merely because root references/voice.md is absent or because this example nests its voice file under references/shared/. - Read this example's README.md and its task routing table first. Read both shared files plus every matching scoped file; do not import Meridian rules. -…
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,542 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.
The file
We split this AGENTS.md into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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
- Very specific: line 7
Do not run setup merely because root references/voice.md is absent or because this example nests its voice file under references/shared/.
- Distinctive: line 9
Read this example's README.md and its task routing table first.
- Distinctive: line 15
All Harbor guidance and provenance are invented for demonstration.
- Distinctive: line 21
Keep artifact, calibration, reference-change, and consumer-deployment approvals separate.
- Distinctive: line 23
Keep privacy, exact-wording, and no-commit/no-push boundaries from the parent contract.
≈ “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.
Files
Harbor example routing
This instruction file applies only to examples/harbor/ and tasks explicitly
using this fictional example. It does not configure the root writing system.
- This is a self-contained, public synthetic demonstration, not a real setup.
Do not run setup merely because root
references/voice.mdis absent or because this example nests its voice file underreferences/shared/. - Read this example's
README.mdand its task routing table first. Read both shared files plus every matching scoped file; do not import Meridian rules. - File paths organize discovery, not authority. Apply stated task scopes and the repository's specificity/enforcement rules; never pick by directory or date. Surface unresolved conflicts. Ask about uncovered tasks rather than extending this example's rules automatically.
- All Harbor guidance and provenance are invented for demonstration. Use it only for fictional Harbor exercises, not as approval or evidence about a real team.
- Preserve task-supplied facts and their certainty. Reference examples are not current reservation data, product behavior, or permission to make promises.
- There are no approved calibration pairs here. Report that coverage gap; the README walkthroughs are illustrations, not approved reusable direction or tests.
- Keep artifact, calibration, reference-change, and consumer-deployment approvals separate. Do not claim any of them occurred merely because these files exist.
- Keep privacy, exact-wording, and no-commit/no-push boundaries from the parent contract. This local routing exception changes no instructions outside Harbor.
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
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.

