yasu551-plugins

claude-code-setup

A Claude Code plugin that standardizes team configuration across repositories. The "ESLint shared config" for Claude Code.

Every developer on your team gets different CLAUDE.md files, different hooks, different MCP servers, different settings. This plugin fixes that. Define your team's config once in a profile repo, or let the interactive wizard generate tailored config by inspecting your repo.

Quick Start

1. Register the marketplace and install

/plugin marketplace add https://github.com/yasu551/claude-code-setup
/plugin install claude-code-setup@yasu551-plugins

Note: The @yasu551-plugins qualifier distinguishes this from the official claude-code-setup@claude-plugins-official plugin. Both can coexist.

2. Create a team profile repo

team-claude-profile/
├── base/
│   ├── CLAUDE.md.sections     # Managed sections for CLAUDE.md
│   ├── hooks.json             # Team hooks
│   ├── settings.json          # Team settings
│   └── .mcp.json              # Team MCP servers
├── overlays/
│   ├── javascript/            # JS/TS-specific config
│   ├── python/                # Python-specific config
│   └── ...
└── profile.json               # Profile metadata + version

Example profile.json:

{
  "name": "myorg-claude-profile",
  "version": "1.0.0",
  "description": "Standard Claude Code configuration for MyOrg",
  "overlays": ["javascript", "python", "go", "rust", "ruby"],
  "defaultOverlay": null,
  "minimumPluginVersion": "0.1.0"
}

Example base/CLAUDE.md.sections:

## Team Standards

- Always use TypeScript strict mode
- Write tests for all new functions
- Use the team's approved MCP servers listed in .mcp.json

3. Initialize a project

Option A: From a team profile repo

/init github.com/myorg/team-claude-profile

This detects your repo type (JS, Python, Go, Rust, Ruby), fetches the profile, and applies base + overlay config. Your CLAUDE.md gets a managed section with team rules, .mcp.json and settings.json are deep merged, and hooks are installed.

Option B: Interactive wizard (existing repo, no profile needed)

/init

Without a URL, the plugin inspects your repo (language, framework, test runner, linter, CI, Docker, etc.), asks a few adaptive questions about your preferences, and generates tailored config. Every generated rule traces back to evidence found in your repo.

Option C: Vision-first project creation (empty repo)

/init

In an empty repo, choose "Set up a new project." Answer 6-8 questions about what you're building (system type, language, framework, persistence, testing, security) and get three outputs:

1. DESIGN.md — An architecture blueprint that Claude reads on every session. Components, data flow, technical decisions, open risks.
2. CLAUDE.md + settings + hooks — Claude knows your stack, conventions, and test commands from minute one.
3. Project scaffold — src/, tests/, entry point, config files (package.json, go.mod, etc.). Ready to start coding.

4. Keep it in sync

/sync

When the team profile is updated, /sync pulls the latest version and applies changes non-destructively. Your custom content outside managed sections is never touched.

Commands

/init [profile-url]

Bootstrap this repo with a team profile or interactive wizard.

With a profile URL:

• Detects repo type automatically (package.json, pyproject.toml, go.mod, Cargo.toml, Gemfile)
• Fetches profile from GitHub (or a local path)
• Applies base config + matching overlay
• Writes managed sections to CLAUDE.md
• Deep merges .mcp.json and .claude/settings.json
• Creates .claude-team-lock.json to track the applied version
• Use --force to re-initialize an already configured repo

Without a URL (interactive wizard, existing repo):

• Inspects your repo: language, framework, package manager, test runner, linter, formatter, CI, Docker, database
• Asks adaptive questions (skips what it can infer from your tooling):
  • Testing rigor: minimal / standard / strict
  • Code change style: surgical / balanced / thorough
  • Security posture: relaxed / standard / strict
• Generates tailored config from built-in stack templates
• Displays a provenance report showing what was detected and why each config was applied
• Lockfile records source: "generated" with fingerprint and answers for reproducible syncs

Without a URL (empty repo — two choices):

• Set up a new project: Asks what you're building (system type, language, framework, persistence, testing, security). Generates DESIGN.md architecture blueprint, CLAUDE.md config, and project scaffold (src/, tests/, config files). Supports JavaScript, Python, Go, Rust, Ruby with framework-specific scaffolds.
• Create a team profile: Creates a profile repo structure that other repos can consume with /init.

/sync

Update to the latest profile version.