Explains this repository's shared Claude Code setup to a new teammate, covering what is committed and shared, what stays personal, and what the team-kit plugin adds. Use when someone asks how the team's Claude Code setup works or what they get by cloning the repository.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
Explain this repository's shared Claude Code setup to a teammate who has just cloned it. Read files only; don't change any.
1. Read the shared setup, skipping any file that doesn't exist:
- `.claude/settings.json`: permissions, hooks, and the marketplaces and plugins it turns on;
- `CLAUDE.md` and the files in `.claude/rules/`: the project's instructions to Claude;
- `.claude/skills/` and `.claude/agents/`: project skills and subagents;
- `.mcp.json`: project MCP servers;
- each marketplace that `.claude/settings.json` declares by a local path, and the skills and agents of the plugins it lists.
2. Name the personal files, which each teammate keeps out of the repository: `.claude/settings.local.json`, `CLAUDE.local.md` and the user folder `~/.claude/`. Don't open them. Say whether the repository's `.gitignore` lists the first two.
3. Report in three short sections: Shared with the team, Personal to you, and Added by team-kit. Give each file one line on what it does for the teammate. If a file you expected is missing, say so rather than guess what it would hold.
Keep the report short and concrete: file names and what each one changes, no general advice.
The line at the top of this page pins the label git:20261031.087ca39, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_vsbgspf6duffkqft
GET https://markdownregistry.com/api/v1/resolve?ref=wesammustafa/claude-code-everything-you-need-to-know/onboard
GET https://markdownregistry.com/api/v1/blob/70f6035c91b5140487331d5e93db0dbc2c29b2e0b85d911e90955e2f00d3f8ef
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
wesammustafa/claude-code-everything-you-need-to-know · .github/scripts/fixtures/valid-example-kit/tree/examples/intermediate/01-first-skill/dot-claude/skills/five-whys/SKILL.md · Find the root cause of a bug by asking why five times
wesammustafa/claude-code-everything-you-need-to-know · examples/advanced/06-share-your-setup/plugins/team-kit/skills/onboard/SKILL.md · Explains this repository's shared Claude Code setup to a new teammate, covering what is committed and shared, what…
wesammustafa/claude-code-everything-you-need-to-know · examples/intermediate/01-first-skill/dot-claude/skills/five-whys/SKILL.md · Finds the root cause of a bug, failure or recurring problem by asking "why" until the answer is a cause you can fix…
wesammustafa/claude-code-everything-you-need-to-know · solutions/a-6/team-marketplace/plugins/team-kit/skills/review-checklist/SKILL.md · The team's checklist for reviewing a change to linkcheck. Use before you commit or open a pull request.
wesammustafa/claude-code-everything-you-need-to-know · solutions/a-capstone/dot-claude/skills/team-review/SKILL.md · The team's review of a change to linkcheck, run the same way on a laptop and in CI. Use on a staged diff or a pull…
wesammustafa/claude-code-everything-you-need-to-know · solutions/i-1/dot-claude/skills/tdd/SKILL.md · Builds a requested feature test-first, one behavior at a time, and stops at a diff for review. Use when the user asks…
wesammustafa/claude-code-everything-you-need-to-know · solutions/i-3/dot-claude/skills/changelog/SKILL.md · Adds a one-line entry for the staged changes to CHANGELOG.md. Use when the user asks for a changelog entry.
wesammustafa/claude-code-everything-you-need-to-know · solutions/i-capstone/dot-claude/skills/check-links/SKILL.md · Runs the link checker on a folder and explains each broken link it finds, with the file, the line and a likely fix. Use…
davepoon/buildwithclaude · plugins/ciagent/skills/onboard/SKILL.md · Set up CIAgent regression testing for the AI agent in this repo — write a runner, record golden baselines, generate a…
wesammustafa/claude-code-everything-you-need-to-know · examples/advanced/06-share-your-setup/plugins/team-kit/skills/onboard/SKILL.md · Explains this repository's shared Claude Code setup to a new teammate, covering what is committed and shared, what…
clacky-ai/openclacky · lib/clacky/default_skills/onboard/SKILL.md · Onboard a new user OR curate a single piece of the assistant's inner state. Without arguments, runs the full first-run…
athola/claude-night-market · plugins/gauntlet/skills/onboard/SKILL.md · Guides a new developer through five staged challenge sets covering architecture, domain, patterns, and hardening. Use…
justxor/claude-code-pro-course · starter-kit/.claude/skills/onboard/SKILL.md · Проводит онбординг нового разработчика в проект - обзор архитектуры, запуск, ключевые потоки и первая задача…
jongwony/epistemic-protocols · epistemic-cooperative/skills/onboard/SKILL.md · Quick protocol recommendation from recent sessions, or quest-based learning through scenario, trial, and quiz.
