project-notes
Skill2 starsChanged 5 days agoMITView on GitHub
Loading and maintaining per-project notes for CG / motion-design productions across sessions — brief, storyboard beats, VO timings, scene and file map, pipeline conventions, verified state, deliverables, open tasks. Use at the START of any task on a named production (a client video, a shot, a campaign) to read its notes before touching scenes, and at the END to update them. Notes live in a separate, private notes folder as SLUG/NOTES.md; project data never goes into a skill.
- Commits and pushes
3 other projects use a version of this.
Adopted by
Most recently taken up by
- mongdang/giroktheir own version, first seen Oct 1, 2026
- git-aditya-star/project-notestheir own version, first seen Sep 17, 2026
- jukrap/ai-agent-playbooktheir own version, first seen Jul 4, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- jukrap/ai-agent-playbook★ 2same name
- mongdang/girok★ 2same name
- git-aditya-star/project-notes★ 1same 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 repository26 other files it gives its agents.
- aftereffects-bridgeSkill
- aftereffects-scriptingSkill
- cinema4d-alembicSkill
- cinema4d-mcpSkill
- cinema4d-motion-trackerSkill
- cinema4d-particlesSkill
- cinema4d-redshiftSkill
- cinema4d-render-previewSkill
- cinema4d-riggingSkill
- cinema4d-takesSkill
- houdini-flipbookSkill
- houdini-mcpSkill
- houdini-network-layoutSkill
- houdini-pop-particlesSkill
- houdini-pyro-smokeSkill
- houdini-to-cinema4dSkill
- houdini-vdb-surfacingSkill
- premiere-bridgeSkill
- unreal-content-managementSkill
- unreal-editor-toolsSkill
- unreal-led-volume-rigSkill
- unreal-materials-pythonSkill
- unreal-mcpSkill
- unreal-sequencer-pythonSkill
- unreal-ultra-dynamic-skySkill
- vo-timingSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 21
End of the session (or after a milestone): update NOTES.md; if the folder is a git repo, git add -A && git commit && git push.
- Distinctive: line 35
Never put project notes in a public repo.
- Very specific: line 36
Keep NOTES.md under ~300 lines.
≈ “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
Project notes
Skills hold reusable know-how. Anything specific to one production (names, paths, timings, decisions, current state) lives in that project's notes file instead.
Where
- A private notes folder kept OUTSIDE the skills (ideally its own private git repo), e.g.
~/Documents/claude-project-notes/. If the user hasn't set one up, ask where it should live and remember the answer. - One folder per production:
<notes-folder>/<slug>/NOTES.md(slug = short lowercase project name). - List existing projects with
ls <notes-folder>in any available shell tool; read withcat.
When
- Start of a task on a named production: list the notes folder, read the matching NOTES.md, then work. If none exists and the work will span sessions, create one from the template below.
- End of the session (or after a milestone): update NOTES.md; if the folder is a git repo,
git add -A && git commit && git push. No packaging needed — notes are not skills.
Template (sections, keep the ones that apply)
Brief · Beats / storyboard · VO or music timings (with frame numbers + fps) · Scene map (DCC files, node/object paths) · Pipeline & exports (file paths, frame ranges, scale and axis conventions) · Current state (verified numbers only) · Deliverables (where outputs went) · Decisions & per-project preferences · Open tasks.
Rules
- Verified facts only; mark anything else "(unverified)". Correct stale lines, don't append contradictions.
- General lessons (API traps, recipes) go to the relevant skill; project facts go here. When a project fact turns out to be a general rule, move it into a skill.
- Absolute paths are fine here. No credentials, contract terms or other sensitive client data.
- Never put project notes in a public repo.
- Keep NOTES.md under ~300 lines; split into
<slug>/<topic>.mdwhen it grows.
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.