Skip to main content
skill CX Codex

project-context — Claude Code skill: reusable project instructions

Turns the background you keep retyping into written instructions and reference files, so each new chat opens with it already in place.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add egorfedorov/claude-context-optimizer --skill project-context -a claude-code
Open on GitHub

What project-context does

The skill reads the conversation you are in and picks out what you keep supplying: your role and current work, the audience, constraints, tone and format, names and terms, recurring reference texts. If something essential is missing, it asks a single question.

You get two outputs in your own language. First, instructions in one code block, under 250 words, as short imperative lines grouped under Context, Always, Never and Output — only what actually changes answers. Second, a named list of the long material (style guide, spec, glossary, price list) that belongs in uploaded files rather than in the instructions themselves.

Then it tells you where each piece goes. On claude.ai or the desktop app that means a Project: instructions in custom instructions, files in knowledge. In Claude it is CLAUDE.md, which loads into every session, so keep only the lines that matter on most tasks — build and test commands, conventions, hard rules. Long references stay in files that CLAUDE.md points to and are read when needed. The skill closes with one line on what this saves you.

What it helps with

  • stop pasting the same briefing into every new chat
  • write a CLAUDE.md that holds only the rules that matter
  • move a style guide or glossary out of instructions and into files
  • lock in tone and output format once
  • set up a Project with custom instructions and knowledge files

Example prompts for the agent

  • I'm tired of re-explaining the same background — turn our conversation into project instructions
  • Write a CLAUDE.md for this repo: build commands, conventions and hard rules
  • Which parts of what I keep repeating should become reference files?

How to install project-context

1Skills CLI (Vercel)

npx skills add egorfedorov/claude-context-optimizer --skill project-context -a claude-code

2Manually: put the files in place

~/.claude/skills/project-context/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/project-context/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about project-context

How do I install project-context in Claude Code?

Run npx skills add egorfedorov/claude-context-optimizer --skill project-context -a claude-code. The skill lands at ~/.claude/skills/project-context/SKILL.md.

What does project-context do?

It gathers the context you repeat and writes it up as instructions under 250 words plus a list of reference files. It also says where the result belongs — a Project, custom instructions or CLAUDE.md.

Where should long reference texts go in Claude Code?

In separate files that CLAUDE.md links to. Since CLAUDE.md loads into every session, it should carry only what most tasks need.

Source text

SKILL.md · MIT
---
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
---

# Project context

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.

## Collect

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.

## Write two things, in the user's language

**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.

## Where it goes

- **claude.ai or the desktop app**: create a Project, paste 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.
- **Cowork**: start each task with the instructions, and keep the reference
  files in the folder you give it.
- **Claude Code**: a `CLAUDE.md` loads into every session, so keep there only
  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."

© egorfedorov · MIT · egorfedorov/claude-context-optimizer

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set2

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor