Orchestrate multi-agent AI coding workflows with parallel task delegation, automated code review, and quality gates for Next.js/React projects. Includes checkpoint/restore, session persistence, and git-synced issue tracking.
Code cleanup agent that suggests improvements and auto-removes dead code only. Reviews codebase for consolidation opportunities, reports findings for approval. Supports team mode for parallel scanning on large codebases. DELEGATE when user asks: - "Find duplicate code" / "Check for redundancy" / "DRY this up" - "Consolidate similar logic" / "Clean up overlapping code" - "Find dead code" / "Remove unused code" / "Clean up the codebase" - After implementer completes changes (before pushing) - "before push" / "pre-push review" / "final cleanup" RETURNS: Dead code auto-removed, consolidation recommendations for approval
Fast codebase exploration, navigation, and documentation fetching. Read-only research agent. DELEGATE when user asks: - "How does X work?" / "Where is X?" / "Find X" - "What files handle Y?" / "Show me the Z code" - "Map the architecture" / "What's the project structure?" - "Find docs for X" / "How do I use Y library?" / "API reference for Z" - "Explain this API" / "What are the options for X?" - "Why is X done this way?" / "Is X safe to change?" / "What happens when Y?" - "Where should I put Z?" / "What's the best practice for X?" - Expert second opinions, blast-radius questions, evidence-based answers - Any exploration before making changes RETURNS: File locations, architecture maps, dependency graphs, code summaries, documentation, evidence-based answers with file:line citations
Code execution agent. Writes, edits, and tests code based on approved plans. DELEGATE when user asks: - "Implement X" / "Build X" / "Create X" / "Add X" - "Fix this bug" / "Make this change" / "Update the code" - "Apply the plan" / "Execute these changes" - After planner has created a roadmap REQUIRED BRIEFING — every prompt MUST contain actual content, not references: 1. The user's original ask, verbatim — not a paraphrase 2. Exact file paths and line ranges to modify — as a subagent this agent gets only your prompt, with none of the conversation context or files you've already read 3. The specific change to make — paste the planner output or quote the recommended fix line-by-line. Never write "based on findings" or "according to plan" 4. The verification command (e.g. `bun test`, `npm run build`, repro steps) 5. Scope boundary — which adjacent code is OFF-LIMITS Thin prompts ("implement based on plan", "fix the bug", "build it") cause regressions. RETURNS: Working code, test results, implementation status, files created/modified
Multi-agent orchestrator. Coordinates complex tasks across multiple agents in parallel. DELEGATE when user asks: - "Implement full feature X" / "Build entire Y system" - "Refactor X across the codebase" / "Large-scale change" - Any task spanning 3+ agents or requiring coordination - Complex debugging requiring multiple perspectives RETURNS: Orchestration status, synthesized results from sub-agents, progress tracking
Task breakdown and architecture planning. Creates detailed implementation roadmaps. DELEGATE when user asks: - "Plan X" / "How should we approach X?" / "Break down X" - "What's the best way to implement Y?" - "Create a roadmap for Z" / "Design the architecture" - Before any multi-file change or complex feature RETURNS: Numbered task lists, dependency graphs, ADRs, risk assessments, phase breakdowns
Autonomous skill-prompt optimization — Karpathy-style mutate/score/keep loop on SKILL.md. Triggers "autoresearch", "optimize skill", "tune", "evolve" a skill, "prompt optimization".
Build feature/page/integration end-to-end with GO/NO-GO gate. For components use `/component`, hooks `/hook`. Triggers "build a feature/page", "implement feature", "add feature", "build integration".
Sync cc-settings with upstream Claude Code (maintainer) or pull the latest cc-settings (user). Triggers "sync with claude code", "changelog sync", "upstream sync" (sync mode); "update cc-settings", "refresh my install" (update mode).
Mid-task rollback points — save/restore state before risky ops (refactors, migrations, destructive edits). For end-of-session save use `/handoff`. Triggers "checkpoint", "snapshot", "before this risky op", "rollback to", "list checkpoints", pre-refactor save.
Create UI component / widget / reusable piece. Triggers "create component", "new component", "add component", or naming a component (Button, Header, Card).
External network access
Connects to servers outside your machine
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Claude Code configuration for the Darkroom team — installs agents, skills, hooks, and coding standards into ~/.claude/.
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/darkroomengineering/cc-settings/main/setup.sh)
Windows (PowerShell):
powershell -ExecutionPolicy Bypass -c "irm https://raw.githubusercontent.com/darkroomengineering/cc-settings/main/setup.ps1 | iex"
Both one-liners clone the repo and run the installer. To pass flags (--light, --dry-run, …), clone first and run the bootstrap from the checkout: bash setup.sh --light or .\setup.ps1 --light.
Requires Bun ≥ 1.1.30 and git — the bootstrap installs Bun automatically if missing. Re-installs are non-destructive: existing permissions, custom hooks, and local overrides survive.
Restart Claude Code after install.
New to Claude Code and don't want the full surface? Install the light profile — raw Claude Code with only two additions: the statusline and the share-learning skill.
bash setup.sh --light # macOS / Linux
.\setup.ps1 --light # Windows (PowerShell)
No custom CLAUDE.md, agents, rules, profiles, MCP servers, hooks (beyond the statusline), or effort overrides — just vanilla Claude Code so you're not overwhelmed. Re-run bash setup.sh without --light any time to upgrade to the full config; both tiers are permanently supported. See MANUAL.md for the full comparison.
~/.claude/
├── AGENTS.md # Portable coding standards (read by all AI tools)
├── CLAUDE.md # Claude-Code-specific config
├── settings.json # Composed from config/*.json (permissions, hooks, MCP)
├── agents/ # 9 specialized subagents
├── skills/ # 34 auto-invocable skills
├── profiles/ # Stack contexts: nextjs, react-native, tauri, webgl, maestro, react-router
├── rules/ # Path-conditioned rules (load on-demand by file type)
└── src/ # Hook + script implementations (TypeScript)
Repo → install mapping:
| Repo dir | Installs to |
|---|---|
agents/ | ~/.claude/agents/ |
skills/ | ~/.claude/skills/ |
rules/ | ~/.claude/rules/ |
profiles/ | ~/.claude/profiles/ |
config/*.json | ~/.claude/settings.json (composed) |
bash setup.sh # Install / update (full profile)
bash setup.sh --light # Light profile: raw CC + statusline + share-learning only
bun src/setup.ts --rollback # Restore the previous backup
bun src/setup.ts --dry-run # Preview what would change
bun run compose # Preview the composed settings.json
bun run lint:skills # Validate skill frontmatter + cap (≤40)
bun run audit:hooks # Classify hooks as trusted/unknown/suspicious
bun run typecheck # TypeScript check
bun test # Run all tests
| Doc | What's in it |
|---|---|
| MANUAL.md | Every skill — how to invoke it, what it does |
| AGENTS.md | Coding standards and guardrails (source of truth) |
| CLAUDE.md | Claude-Code config, delegation rules, effort levels |
| docs/profiles.md | Stack-specific profiles (Next.js, RN, Tauri, WebGL, React Router) |
| docs/skill-authoring.md | Writing new skills |
| CHANGELOG.md | Release history |
Shared config means every engineer on the team runs the same agents, the same guardrails, and the same coding standards — no per-machine drift. AGENTS.md is the open standard for AI coding instructions and is also read by Codex, Cursor, Copilot, and Windsurf, so the rules follow you across tools.
darkroom.engineering · MIT
npx claudepluginhub darkroomengineering/cc-settings --plugin darkroomComplete collection of battle-tested Claude Code configs from an Anthropic hackathon winner - agents, skills, hooks, and rules evolved over 10+ months of intensive daily use
Essential Claude Code extensions: core agents, hooks, commands, and universal tools
Bootstrap and customize dotclaude in any project. Copies the full template into .claude/ if missing, then tunes every config file to match your stack.
oh-my-zsh for Claude Code — 11 agents, 33 commands, 24 skills, 15 hooks + 9 examples (21 events), 9 rules, 4 MCP (minimal: playwright, context7, jina-reader, chrome-devtools@0.23.0). One-line install: curl -fsSL https://raw.githubusercontent.com/sangrokjung/claude-forge/main/install.sh | bash
Battle-tested configuration system for Claude Code agents: 28 architectural principles (incl. P-28 Feature-Layer Architecture for project-knowledge-as-a-navigable-tree), 19 safety hooks, 23 skills (incl. /layer-new + /feature-new for ULTRAPACK-style feature narratives), 16 alternative comparisons, 12 templates (incl. extended kb-skeleton with docs/layers/), diagnostic scripts (incl. build_kb_graph.py + validate_kb_links.py). Pairs with mclaude for multi-session coordination.
Unified capability management center for Skills, Agents, and Commands.