settings
/settings
Shows or changes project settings in project.yaml (stack, stage, budgets, modes), or per-developer overrides in project.local.yaml with --local. Use when the user wants to see the configuration, change rigor or automation, adjust a budget, or override a setting just for themselves.
- Author
- chatquill ↗
- Repository
- claude-code-websites ↗
- Licence
- MIT
- Last repository change
- 09.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 09.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Shows or changes project settings in project.yaml (stack, stage, budgets, modes), or per-developer overrides in project.local.yaml with --local. Use when the user wants to see the configuration, change rigor or automation, adjust a budget, or override a setting just for themselves.
Arguments
/settings [key | key=value | --local key=value]
Original author description
Shows or changes project settings in project.yaml (stack, stage, budgets, modes), or per-developer overrides in project.local.yaml with --local. Use when the user wants to see the configuration, change rigor or automation, adjust a budget, or override a setting just for themselves.
How it works
- Inputs
- Phases
- Output
SKILL.md preview
--- name: settings description: "Shows or changes project settings in project.yaml (stack, stage, budgets, modes), or per-developer overrides in project.local.yaml with --local. Use when the user wants to see the configuration, change rigor or automation, adjust a budget, or override a setting just for themselves." argument-hint: "[key | key=value | --local key=value]" user-invocable: true allowed-tools: Read, Edit, AskUserQuestion, Bash(bash .claude/scripts/yaml-get.sh *), Bash(bash .claude/scripts/config-set.sh *), Bash(bash .claude/scripts/set-stage.sh *) model: haiku --- # Settings Reads and writes configuration through the helper scripts only. It never hand-edits YAML, and it explains what a change affects before making it. Resolution order is described in `.claude/docs/config-resolution.md`: `project.local.yaml` → `project.yaml` → rigor expansion → defaults. ## Inputs - Argument forms: - none → show a summary - `key` → show one value and where it came from - `key=value` → change `project.yaml` - `--local key=value` → change `project.local.yaml` (gitignored, per developer) ## Phases ### Phase 1: Show With no argument, read `project.yaml` (and `project.local.yaml` if present) and print grouped tables: **Project** (name, type, stage), **Modes** (rigor, automation), **Stack** (only keys that are set), **Specialists**, **Budgets**, **a11y / i18n / privacy**. Mark values overridden locally with `(local)`. With a `key` argument, print its value from each layer and the effective one. ### Phase 2: Validate a change Before writing: - `project.stage` → only via `set-stage.sh` (values: discovery, design, build, launch, grow). Moving forward past an unpassed gate: warn and suggest `/gate-check`. - `modes.rigor` ∈ minimal / standard / full; `modes.automation` ∈ ask / batch / auto. Show what the rigor change expands to (table in `config-resolution.md`). - Do not write a knob that rigor expands to (`modes.review_mode`, `quality.tdd`, `quality.hook_strictness`, `docs.density`, `quality.gates`, `quality.audits_before_launch`) unless the user explicitly wants to pin it; explain that pinning stops rigor from changing it. - `stack.*` → warn that changing a core technology needs an ADR; suggest `/setup-stack --change <key>` instead. - Budgets must be numbers; tightening is fine, loosening a budget asks "why?" and suggests noting the reason in the PRD. - Keys deeper than two levels (`budgets.lighthouse.performance`) are not supported by `config-set.sh`; show the exact line for the user to edit by hand, or edit it yourself after asking. ### Phase 3: Write State the old → new value and its effect, ask "Change it?", and on yes run `config-set.sh [--local] key=value` (or `set-stage.sh`). Print the helper's output. ## Output `project.yaml` or `project.local.yaml`.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · chatquill/claude-code-websites | 90 | MIT |
| crisandrews/clawcode | 100 | MIT |
| cognigy/cognigy-plugin | 100 | MIT |
| repowise-dev/repowise | 100 | AGPL-3.0 |
| rvdbreemen/adr-kit | 100 | MIT |
| athenode-sdd/athenode-plugin | 100 | Apache-2.0 |
| thettwe/nyann | 100 | MIT |
| liamcain/obsidian-dev-skills | 100 | MIT |
| egsok/plan-tango | 98 | MIT |
Database snapshot: 13.11.2026 · package version f904a402ee6a (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100project-settings
Shows or changes a project setting and where its value comes from. Use to check or set one. - 100get-project-settings
Show an existing Diffy project's settings as YAML. Use when the user asks for project details, project settings, project config, "details on project <id>", or to view/get/show/export a project's configuration. Displays the exportable YAML (the dashboard "Export" format), never raw JSON. - 95plugin-settings
This skill should be used when the user asks about "plugin settings", "store plugin configuration", "user-configurable plugin", ".local.md files", "plugin state files", "read YAML frontmatter", "per-project plugin settings", or wants to make plugin behavior configurable.… - 95plugin-settings
This skill should be used when the user asks about "plugin settings", "store plugin configuration", "user-configurable plugin", ".local.md files", "plugin state files", "read YAML frontmatter", "per-project plugin settings", or wants to make plugin behavior configurable.… - 80Plugin Settings
This skill should be used when the user asks about "plugin settings", "store plugin configuration", "user-configurable plugin", ".local.md files", "plugin state files", "read YAML frontmatter", "per-project plugin settings", or wants to make plugin behavior configurable.… - 95plugin-settings
This skill should be used when the user asks about "plugin settings", "store plugin configuration", "user-configurable plugin", ".local.md files", "plugin state files", "read YAML frontmatter", "per-project plugin settings", or wants to make plugin behavior configurable.…