recall-contract-context
Skill0 starsChanged 8 months agoMITView on GitHub
Use when planning or implementing API-facing work and the agent needs validated prior contract knowledge before writing code
In this repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- backend-contract-exit-gateSkill
- brainstormingSkill
- compound-knowledge-summarySkill
- dispatching-parallel-agentsSkill
- executing-plansSkill
- finishing-a-development-branchSkill
- frontend-contract-entry-gateSkill
- receiving-code-reviewSkill
- requesting-code-reviewSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- using-git-worktreesSkill
- using-superpowersSkill
- verification-before-completionSkill
- writing-plansSkill
- writing-skillsSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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
- Distinctive: line 14
Use this skill when:
- Very specific: line 29
Search knowledge/patterns, knowledge/examples, and knowledge/incidents.
- Very specific: line 31
Write a short recall note using templates/recall-note.md.
- Distinctive: line 46
Prefer validated repository knowledge over prompt improvisation.
≈ “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
Recall Contract Context
Overview
Recall before implementation. Do not rediscover DTO, envelope, naming, or OpenAPI rules from scratch if the repository already contains validated knowledge.
When to Use
Use this skill when:
- a task changes an API contract
- a task adds or edits DTOs
- a task affects OpenAPI output
- frontend and backend coordination depends on one contract
Required Inputs
- affected endpoints or contract surface
- expected OpenAPI source location
- any existing related incident or example docs
Process
- Search
knowledge/patterns,knowledge/examples, andknowledge/incidents. - Extract stable constraints separately from task-specific guesses.
- Write a short recall note using
templates/recall-note.md. - Carry unresolved questions forward into planning or implementation.
Minimum Output
The recall note must state:
- relevant DTO semantics
- envelope expectations
- OpenAPI or decorator rules
- operation naming constraints
- known failure modes or gaps
Guardrails
- Prefer validated repository knowledge over prompt improvisation.
- Mark inferences as inferences.
- Missing knowledge is not silent; record the gap.
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.