comp
Skill67 starsChanged 4 months agoMITView on GitHub
Create or update all 4 COMP files (CLAUDE.md, ORIENT.md, MEMORY.md, PLAN.md) for a directory
1 other project uses a version of this.
Adopted by
Most recently taken up by
- tsukumogami/shirabetheir own version, first seen Oct 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- tsukumogami/shirabe★ 0same name
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 repository24 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- autoresearchSkill
- brainstormSkill
- bug-huntSkill
- check-resolvableSkill
- debugSkill
- dialectic-reviewSkill
- distillSkill
- finalizeSkill
- implementSkill
- learnSkill
- plan-taskSkill
- premortemSkill
- red-teamSkill
- researchSkill
- retroSkill
- reviewSkill
- rsbSkill
- sessionsSkill
- shipSkill
- socratesSkill
- tradeoffSkill
- verifySkill
- wrapupSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
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 11
Create or update all 4 COMP files for a project directory.
- Distinctive: line 17
If no arguments, use the current working directory.
- Distinctive: line 31
Read all 4 COMP files if they exist.
- Distinctive: line 53
Always READ existing files before editing — never overwrite blindly
- Distinctive: line 54
Keep each file focused on its purpose — don't duplicate across files
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
COMP Update
Create or update all 4 COMP files for a project directory.
Input
Directory to update: $ARGUMENTS
If no arguments, use the current working directory. If ambiguous, ask.
The 4 Files
| File | Purpose | Audience | Change Frequency |
| CLAUDE.md | Behavioral contract — how the AI should work here | Agent | Rare — only when conventions or architecture change |
| ORIENT.md | Orientation — what this project is, how to work in it | Human | When project shape changes |
| MEMORY.md | Accumulated knowledge — decisions, gotchas, cross-session context | Agent + Human | Most sessions |
| PLAN.md | Direction — roadmap, phases, progress, next steps (with ## Current State at top) | Human + Agent | Most sessions |
Process
Step 1: Read Existing Files
Read all 4 COMP files if they exist. Also read the directory listing (ls).
Step 2: Determine What Needs Updating
Based on the current session's work and the current state of the directory:
- Which files exist vs need creation?
- Which existing files are stale or incomplete?
- What new information needs recording?
Step 3: Create or Update Each File
PLAN.md — If creating: project roadmap, current phase, next steps, and a ## Current State section at the top with active work, blockers, and what to do next session. If updating: mark progress, adjust priorities, refresh the Current State section.
MEMORY.md — If creating: key decisions, known gotchas, cross-session context. If updating: add new decisions/gotchas. MEMORY is for durable knowledge that accumulates — don't put ephemeral session state here (that goes in PLAN.md's Current State section).
ORIENT.md — If creating: one-paragraph project description, current codebase shape (mental model, not file index), most common operations, known weirdness, key links. If updating: refresh to reflect new capabilities or structural changes. Written for the human — answer "what do I need to know to work on this after two weeks away?"
CLAUDE.md — If creating: project overview, key technical details, conventions, situational guides. If updating: add new conventions, update schema. Rare — don't add session-specific detail here.
Step 4: Summary
Report what was created/updated.
Rules
- Always READ existing files before editing — never overwrite blindly
- Keep each file focused on its purpose — don't duplicate across files
- CLAUDE.md is the behavioral contract (for the agent); ORIENT.md is orientation (for the human)
- MEMORY.md is durable cross-session knowledge; PLAN.md's Current State section is the session-scoped snapshot
- For sub-projects, reference the parent project's COMP files where relevant
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.