AI-OS-Template
CLAUDE.md0 starsChanged 45 days agoMITView on GitHub
Keeps Claude Code compatible with the shared AGENTS.md and adds Claude-only runtime behavior. Local override loading follows the canonical rule in AGENTS.md ("Local Agent Overrides"). Claude-only addition: also read CLAUDE.local.md before this file when present. Both files are user-owned, never updated. Follow docs/agent-startup.md from the shared AGENTS.md. The detect-first-run.js hook supplies an optional setup hint; it does not override a user task. Use /start-here only when the user chooses guided setup. Do not duplicate a daily session block already opened…
In this repository96 other files it gives its agents.
- AGENTS.mdAGENTS.md
- team_context/AGENTS.mdAGENTS.md
- fin-company-cfoSkill
- fin-invoice-reconciliationSkill
- fin-month-end-reportingSkill
- fin-personal-cfoSkill
- meta-find-skillsSkill
- meta-memory-recallSkill
- meta-memory-writeSkill
- meta-skill-creatorSkill
- meta-skillifySkill
- meta-synthesize-localsSkill
- meta-toolifySkill
- meta-wrap-upSkill
- mkt-ab-testingSkill
- mkt-ad-creativeSkill
- mkt-adsSkill
- mkt-asoSkill
- mkt-brand-voiceSkill
- mkt-churn-preventionSkill
- mkt-cold-emailSkill
- mkt-co-marketingSkill
- mkt-community-marketingSkill
- mkt-content-repurposingSkill
- mkt-copy-editingSkill
- mkt-copywritingSkill
- mkt-croSkill
- mkt-directory-submissionsSkill
- mkt-emailsSkill
- mkt-eventsSkill
- mkt-free-toolsSkill
- mkt-icpSkill
- mkt-influencer-marketingSkill
- mkt-jab-hookSkill
- mkt-launchSkill
- mkt-lead-magnetsSkill
- mkt-marketing-loopsSkill
- mkt-offersSkill
- mkt-onboardingSkill
- mkt-paywallsSkill
- mkt-popupsSkill
- mkt-positioningSkill
- mkt-programmatic-seoSkill
- mkt-prospectingSkill
- mkt-public-relationsSkill
- mkt-referralsSkill
- mkt-sales-enablementSkill
- mkt-schemaSkill
- mkt-signupSkill
- mkt-smsSkill
- mkt-socialSkill
- mkt-ugc-scriptsSkill
- mkt-visual-identitySkill
- ops-analyticsSkill
- ops-attributionSkill
- ops-cronSkill
- ops-ingestSkill
- ops-loopifySkill
- ops-project-managementSkill
- ops-revopsSkill
- The first 60 shown.
The file
We split this CLAUDE.md into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 22
Follow docs/agent-startup.md from the shared AGENTS.md.
- Very specific: line 25
Do not duplicate a daily session block already opened during startup.
- Distinctive: line 31
Don't greet proactively. If the user greets casually and open threads exist, mention them in one line.
- Very specific: line 33
After a major deliverable (file saved to projects/, skill built/modified), run the post-deliverable question from AGENTS.md ("How did this …
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.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
CLAUDE.md
Keeps Claude Code compatible with the shared AGENTS.md and adds Claude-only
runtime behavior.
@AGENTS.md
Local Overrides
Local override loading follows the canonical rule in AGENTS.md ("Local Agent
Overrides"). Claude-only addition: also read CLAUDE.local.md before this file
when present. Both files are user-owned, never updated.
Claude Runtime
Shared Startup
Follow docs/agent-startup.md from the shared AGENTS.md. The
detect-first-run.js hook supplies an optional setup hint; it does not override
a user task. Use /start-here only when the user chooses guided setup.
Do not duplicate a daily session block already opened during startup.
Scheduled cron runs (AI_OS_CRON_JOB_SLUG is set) follow the job prompt only.
Team mode uses the injected snapshot exclusively and skips local startup.
Greeting & Checkpoint
- Don't greet proactively. If the user greets casually and open threads exist, mention them in one line. If they state a task, begin immediately.
- After a major deliverable (file saved to
projects/, skill built/modified), run the post-deliverable question from AGENTS.md ("How did this land? Any adjustments?") and log feedback per that rule. Skip this for quick answers or small edits.
Daily Memory
Each session appends a numbered ## Session N block to
context/memory/{YYYY-MM-DD}.md, tracking goal, deliverables, decisions and open
threads silently as they happen (never announce). A ### Project reference means
load that brief. On sign-off, run meta-wrap-up, finalising the current block.
Template + tracked events: docs/daily-memory.md.
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.

