AI-OS-Template / team_context
AGENTS.md0 starsChanged 45 days agoMITView on GitHub
This file holds shared team-level instructions for Team OS. It is loaded when the Team OS context snapshot includes team context. Apply these instructions after the root AGENTS.md system rules and before private user or client-specific context. - Treat the Team OS server snapshot as the source of truth for team, user, and client context. - Use team_context/team-profile.md to understand what the team does. - Use team_context/operating-rules.md for shared approval, review, and working rules. - Use team_context/shared-preferences.md for team-wide output…
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.
In this repository96 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.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 AGENTS.md into the rules it gives an agent
8 rules. About 0 are common, 2 are distinctive, and 6 are 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.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Treat the Team OS server snapshot as the source of truth for team, user, and client context.
- Very specific: line 13
Use team_context/team-profile.md to understand what the team does.
- Very specific: line 14
Use team_context/operating-rules.md for shared approval, review, and working rules.
- Very specific: line 16
Use team_context/shared-preferences.md for team-wide output and workflow preferences.
- Very specific: line 18
Use team_context/prompt-tags.md only when prompt tags are needed.
- Very specific: line 21
Keep private user notes out of team_context/.
- Distinctive: line 23
Keep client-only information in the selected client's context, not in shared team files.
- Very specific: line 25
Keep skills in the root or client .claude/skills/ folders.
≈ “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
Team Context Agent Instructions
This file holds shared team-level instructions for Team OS. It is loaded when the Team OS context snapshot includes team context.
Apply these instructions after the root AGENTS.md system rules and before
private user or client-specific context.
Rules
- Treat the Team OS server snapshot as the source of truth for team, user, and client context.
- Use
team_context/team-profile.mdto understand what the team does. - Use
team_context/operating-rules.mdfor shared approval, review, and working rules. - Use
team_context/shared-preferences.mdfor team-wide output and workflow preferences. - Use
team_context/prompt-tags.mdonly when prompt tags are needed. - Load available brand or client files when the task needs that extra context; do not assume details that are only listed as available.
- Keep private user notes out of
team_context/. Private preferences belong incontext/USER.mdorcontext/MEMORY.md. - Keep client-only information in the selected client's context, not in shared team files.
- Keep skills in the root or client
.claude/skills/folders. Do not treatteam_context/as a separate AI-OS workspace.
Folder Roles
team_context/AGENTS.md- team-level instructions.team_context/team-profile.md- team identity and operating context.team_context/operating-rules.md- shared rules for how work is handled.team_context/shared-preferences.md- shared style and workflow preferences.team_context/prompt-tags.md- team prompt tags.brand_context/- shared brand context.clients/{slug}/- client-specific context.
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.