project-context
Skill1 starsChanged 17 days agoMITView on GitHub
Establish or refresh verified project commands, runtime facts, and repository layout when those facts are unknown, stale, or explicitly requested. Do not use for routine tasks when the existing project profile already answers the question.
34 other projects use a version of this.
Adopted by
Most recently taken up by
- Molunerfinn/skillstheir own version, first seen Nov 16, 2026
- shinpr/ai-coding-project-boilerplatetheir own version, first seen Nov 13, 2026
- advait/effect-durable-agenttheir own version, first seen Nov 8, 2026
- upex-galaxy/agentic-qa-boilerplatetheir own version, first seen Nov 7, 2026
- egorfedorov/claude-context-optimizertheir own version, first seen Nov 1, 2026
- ritamgh/claude-skillstheir own version, first seen Nov 1, 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 versions34 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 34
- shinpr/ai-coding-project-boilerplate★ 239same name
- egorfedorov/claude-context-optimizer★ 130same 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
24 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 repository14 other files it gives its agents.
- .agents/AGENTS.mdAGENTS.md
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- dev-debugSkill
- dev-planSkill
- dev-reviewSkill
- dev-ui-verifySkill
- dev-verifySkill
- dev-debugSkill
- dev-planSkill
- dev-reviewSkill
- dev-ui-verifySkill
- dev-verifySkill
- project-contextSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 25 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill to avoid rediscovering stable project facts every session.
- Distinctive: line 18
Do not run it ritualistically before every edit.
- Very specific: line 22
Read agent-core/project/profile.md if present.
- Distinctive: line 23
If the needed fact is present and still consistent with the relevant files, use it.
- Distinctive: line 32
Leave unknown values unknown rather than filling conventional defaults.
- Distinctive: line 34
Keep the profile compact. Never store secrets or environment values.
“Common” is measured: kept by at least 6 in 10 of the 25 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
Use this skill to avoid rediscovering stable project facts every session.
Trigger
Use when:
- first bootstrapping this environment in a repository,
agent-core/project/profile.mdis missing,- commands/runtime facts are stale or contradicted by the repository,
- a task depends on a project fact that the profile does not establish.
Do not run it ritualistically before every edit.
Procedure
- Read
agent-core/project/profile.mdif present. - If the needed fact is present and still consistent with the relevant files, use it.
Otherwise run:
python3 agent-core/scripts/bootstrap_project.py --write- Inspect only source files needed to resolve remaining unknowns: manifests, lockfiles, task-runner files, compose files, relevant README/AGENTS files, and CI workflows when CI behavior matters.
- Record only facts supported by repository evidence or a command actually run.
- Leave unknown values unknown rather than filling conventional defaults.
Keep the profile compact. Never store secrets or environment values.
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.

