Receber por email
← Voltar para o catálogo

code-env-setup

Interactive Claude Code environment setup wizard. Detects existing configuration, guides through best-practice setup for Global CLAUDE.md, project scaffolding, MCP servers, hooks, custom agents, keybindings, and settings. Use when user runs /devtools:code-env-setup, mentions "setup claude code", "configure claude", "claude code setup", "environment setup", or "initialize claude code".

16estrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add joaquimscosta/arkhe-claude-plugins

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/code-env-setup/svg)](https://www.skillteca.com.br/skills/code-env-setup)

Alerta por categoria

Receba novas skills de Design e Frontend toda segunda

1 email curto, só com as skills novas de Design e Frontend. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Claude Code Setup Wizard

Interactive environment setup following the Claude Code Guide.

Pre-flight

Run the detection script to understand current state:

python3 ${CLAUDE_SKILL_DIR}/scripts/detect_setup.py

Two-Phase Workflow

Phase 1: Detect

  1. Run the detector on the project root:

``bash python3 ${CLAUDE_SKILL_DIR}/scripts/detect_setup.py <project-root> ``

  1. Fetch the guide via WebFetch:

`` https://raw.githubusercontent.com/joaquimscosta/arkhe-claude-plugins/main/docs/CLAUDE_CODE_GUIDE.md `` If WebFetch fails (network error, 404), warn the user and proceed using LLM knowledge only.

  1. Cross-reference detection JSON against guide recommendations to identify what is missing or incomplete.
  1. Detect MCP servers separately via Bash:

``bash claude mcp list ``

Phase 2: Configure

  1. Present category selection using AskUserQuestion (multiSelect: true). Show detection status for each category (configured / partially configured / not configured):

| # | Category | Guide Section | What It Configures | |---|----------|---------------|--------------------| | 1 | Global CLAUDE.md | Section 1 | ~/.claude/CLAUDE.md — security NEVER rules, account config | | 2 | Project Scaffolding | Section 2 | .claude/ dirs, .env.example, .gitignore, CLAUDE.md | | 3 | MCP Servers | Section 3 | Install recommended servers via claude mcp add | | 4 | Hooks | Section 7 | ~/.claude/hooks/block-secrets.py, hooks in settings.json | | 5 | Custom Agents | Section 10 | ~/.claude/agents/ starter agent files | | 6 | Keybindings | Section 13 | ~/.claude/keybindings.json | | 7 | Settings | Section 13 | Language, background tasks in settings.json |

If user passed a specific category as argument (e.g., /devtools:code-env-setup hooks), skip the selection and go directly to that category.

  1. Walk through each selected category with targeted AskUserQuestion calls. See [WORKFLOW.md](WORKFLOW.md) for per-category question flows.
  1. Show confirmation summary — table of all proposed CREATE/MODIFY/SKIP actions. Ask user to confirm before executing.
  1. Execute changes — create files, install MCP servers, update settings.
  1. Post-setup summary — show what was configured, next steps, and remind user they can re-run /devtools:code-env-setup for incremental updates.

Key Rules

  • Never overwrite existing files without asking. Always offer merge/replace/skip.
  • Detect first — skip items already configured.
  • Use AskUserQuestion for every decision. Do not assume user preferences.
  • Merge settings — when updating settings.json, read existing content first and deep-merge.
  • MCP servers — ask scope (global -s user vs project -s project) before installing.

Guide Reference

Fetch at runtime — do not cache or embed:

  • Claude Code Guide: https://raw.githubusercontent.com/joaquimscosta/arkhe-claude-plugins/main/docs/CLAUDE_CODE_GUIDE.md

References

  • Workflow: See [WORKFLOW.md](WORKFLOW.md) for per-category setup flows
  • Examples: See [EXAMPLES.md](EXAMPLES.md) for example setup sessions
  • Troubleshooting: See [TROUBLESHOOTING.md](TROUBLESHOOTING.md) for common issues
  • Detection Script: See [scripts/detect_setup.py](scripts/detect_setup.py) for detection logic
Compartilhar X LinkedIn