← ClaudeAtlas

claude-trimlisted

Use when a user wants to trim Claude Code's startup context, system prompt, tool definitions, or skill listings by interactively choosing unused settings and measuring before/after. Not for Codex CLI, conversation compaction, or historical cost analysis.
Rhovian/niles · ★ 4 · AI & Automation · score 70
Install: claude install-skill Rhovian/niles
# Claude trim ## 1. Establish scope and dependencies Require the operator to specify global, project, or local before choosing a write target; never default to global. Global is `~/.claude/settings.json`, project is shared `.claude/settings.json`, and local is `.claude/settings.local.json`. Resolve the actual config directory and project root; inspect other layers, managed policy, launch flags, and environment that could override the target. Inventory can proceed while scope is pending. Explain who shares the target: global reaches sessions using that config directory across projects; project/local files also affect other sessions in that tree on reload or relaunch, including Niles workers. Discover supported controls and their meaning from `claude --help` and the official [settings reference](https://code.claude.com/docs/en/settings-reference) and [environment reference](https://code.claude.com/docs/en/env-vars). Confirm that documented controls are supported by the installed CLI before proposing them. Ask which workflows must survive. Preserve their command execution, file access, instructions, skills, and integrations. If running under an orchestrator such as Niles, preserve its shell commands and appended launch briefing; native delegation tools are a separate dependency to discuss. Keep mandatory repository and managed instructions. ## 2. Inventory and measure Reconstruct the intended launch: cwd, model, settings sources, tool/permission flags, appended instruction