project-context
Skill127 starsChanged 5 months agoMITView on GitHub
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.
33 other projects use a version of this.
Adopted by
Most recently taken up by
- advait/effect-durable-agenttheir own version, first seen Nov 8, 2026
- shinpr/ai-coding-project-boilerplatetheir own version, first seen Nov 8, 2026
- upex-galaxy/agentic-qa-boilerplatetheir own version, first seen Nov 7, 2026
- ritamgh/claude-skillstheir own version, first seen Nov 1, 2026
- OpenxIntelligence/Coding-Agent-Skillstheir own version, first seen Nov 1, 2026
- I-Onlabs/claude-code-skillstheir own version, first seen Oct 25, 2026
Used with
Projects with it also use code-review.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 3 projects that use this
Other versions33 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 33
- shinpr/ai-coding-project-boilerplate★ 236same name
- TenureAI/PhD-Zero★ 52same name
- upex-galaxy/agentic-qa-boilerplate★ 26same name
- sergeeey/Claude-cod-top-2026★ 9same name
- perhapsspy/project-context★ 7same name
- advait/effect-durable-agent★ 4same name
- aida-core/aida-marketplace★ 4same name
- I-Onlabs/claude-code-skills★ 4same name
- IgorBabikov/Flowcairn★ 4same name
- OpenxIntelligence/Coding-Agent-Skills★ 4same name
23 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- ccoSkill
- doc-digestSkill
- fresh-startSkill
- sharpen-promptSkill
- token-checkSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 24 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 32
claude.ai or the desktop app: create a Project, paste the instructions into its custom instructions, and add the reference files to its …
- Distinctive: line 34
Every chat started in that Project begins with both.
- Distinctive: line 36
Cowork: start each task with the instructions, and keep the reference files in the folder you give it.
“Common” is measured: kept by at least 6 in 10 of the 24 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.mdloads 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 thatCLAUDE.mdpoints 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."
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.