project-context
Skill0 starsChanged 3 months agoMITView on GitHub
Create and maintain PROJECT_CONTEXT.md - the concise navigation and architecture map of a Frappe application. Full first-time analysis, incremental updates keyed to analyzed_commit, and strict update-decision rules.
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
- egorfedorov/claude-context-optimizertheir own version, first seen Nov 1, 2026
- ritamgh/claude-skillstheir own version, first seen Nov 1, 2026
- OpenxIntelligence/Coding-Agent-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 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
- egorfedorov/claude-context-optimizer★ 127same 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
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 repository8 other files it gives its agents.
- codex-reviewSkill
- deploymentSkill
- feature-changelogSkill
- frappe-taskSkill
- git-finalizationSkill
- task-implementationSkill
- task-planningSkill
- testing-taskSkill
The file
Files
Project Context Skill
Maintains docs/ai-context/PROJECT_CONTEXT.md in the target app
repository: a concise map
that prevents future agents from rereading the whole repository. It is not
a code dump, not a Git history, not a feature archive, not a task tracker.
When to Use
- During
initwhendocs/ai-context/PROJECT_CONTEXT.mdis missing → first-time analysis (references/full-project-analysis.md). - During
initorstartwhen it exists → incremental analysis (references/incremental-analysis.md). - During finalization when the approved task changed architecture or navigation → content update per (references/context-update-rules.md).
Inputs
- Target app repository root (from
bin/frappe-workflow detect --json). - Template:
templates/project/PROJECT_CONTEXT.md(plugin repository). - Current HEAD (
git rev-parse HEAD) and, for incremental runs, the recordedanalyzed_commit.
Outputs
docs/ai-context/PROJECT_CONTEXT.mdin the app repository, passingbin/frappe-workflow validate project-context.- Frontmatter with
analyzed_commitset to the commit that was analyzed.
Preconditions
- Detection succeeded; the app root is a Git repository.
- For incremental runs: existing file parses (frontmatter present).
Stopping Conditions
- Validation passes and
analyzed_commitequals current HEAD → done. - The repository has no commits yet → record that, produce the structural
sections from the working tree, set
analyzed_commitafter the first commit exists. - Existing file invalid/obsolete beyond repair → report it and perform one full re-analysis (this is the only case that rereads everything).
Prohibited
- Copying implementation details that reading the referenced file provides.
- Binding the app to a Site here (Site choice is task-level state).
- Updating content when the update-decision question answers "no"
(bumping
analyzed_commitalone is allowed after confirming no content change is needed). - Inventing versions:
frappe_version/erpnext_versioncome from the bench (apps.txt,__init__.pyversions) or are recorded asUnknown.
Shared Rules
shared-workflow-rules.md, frappe-project-detection.md, file-lifecycle.md.
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.

