cc-settings plugin
The Darkroom team standards, skills, checks and hooks for Claude Code and Codex, installed with one command.
- 53 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The installer writes into the user configuration of Claude Code and Codex, including hooks.
- A `curl | bash` run executes a downloaded script, and the `/ship` skill pushes a branch and opens a PR.
Install
- Works in
Manual install
npx darkroom-settingsAny platform with Node 18 or newer. `setup.sh` has `--dry-run` for a preview.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The installer writes into the user configuration of Claude Code and Codex, including hooks.
- A `curl | bash` run executes a downloaded script, and the `/ship` skill pushes a branch and opens a PR.
This is third-party code. Review the repository files before installing.
What it does
The installer configures Claude Code and Codex to the Darkroom studio standards without replacing personal settings it does not own. Asking to fix a bug starts cause-first debugging, a request to review changes stays read-only, and ship it needs a real build and tests before publishing. Skills are called by plain words or commands: `/fix`, `/build`, `/dr-review`, `/proof-of-work`, `/ship`, `/handoff`. Large tasks are split between agents (explore, implement, test, review, security) that run in the background. A `--light` tier is meant for beginners, and a project from the starter is created with `/dr-init`.
Who it is for. Frontend teams and studios that need one rule set for Claude Code and Codex on every machine.
Good fit when
- A new machine should behave like the rest of the team, and one command, `npx darkroom-settings`, sets it up.
- Before shipping you need real typecheck, tests, lint and a UI screenshot: `/proof-of-work`.
- Change review must stay apart from edits: `/dr-review` only reads and ranks findings.
- Work pauses: `/handoff` saves state and a new session continues from the same place.
- A project moves from `CLAUDE.md` to `AGENTS.md` with `/cc migrate`.
Not a fit when
- You want minimal manual setup and do not want an installer touching the Claude Code user directory.
- The team does not follow Darkroom standards: rules and workflows are tuned to their projects.
- Network installs through `curl | bash` are forbidden by your security policy.
Example request
Explain where this project configuration is loaded, read only, citing files and lines.Limitations
The installer changes the user configuration of Claude Code and Codex and installs hooks. It can run through `curl | bash` from GitHub, so read it first; a trial run is `bash setup.sh --target=both --dry-run`. In Codex the hooks must be reviewed and trusted once in `/hooks`. Auto-update exists only on macOS and is switched on with `--auto-update=on`. Team rules and skills are tuned to the Darkroom stack and will need adapting.
How to disable. Roll back with `bun src/setup.ts --rollback` from a repository clone: it restores the newest backup. Full uninstall steps are in `docs/install.md`.
FAQ
How do I install cc-settings?
With `npx darkroom-settings` on any platform with Node 18 or newer. macOS and Linux also have `curl -fsSL .../setup.sh | bash`, and Windows has a PowerShell script.
What does the --light tier do?
It installs a minimal beginner set. Running again without the flag installs the full set: `npx darkroom-settings --light` and then without it.
What do I check after installing?
Restart Claude Code and Codex, then run `bun ~/.claude/src/scripts/whats-on.ts`: the report shows what is installed in Claude user scope.
Does it replace my personal settings?
No, the installer leaves settings it does not own alone. A backup lets you undo changes with `--rollback`.
How do I enable auto-update?
Add `--auto-update=on` to the install command. On macOS it is a daily check at 10:00 local time, and `--auto-update=off` removes it.
Discussion
No questions or reviews yet.
Related
PluginsOne-command Claude Code environment installer: a wizard sets up agents, rules, commands, skills and hooks in three profiles
Shared Claude Code settings for a team: hooks against dangerous commands, a check before finishing and skills from spec to review
A set of 24 slash commands for the Claude Code CLI: commits, review, refactoring, tests and cleanup without repeating the same prompts
A set of Claude Code utilities: background skills, expert agents, slash commands and prompt templates for development
A Claude Code plugin that limits the agent with rules and hooks and hands independent code review to Codex CLI in a review loop.
A set of 116 skills, 44 agents and safety hooks for Claude Code, Cursor, Codex, Gemini CLI and nine more editors
README in short
The repository defines team standards, workflows, safety checks and acceptance gates for Claude Code and Codex. The rest is covered in `MANUAL.md`.