isaacross68/context-diet-skill-win-10844

> Context Diet is a Claude Code agent skill for measuring system-prompt overhead, reviewing tool payload size, and reducing unused definitions through controlled settings.json configuration.
> Direct Download - Context Diet
Download Latest Build
## About Context Diet
Context Diet is a Claude Code optimization skill focused on identifying unnecessary system-prompt and tool-definition overhead. It uses a logging proxy to measure payload size and helps determine which tools and features contribute most to the working context.
The skill is intended for developers and teams tuning Claude Code configurations. It supports a measured workflow: inspect current usage, compare tool payloads, and apply targeted settings changes rather than disabling capabilities without review.
## Features
Measures system-prompt bloat through a logging proxy
Ranks available tools by payload size
Identifies unused tool definitions and features
Includes conservative configuration templates
Includes aggressive configuration templates
Applies deterministic merges to settings.json
Creates backups before configuration changes
Supports global, project-level, and dry-run modes
## Installation
Clone the repository into a local working directory:
bash
git clone https://github.com/isaacross68/context-diet-skill-win-10844.git
cd REPO
Ensure Node.js is available in your environment. Review the skill files and configuration templates before using the tool with Claude Code.
For an initial evaluation, use dry-run mode where available. This allows configuration changes to be inspected before they are written to a global or project settings file.
## Usage
A typical workflow is:
1. Start with the logging proxy to collect information about the current prompt and tool payloads.
2. Review the ranked tool-size results.
3. Identify definitions or features that are not needed for the target project.
4. Select a conservative or aggressive configuration template.
5. Run the configuration process in dry-run mode.
6. Apply the reviewed settings at either the project or global scope.
7. Confirm the resulting settings.json and retain the generated backup.
Example workflow:
text
Measure -> Rank payloads -> Review unused tools -> Preview changes -> Apply settings
Use project mode when the configuration should affect one repository. Use global mode when the same settings should apply across Claude Code projects.
## Configuration
Context Diet works with Claude Code settings.json configuration. Changes are designed to be deterministic and are accompanied by backups when settings are updated.
The available configuration approaches are:
Conservative: reduces selected overhead while retaining more optional functionality.
Aggressive: disables a broader set of unused definitions or features.
Dry run: previews the intended merge without applying it.
Project scope: stores changes for the current project.
Global scope: applies changes to the global Claude Code configuration.
Review each generated change before applying it, especially when switching from project-level testing to global settings.