plugins/claude-code-expert/skills/claude-code-setup/SKILL.md
Deploy or audit the full 5-layer Claude Code stack (CLAUDE.md + skills + hooks + agents + memory) in a repository. Use this skill whenever the user runs /cc-setup, asks to "set up Claude Code on this repo", "configure a new repo for Claude", "audit my Claude Code setup", "generate CLAUDE.md", "install hooks", "wire up the 4-layer stack", or starts work in a repo that lacks .claude/. Also triggers on "bootstrap Claude Code", "add claude setup", or whenever a fresh repo needs Claude Code configuration.
npx skillsauth add markus41/claude claude-code-setupInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Deploys all five layers of the modern Claude Code stack. Detects the project's shape, picks defaults from the detection matrix, and generates configuration that hits the ground running.
| Layer | Artifact | Loaded |
|---|---|---|
| L0 — MCP reference | plugin's MCP tools (queryable) | on demand |
| L1 — CLAUDE.md | CLAUDE.md (≤120 lines, routing) | always |
| L2 — Skills | .claude/skills/*/SKILL.md | frontmatter always; body on trigger |
| L3 — Hooks | .claude/hooks/*.sh + .claude/settings.json | on lifecycle events |
| L4 — Agents | .claude/agents/*.md | on invocation |
| L5 — Memory | engram (tier 1) + Obsidian vault (tier 2) + .claude/rules/ (tier 3) | tier 3 always; others on demand |
Run in order; short-circuit on first hit per category.
| Category | Checks | MCP tool for config |
|---|---|---|
| Language | package.json, tsconfig.json, pyproject.toml, go.mod, Cargo.toml, *.csproj, pom.xml | cc_kb_lsp_config(language) |
| Framework | next.config.*, nuxt.config.*, vite.config.*, fastapi/flask imports, manage.py | — |
| Infra | Dockerfile, docker-compose*, kubernetes/, helm/, terraform/, .github/workflows/ | — |
| DB | prisma/, drizzle.config.*, knexfile.*, .env*DATABASE_URL*, supabase/ | — |
| Test | jest.config*, vitest.config*, pytest.ini, cypress.config*, playwright.config* | — |
| Monorepo | turbo.json, nx.json, pnpm-workspace.yaml, lerna.json, rush.json | — |
Build a project fingerprint. Count LOC, list detected stacks, identify existing .claude/ contents.
| Preset | Profile |
|---|---|
| developer (default) | Permissive for local dev, 4 layers configured, standard hooks |
| power-user | Full 5 layers, all detected MCPs, comprehensive hooks, model cascading |
| ci-cd | Restrictive, audit-only hooks, Haiku model |
| secure | Strict read-only default, deny network tools |
| minimal | CLAUDE.md only |
| team | Shared conventions, no local overrides |
Template: routing table + build commands + "don't touch" list. ≤120 lines. See MCP cc_docs_resolve_task for task-routing rows.
Add an Obsidian routing block if the vault is detected (existing Obsidian MCP or path C:/Users/MarkusAhling/obsidian/ readable). Content from memory/rules/cc-obsidian-intro.md.
Small set of skills tied to detected stack. Prefer delegating to the plugin's MCP KB rather than inlining large skill bodies.
Install 2-3 baseline hooks from MCP KB:
protect-sensitive-files (fetch via cc_kb_hook_recipe)auto-format-after-editsession-init, on-stop, lessons-learned-captureCopy role-based agents that match the repo's work type. Always include audit-reviewer. Include security-compliance-advisor if auth/payment detected.
Copy plugin baseline rules into target:
.claude/rules/cc-always.md ← plugin memory/rules/cc-always.md
.claude/rules/cc-obsidian-intro.md ← plugin memory/rules/cc-obsidian-intro.md
.claude/rules/cc-patterns.md ← plugin memory/rules/cc-patterns.md (latest snapshot)
CLAUDE.md references all three via @.claude/rules/*.md notation (auto-loaded every session).
Phase 10 audit: 0–100 score across 5 layers + MCP + LSP + memory + cost optimization. Output markdown report.
/cc-setup --audit)Skips generation; scores the existing setup. Reports gaps and suggests next steps. Does not modify any file.
| Need | Tool |
|---|---|
| Hook recipe | cc_kb_hook_recipe(name) |
| LSP config | cc_kb_lsp_config(language) |
| Topology kit | cc_kb_topology_kit(name) |
| Workflow pack | cc_kb_workflow_pack(name) |
| Autonomy profile | cc_kb_autonomy_profile(profile) |
| Pattern template | cc_kb_pattern_template(name) |
| Channel server | cc_kb_channel_server(name) |
| Model recommendation | cc_docs_model_recommend(task, budget?) |
| Hook pack shortlist | cc_docs_hook_pack_recommend(signals) |
| Topology shortlist | cc_docs_team_topology_recommend(task, complexity, team_size) |
development
Enhanced plan-authoring skill with Pre-Writing context gathering, task metadata, non-TDD templates, Red Flags, telemetry, and an automated plan linter. Use when you have a spec or requirements for a multi-step task, before touching code.
tools
Documentation intelligence engine with graph-based API docs, algorithm library, and drift detection
tools
Ultraplan cloud planning — kick off a plan in the cloud from your terminal, review and revise in the browser, then execute remotely or send back to CLI
tools
--- name: mcp description: Configure MCP servers for Claude Code — stdio vs HTTP, authentication, Tools/Resources/Prompts distinction, channels (CI webhook, mobile relay, Discord bridge, fakechat), and cost of always-loaded tools. Use this skill whenever adding an MCP server, debugging connection issues, choosing between MCP Tools vs Prompts vs Resources, installing channel servers, or managing .mcp.json. Triggers on: "MCP server", "mcp config", "add Obsidian MCP", "install context7", "channels"