← ClaudeAtlas

update-configlisted

Use when updating settings.json, environment variables, or CLI tool permissions
imMamdouhaboammar/get-fable · ★ 4 · AI & Automation · score 70
Install: claude install-skill imMamdouhaboammar/get-fable
# Update Config Skill Modify Claude Code configuration by updating settings.json files. ## When Hooks Are Required (Not Memory) If the user wants something to happen automatically in response to an EVENT, they need a **hook** configured in settings.json. Memory/preferences cannot trigger automated actions. **These require hooks:** - "Before compacting, ask me what to preserve" → PreCompact hook - "After writing files, run prettier" → PostToolUse hook with Write|Edit matcher - "When I run bash commands, log them" → PreToolUse hook with Bash matcher - "Always run tests after code changes" → PostToolUse hook **Hook events:** PreToolUse, PostToolUse, PreCompact, PostCompact, Stop, Notification, SessionStart ## CRITICAL: Read Before Write **Always read the existing settings file before making changes.** Merge new settings with existing ones - never replace the entire file. ## CRITICAL: Use AskUserQuestion for Ambiguity When the user's request is ambiguous, use AskUserQuestion to clarify: - Which settings file to modify (user/project/local) - Whether to add to existing arrays or replace them - Specific values when multiple options exist ## Decision: /config command vs Direct Edit **Suggest the `/config` slash command** for these simple settings: - `theme`, `editorMode`, `verbose`, `model` - `language`, `alwaysThinkingEnabled` - `permissions.defaultMode` **Edit settings.json directly** for: - Hooks (PreToolUse, PostToolUse, etc.) - Complex permission rules (allow/deny ar