attograd-memory
Skill4 starsChanged 3 months agoMITView on GitHub
Recall and record durable project decisions with AttogradDB. Use when starting work in a repository, planning or editing code, or deciding whether a project constraint should persist.
In this repository2 other files it gives its agents.
- docs/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 5 are distinctive, and 3 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use the attograd-memory MCP tools for decisions that should survive the current task.
- Distinctive: line 12
Before planning or editing:
- Distinctive: line 15
Treat every returned active decision as a project constraint.
- Distinctive: line 16
Do not contradict an active decision without an explicit replacement.
- Very specific: line 20
Call remember_decision when the user or team makes a durable choice about architecture, dependencies, APIs, workflow, security, or scope.
- Very specific: line 28
When a new decision replaces an active one, pass the old decision's id as supersedes.
- Distinctive: line 29
Do not create a contradictory active decision.
- Distinctive: line 31
Do not store transient task details, guesses, or secrets.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
AttogradDB project memory
Use the attograd-memory MCP tools for decisions that should survive the current task.
Start of a task
Before planning or editing:
- Call
recall_decisions. - Treat every returned active decision as a project constraint.
- Do not contradict an active decision without an explicit replacement.
Record durable decisions
Call remember_decision when the user or team makes a durable choice about architecture,
dependencies, APIs, workflow, security, or scope. Include:
claim: the decision in one clear sentence.rationale: why it was chosen.scope: the affected area when useful.evidence: a file, benchmark, issue, or other supporting reference when available.
When a new decision replaces an active one, pass the old decision's id as supersedes.
Do not create a contradictory active decision.
Do not store transient task details, guesses, or secrets.
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.

