agentsclimarketplace

Code env setup

Skill joaquimscosta/arkhe-claude-plugins/plugins/devtools/skills/code-env-setup

Supercharge Claude Code with 109 specialized components — 22 agents, 32 commands, 55 skills across 13 modular plugins. Deep reasoning, autonomous dev loops, DDD architecture, design system enforcement, git automation, and more.

Install
npx -y skills add joaquimscosta/arkhe-claude-plugins --skill code-env-setup

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 21 stars21 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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".

SKILL.md

3.8 KB, as published. Nobody here has run it

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:

    python3 ${CLAUDE_SKILL_DIR}/scripts/detect_setup.py <project-root>
    
  2. 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.

  3. Cross-reference detection JSON against guide recommendations to identify what is missing or incomplete.

  4. Detect MCP servers separately via 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):
#CategoryGuide SectionWhat It Configures
1Global CLAUDE.mdSection 1~/.claude/CLAUDE.md — security NEVER rules, account config
2Project ScaffoldingSection 2.claude/ dirs, .env.example, .gitignore, CLAUDE.md
3MCP ServersSection 3Install recommended servers via claude mcp add
4HooksSection 7~/.claude/hooks/block-secrets.py, hooks in settings.json
5Custom AgentsSection 10~/.claude/agents/ starter agent files
6KeybindingsSection 13~/.claude/keybindings.json
7SettingsSection 13Language, 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 for per-category question flows.

  2. Show confirmation summary — table of all proposed CREATE/MODIFY/SKIP actions. Ask user to confirm before executing.

  3. Execute changes — create files, install MCP servers, update settings.

  4. 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

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.