claude-optimizer

Included with Lifetime

$97 forever

Audits and improves CLAUDE.md files to make Claude more compliant and effective. Use when the user says "optimize my CLAUDE.md", "my claude.md is too long", "improve my claude instructions", "claude isn't following my instructions", or any time they want to improve how Claude behaves in their project. CLAUDE.md is loaded on every turn — bloated instructions dilute the signal.

General

What this skill does


# Claude Optimizer

## Why This Matters

CLAUDE.md is loaded into context on every single turn. Bloated or poorly structured instructions compete with the user's actual request for attention. A well-structured CLAUDE.md dramatically improves compliance; a 10K-token wall of prose does the opposite.

## Workflow

**Step 1 — Read and measure**

```bash
wc -w path/to/CLAUDE.md
# Rough token estimate: word count ÷ 0.75
```

Also check for nested `@`-referenced files — they count against context too.

**Step 2 — Analyze against these criteria**

| Issue | Symptom | Fix |
|-------|---------|-----|
| Token bloat | >3,500 tokens | Move deep content to `@references/` files |
| Explanatory fluff | "It's important to note that...", "Please ensure..." | Delete. Claude 4 follows direct instructions. |
| Duplicated rules | Same constraint stated 3 different ways | Keep the clearest one |
| Missing structure | Safety rules buried mid-file | Safety rules first — highest attention at top |
| Prose where lists work | Paragraph describing a workflow | Numbered list or code block |
| Missing parallel hints | Sequential tool calls that could be concurrent | Add "Run X and Y in parallel" where appropriate |
| Inline content that should be referenced | Large code templates, full file examples | Move to `@path/to/reference.md` |

**Target:** 2,500–3,500 tokens. Hard limit: 5,000 tokens. Below 1,500 often means missing critical context.

**Step 3 — Propose changes with reasoning**

Show the user what you'd change and why. Don't silently rewrite the file. The user knows their workflow better than you do — some verbosity is intentional.

**Step 4 — Apply only after approval**

Rewrite the file after the user confirms. If the file is large, show a diff-style summary of what's changing rather than pasting the entire new version.

## Structure Template

```markdown
# Safety Rules (first — highest attention)
Hard constraints that cannot be overridden.

# Communication Style
How Claude should respond.

# Workflow
Step-by-step processes. Use numbered lists or code blocks.

# Project Context
What the project is, stack, key conventions.

# Commands / Tools
Available scripts, how to run them.
```

## What NOT to Remove

- Safety rules (even if they feel obvious)
- Project-specific conventions that differ from defaults
- Commands that Claude genuinely needs to run (test, lint, build)
- `@references` to files with deep context (they load lazily, low cost)

## References

| Priority | Load when | Reference |
|----------|-----------|-----------|
| 1 — High | Need CLAUDE.md structure guidelines, what to include/exclude, or token budget rules | `references/best-practices.md` |

Files: 2

Size: 6.8 KB

Complexity: 22/100

Category: General

Source: https://github.com/kriscard/kriscard-claude-plugins/tree/main/skills/dev/claude-optimizer

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts