apply-settings-profilelisted

<task> Apply the dotclaude settings profile to a settings file the user picks. Claude Code applies only `agent` and `subagentStatusLine` from a plugin, so a plugin cannot set permissions, environment variables, or model settings itself. This skill merges `profiles/recommended.json` into the chosen file, keeping the settings half of dotclaude under the user's control and easy to review. </task> <procedure> 1. Pick the scope. Use `$ARGUMENTS` if it is `user`, `project`, or `local`. Otherwise ask the user, offering: **User** (`~/.claude/settings.json`, applies everywhere; default), **Project** (`.claude/settings.json`, shared through git), **Local** (`.claude/settings.local.json`, this checkout only). 2. Preview. This writes nothing: ```bash bun "${CLAUDE_SKILL_DIR}/scripts/apply-settings.mjs" --scope <scope> ``` 3. Show the user the listed changes, grouped as below, and ask whether to apply them. | Group | Keys | Why | | --- | --- | --- | | Fast mode off | `env.CLAUDE_CODE_DISABLE_FAST_MODE=1`, `fastMode: false`, `fastModePerSessionOptIn: true`, `ultracode: false` | The env var removes the `/fast` toggle; the others keep a stray toggle, or ultracode's xhigh orchestration, from persisting. With `workflowKeywordTriggerEnabled: false`, ultracode starts only when the user picks `/effort ultracode`; no setting disables it alone, and the `xhigh` cap does not block it. | | Models | `model`, `availableModels`, `advisorModel`, `env.CLAUDE_CODE_SUBAGENT_MODEL`,