agent-ready-repo / profiles
AGENTS.md27 starsChanged yesterdayApache-2.0View on GitHub
Applies to profiles/. Inherits the root AGENTS.md. Scope-specific deltas only. A profile is a hand-authored profiles/<id>.toml that composes an ordered, single-scope set of existing packs; it introduces no primitives. The filename stem is its identifier. Reserved _ children are authoring assets, not active profiles. profile.schema.json owns fields and semantic validation. Read it with agentbundle catalogue contracts show profile.schema.json. Profile TOML is the source; profiles are scaffold sources but are not projected by catalogue self-host. Start from profiles/_example/profile.toml.
Files
AGENTS.md — profiles/
Applies to profiles/. Inherits the root AGENTS.md. Scope-specific deltas only.
Profile boundary
A profile is a hand-authored profiles/<id>.toml that composes an ordered,
single-scope set of existing packs; it introduces no primitives. The filename stem
is its identifier. Reserved _ children are authoring assets, not active profiles.
Validation and ownership
profile.schema.json owns fields and semantic validation. Read it with
agentbundle catalogue contracts show profile.schema.json. Profile TOML is the
source; profiles are scaffold sources but are not projected by catalogue self-host.
- A pack name appears at most once in a profile.
- Packs with a declared
conflictsrelationship do not share a profile.
Essential commands
agentbundle catalogue lint --root .
agentbundle catalogue verify --root .
agentbundle list-profiles <catalogue>Deeper pointers
Start from profiles/_example/profile.toml.
In this repository75 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- docs-site/AGENTS.mdAGENTS.md
- guides/AGENTS.mdAGENTS.md
- packages/AGENTS.mdAGENTS.md
- packs/AGENTS.mdAGENTS.md
- tests/AGENTS.mdAGENTS.md
- tools/AGENTS.mdAGENTS.md
- web/AGENTS.mdAGENTS.md
- docs/CLAUDE.mdCLAUDE.md
- guides/CLAUDE.mdCLAUDE.md
- packages/CLAUDE.mdCLAUDE.md
- packs/CLAUDE.mdCLAUDE.md
- profiles/CLAUDE.mdCLAUDE.md
- tests/CLAUDE.mdCLAUDE.md
- tools/CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- adapt-to-projectSkill
- assimilate-primitiveSkill
- assimilate-repoSkill
- author-briefSkill
- author-delivery-briefSkill
- author-product-docsSkill
- bug-fixSkill
- close-workSkill
- compile-okfSkill
- contract-acquisitionSkill
- explain-diffSkill
- init-projectSkill
- intake-intentSkill
- navigate-decisionsSkill
- navigate-intentsSkill
- new-adrSkill
- new-rfcSkill
- new-specSkill
- operational-safetySkill
- project-knowledgeSkill
- propose-catalogue-packSkill
- receive-briefSkill
- repository-explorationSkill
- repository-groundingSkill
- security-checklists-referenceSkill
- security-checklistsSkill
- work-intakeSkill
- work-loopSkill
- workspace-statusSkill
- adapt-to-projectSkill
- assimilate-primitiveSkill
- assimilate-repoSkill
- author-briefSkill
- author-delivery-briefSkill
- author-product-docsSkill
- bug-fixSkill
- close-workSkill
- compile-okfSkill
- contract-acquisitionSkill
- explain-diffSkill
- init-projectSkill
- intake-intentSkill
- navigate-decisionsSkill
- The first 60 shown.
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.