Configuration Meta Skill

🚨 MANDATORY: Invoke docs-management First

STOP - Before providing ANY response about Claude Code configuration or settings:

• INVOKE docs-management skill

• QUERY for the user's specific topic

• BASE all responses EXCLUSIVELY on official documentation loaded

Skipping this step results in outdated or incorrect information.

Verification Checkpoint

Before responding, verify:

• Did I invoke docs-management skill?

• Did official documentation load?

• Is my response based EXCLUSIVELY on official docs?

If ANY checkbox is unchecked, STOP and invoke docs-management first.

Overview

Central authority for Claude Code configuration and settings. This skill uses 100% delegation to docs-management - it contains NO duplicated official documentation.

Architecture: Pure delegation with keyword registry. All official documentation is accessed via docs-management skill queries.

When to Use This Skill

Keywords: settings, configuration, settings.json, environment variables, permissions, sandbox, enterprise settings, managed-settings.json, user settings, project settings, local settings, tools, hooks configuration, model configuration, plugin settings, precedence

Use this skill when:

• Configuring settings.json files

• Understanding settings hierarchy and precedence

• Setting up permission rules (allow, deny, ask)

• Configuring sandbox settings

• Managing enterprise policies

• Setting environment variables

• Understanding available tools

• Configuring plugin settings

• Troubleshooting configuration issues

Keyword Registry for docs-management Queries

Use these keywords when querying docs-management skill for official documentation:

Settings Files

Topic Keywords

Overview "settings", "settings.json", "configuration files"

User Settings "user settings", "~/.claude/settings.json"

Project Settings ".claude/settings.json", "project settings"

Local Settings "settings.local.json", "local settings"

Enterprise "managed-settings.json", "enterprise managed policy"

Available Settings

Topic Keywords

Settings Table "available settings", "settings options"

Model Setting "model setting", "model override"

Hooks Setting "hooks setting", "disableAllHooks"

Output Style "outputStyle setting", "output style config"

Status Line "statusLine setting", "status line config"

API Key Helper "apiKeyHelper", "custom script auth"

Keybindings "keybindings.json", "keyboard shortcuts config", "custom keybindings"

Plans Directory "plansDirectory", "plans directory setting", "plan file storage"

Turn Duration "showTurnDuration", "turn duration display", "timing display"

Permissions

Topic Keywords

Permission Settings "permission settings", "allow deny ask rules"

Allow Rules "permissions allow", "allow tool rules"

Deny Rules "permissions deny", "deny tool rules", "excluding sensitive files"

Ask Rules "permissions ask", "confirmation rules"

Default Mode "defaultMode", "permission modes"

Sandbox

Topic Keywords

Sandbox Settings "sandbox settings", "bash sandboxing"

Sandbox Network "sandbox network", "allowUnixSockets", "allowLocalBinding"

Excluded Commands "excludedCommands", "sandbox exclusions"

Auto Allow "autoAllowBashIfSandboxed", "auto-approve sandboxed"

Precedence

Topic Keywords

Settings Precedence "settings precedence", "configuration hierarchy"

Override Order "enterprise project user precedence", "settings override"

Environment Variables

Topic Keywords

Environment Variables "environment variables", "ANTHROPIC_API_KEY"

Model Variables "ANTHROPIC_MODEL", "model environment"

Proxy Variables "HTTP_PROXY", "HTTPS_PROXY", "proxy configuration"

Telemetry Variables "DISABLE_TELEMETRY", "telemetry settings"

Bedrock Variables "CLAUDE_CODE_USE_BEDROCK", "bedrock environment"

Vertex Variables "CLAUDE_CODE_USE_VERTEX", "vertex environment"

Temp Directory "CLAUDE_CODE_TMPDIR", "temporary directory", "temp file location"

Background Tasks "CLAUDE_CODE_DISABLE_BACKGROUND_TASKS", "disable background tasks", "background process control"

Plugins

Topic Keywords

Plugin Configuration "plugin configuration", "enabledPlugins"

Marketplaces "extraKnownMarketplaces", "plugin marketplaces config"

JSON Schema

Topic Keywords

Custom Schema "settings schema", "JSON schema", "claude-code-settings.schema.json"

Schema Location "custom schema", "extended schema", "SchemaStore"

Schema Updates "update schema", "schema refresh", "/update-settings-schema"

