Skip to content

wesammustafa/Claude-Code-Quest / examples/advanced/06-share-your-setup/plugins/team-kit/skills/onboard

onboard

Verified

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.

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.

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 469kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 321kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 321kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 321kUpdated Claude CodeCodexVerifiedInstall