cco
In Claude Code: what this session costs and where the tokens go, plus the tools to cut it — /cco for the board, /cco audit, /cco…
Turn background the user keeps re-explaining or re-pasting into reusable instructions, so new chats start with it for free. Use when the user repeats the same context, rules, style guide, persona or reference text across messages or chats, says they are tired of explaining the
$ npx -y skills add egorfedorov/claude-context-optimizer --skill project-context --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/project-contextContext preview
The summary Claude sees to decide when to auto-load this skill.
Turn background the user keeps re-explaining or re-pasting into reusable instructions, so new chats start with it for free. Use when the user repeats the same context, rules, style guide, persona or reference text across messages or chats, says they are tired of explaining the
name: project-context description: Turn background the user keeps re-explaining or re-pasting into reusable instructions, so new chats start with it for free. Use when the user repeats the same context, rules, style guide, persona or reference text across messages or chats, says they are tired of explaining the same thing, or asks how to set up a Claude Project, custom instructions or a CLAUDE.md. license: MIT
Context pasted into every new chat is paid for again in every chat, and drifts each time it is retyped. Written once as instructions, it costs nothing to bring along and stays the same.
From this conversation, gather what the user keeps supplying: who they are and what they work on, the audience, rules and constraints, tone and format preferences, terms and names, recurring reference material. Ask one question at most, and only for something essential that isn't in the conversation.
**1. Instructions**, in one code block, under 250 words: short imperative lines grouped as *Context*, *Always*, *Never* and *Output*. Keep only what changes the answers. No pleasantries, no restating what Claude does anyway.
**2. Reference material**: the long texts (a style guide, a spec, a glossary, a price list) listed by name, to upload as files rather than paste into the instructions.
into its custom instructions, and add the reference files to its knowledge. Every chat started in that Project begins with both. For preferences that apply everywhere, use Settings → Profile instead.
files in the folder you give it.
the lines that matter on most tasks (build and test commands, conventions, hard rules). Long references belong in files that `CLAUDE.md` points to, read when needed.
End with one line on what this saves: for example, "This replaces the ~1,200-token briefing you've been pasting into each new chat."
See what Claude costs you, and spend less of it. Every message re-sends the whole conversation, so long chats and long coding sessions use up limits fast and recall early details worse.
In Claude Code: what this session costs and where the tokens go, plus the tools to cut it — /cco for the board, /cco audit, /cco…
Turn a long document, PDF, transcript, spreadsheet or log into a compact working digest the conversation can continue from. Use…
Continue in a new chat without losing anything — writes a compact handoff to paste into a fresh conversation. Use whenever the…
Rewrite a vague request into a precise prompt — goal, context, scope, constraints, what done looks like, output format. Use when…
Estimate how many tokens a pasted text, an attached file or the conversation so far takes, what it means for the context window…