Schema Validation "validate schema", "schema compliance", "draft-07"

Tools

Topic Keywords

Available Tools "tools available to Claude", "tool table"

Tool Permissions "tool permissions", "permission required tools"

Quick Decision Tree

What do you want to do?

• Configure settings file -> Query docs-management: "settings.json", "available settings"

• Set up permissions -> Query docs-management: "permission settings", "allow deny rules"

• Configure sandbox -> Query docs-management: "sandbox settings", "bash sandboxing"

• Understand precedence -> Query docs-management: "settings precedence", "configuration hierarchy"

• Set environment variables -> Query docs-management: "environment variables", specific variable name

• Configure enterprise policy -> Query docs-management: "managed-settings.json", "enterprise managed policy"

• Set up plugin settings -> Query docs-management: "plugin configuration", "enabledPlugins"

• Understand available tools -> Query docs-management: "tools available to Claude"

• Exclude sensitive files -> Query docs-management: "excluding sensitive files", "deny rules"

• Configure model -> Query docs-management: "model setting", "ANTHROPIC_MODEL"

• Troubleshoot config issues -> Query docs-management: "configuration troubleshooting" + specific issue

Topic Coverage

⚠️ STALENESS WARNING: The lists below are for navigation reference only. ALWAYS query docs-management for the authoritative, current list of settings fields, environment variables, and configuration options. These change with Claude Code releases.

Settings File Types

Query Pattern: docs-management: "settings.md file types locations"

• User settings, project settings, local settings

• Enterprise policies (managed settings)

• Platform-specific paths

Key Settings Options

Query Pattern: docs-management: "settings.md available settings table"

Categories include: authentication helpers, cleanup, announcements, environment, permissions, hooks, model, output styling, status line. Query docs-management for the complete list of current settings fields.

Permission Settings

Query Pattern: docs-management: "settings.md permission settings allow deny ask"

Covers: allow/deny/ask rules, additional directories, default mode, bypass mode controls.

Sandbox Settings

Query Pattern: docs-management: "settings.md sandbox settings network"

Covers: enabled flag, auto-allow behavior, excluded commands, network settings (sockets, binding, proxies).

Settings Precedence

Query Pattern: docs-management: "settings.md precedence hierarchy"

Order (query docs-management for current precedence rules).

Environment Variable Categories

Query Pattern: docs-management: "settings.md environment variables"

Categories: authentication, model config, provider settings, proxy, telemetry, tool behavior.

Plugin Configuration

Query Pattern: docs-management: "settings.md plugin configuration enabledPlugins"

Covers: enabled plugins map, marketplace sources.

Tools Available to Claude

Query Pattern: docs-management: "interactive-mode.md tools available to Claude"

Categories: file operations, execution, user interaction, specialized tools, notebook editing.

Delegation Patterns

Standard Query Pattern

User asks: "How do I configure permissions?"

1. Invoke docs-management skill
2. Use keywords: "permission settings", "allow deny rules"
3. Load official documentation
4. Provide guidance based EXCLUSIVELY on official docs

Multi-Topic Query Pattern

User asks: "I want enterprise settings with sandbox and restricted permissions"

1. Invoke docs-management skill with multiple queries:
   • "managed-settings.json", "enterprise managed policy"
   • "sandbox settings", "bash sandboxing"
   • "permission settings", "deny rules"
2. Synthesize guidance from official documentation

Troubleshooting Pattern

User reports: "My settings aren't taking effect"

1. Invoke docs-management skill
2. Use keywords: "settings precedence", "configuration hierarchy"
3. Guide user through precedence rules from official docs

Troubleshooting Quick Reference

Issue Keywords for docs-management

Settings not applied "settings precedence", "configuration hierarchy"

Permission denied "permission settings", "deny rules"

Sandbox blocking commands "sandbox settings", "excludedCommands"

Environment variable not working "environment variables", specific variable name

Enterprise policy override "managed-settings.json", "enterprise policy"

Plugin not loading "plugin configuration", "enabledPlugins"

Tool not available "tools available", "tool permissions"

Repository-Specific Notes

This repository has project-level settings in .claude/settings.json including:

• Custom hooks configuration

• Permission rules

• Model settings

When modifying this repository's settings, ensure changes align with the hook-management skill guidance for hook configurations.

Auditing Settings

This skill provides the validation criteria used by the settings-auditor agent for formal audits.

Audit Resources

Resource Location Purpose

Audit Framework references/audit-framework.md

Query guides and scoring criteria

Scoring Categories

Category Points Key Criteria

JSON Validity 20 Valid syntax, well-formed

Schema Compliance 25 Only valid settings options

Permission Rules 25 Valid patterns, appropriate restrictions

Environment Config 15 Valid env vars, no secrets

Precedence Awareness 15 Correct scope usage

Thresholds: 85+ = PASS, 70-84 = PASS WITH WARNINGS, <70 = FAIL

Related Agent

The settings-auditor agent (Haiku model) performs formal audits using this skill:

• Auto-loads this skill via skills: settings-management

• Uses audit framework and docs-management for rules

• Generates structured audit reports

• Invoked by /audit-settings command

External Technology Validation

When auditing settings that reference external technologies (scripts, packages, runtimes), the auditor MUST validate claims using MCP servers before flagging findings.

Technologies Requiring MCP Validation:

• .NET/C# scripts: Validate with microsoft-learn + perplexity

• Node.js/npm packages: Validate with context7 + perplexity

• Python scripts/packages: Validate with context7 + perplexity

• Shell scripts: Validate with perplexity

• Any version-specific claims: ALWAYS validate with perplexity

Validation Rule:

Never flag a technology usage as incorrect without first:

• Querying appropriate MCP server(s) for current documentation

• Verifying with perplexity for recent changes (especially .NET 10+)

• Documenting MCP sources in the finding

Stale Data Warning:

• microsoft-learn can return cached/outdated documentation

• ALWAYS pair microsoft-learn with perplexity for version verification

• Trust perplexity for version numbers and recently-released features

VS Code Integration

This plugin provides an extended JSON Schema for Claude Code settings that enables IntelliSense in VS Code.

Schema Association Options

Option 1: Workspace Settings (Recommended)

Add to .vscode/settings.json :

{ "json.schemas": [ { "fileMatch": ["/.claude/settings.json", "/.claude/settings.local.json"], "url": "./plugins/claude-ecosystem/skills/settings-management/references/claude-code-settings.schema.json" } ] }

Option 2: In-File Schema Reference

Add at the top of your settings.json :

{ "$schema": "https://raw.githubusercontent.com/melodic/claude-code-plugins/main/plugins/claude-ecosystem/skills/settings-management/references/claude-code-settings.schema.json" }

Note: In-file $schema references override workspace settings. Use workspace settings for flexibility.

Environment Variable IntelliSense

The schema includes 68+ environment variables with:

• Full autocomplete for all official env var names

• Descriptions and categories for each variable

• enum: ["0", "1"] for boolean flags (type safety)

• Deprecation markers for obsolete variables

Try it: In your settings.json , type "env": { "A and VS Code will autocomplete ANTHROPIC_API_KEY , ANTHROPIC_MODEL , etc.

Schema Version

The schema tracks Claude Code versions and includes version history:

Field Purpose

x-schema-version

Plugin schema version (e.g., 1.1.0)

x-claude-code-version

Claude Code version tracked

x-env-var-count

Number of env vars defined (68+)

x-last-updated

Last schema update date

Keeping Schema Updated

Run /update-settings-schema to sync the schema with latest canonical documentation. This extracts new env vars and settings from the official docs.

References

Official Documentation (via docs-management skill):

• Primary: "settings" documentation

• Related: "iam", "hooks", "sandboxing", "model-config", "network-config"

Repository-Specific:

• Project settings: .claude/settings.json

• Hooks configuration: .claude/hooks/

Version History

v1.1.0 (2026-01-16): Added v2.1.4-v2.1.9 keyword registry entries

• Added keybindings.json setting keywords (v2.1.7)

• Added plansDirectory setting keywords (v2.1.9)

• Added showTurnDuration setting keywords (v2.1.7)

• Added CLAUDE_CODE_TMPDIR env var keywords (v2.1.5)

• Added CLAUDE_CODE_DISABLE_BACKGROUND_TASKS env var keywords (v2.1.4)

v1.0.0 (2025-11-26): Initial release

• Pure delegation architecture

• Comprehensive keyword registry

• Quick decision tree

• Topic coverage for all configuration features

• Troubleshooting quick reference

Last Updated

Date: 2026-01-16 Model: claude-opus-4-5-20251101