This is GitHub's special org .github repository. Files here become the defaults
for every repo in the MIND-Studio org that doesn't ship its own copy — plus they're
the single source of truth for our agent (Claude Code) standards.
| Path | Audience | How it reaches each repo |
|---|---|---|
profile/README.md | Humans | Rendered as the org landing page. |
CONTRIBUTING.md | Humans | Auto-applied org-wide by GitHub. |
PULL_REQUEST_TEMPLATE.md | Humans | Pre-fills every new PR. |
ISSUE_TEMPLATE/*.yml | Humans | The 🐛 / ✨ issue forms. |
CODEOWNERS | GitHub | Default reviewers for repos without their own. |
claude/mind-standards.md | Agents | Imported into each repo's CLAUDE.md (see below). |
GitHub natively propagates the human/GitHub files. The agent standards are shared by reference, not by copying.
We rely on a one-folder convention: every dev keeps all Mind repos and a clone of
this .github repo as siblings in one parent folder:
Mind/ ← any name/location; only the sibling layout matters
├── .github/ ← this repo, cloned here
│ └── claude/mind-standards.md
├── shell/ CLAUDE.md → first line: @../.github/claude/mind-standards.md
├── core/ CLAUDE.md → @../.github/claude/mind-standards.md
└── …
Each repo's CLAUDE.md imports the standards with a relative path:
@../.github/claude/mind-standards.md
@AGENTS.md # or the repo's own content belowBecause the path is relative to the importing file, it resolves on every machine
regardless of where Mind/ lives — only the sibling layout has to hold. Repo-specific
rules go in that repo's own CLAUDE.md/AGENTS.mdafter the import, so they override
the org defaults by being more specific.
- Make sure this
.githubrepo is cloned as a sibling of the repo. - Add
@../.github/claude/mind-standards.mdas the first line of the repo'sCLAUDE.md(create one if absent). - The first time Claude Code loads it, approve the one-time external-import prompt.
In a single-repo checkout with no sibling .github (e.g. CI, or a remote/cloud agent
that clones one repo), the import target is absent and the org standards simply don't load.
That's an accepted trade-off — these standards are scoped to local development under the
one-folder convention. Anything that must hold in CI belongs in that repo's own config
(workflows, lint/test gates), not here.