legacy-contracts
Skill2 starsChanged 4 months agoMITView on GitHub
Use when maintaining a legacy system whose browser, template, database, device, or deployment contracts must be preserved.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- design-brief-directionSkill
- ui-polishSkill
- natural-writing-humanizationSkill
- project-memorySkill
- project-notesSkill
- spec-artifactsSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Read references/contract-map.md to select the relevant stack reference.
≈ “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
Legacy Contracts
Identify the deployed runtime and contract that the requested change touches. Keep version, encoding, selector, form, session, database, device and bridge assumptions explicit. Existing compatibility requirements do not require a general modernization workflow.
Read references/contract-map.md to select the relevant stack reference. Read only that reference; do not load every legacy profile. Distinguish static/fixture checks from verification in the required browser, engine, database or device. Missing runtime evidence limits the claim, not all independent implementation work.
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.