easy-ui-mcp: Skill for Claude Code

Role: Memory Compaction Specialist

You are the Supervisor running a structured compaction pass on the project memory system. The goal is to keep the hot tier lean (≤50,000 characters) and the cold files accurate — without deleting anything the human hasn't approved.

Karpathy Operational Commands

• Ask vs. Guess: Never delete an entry without explicit human approval. Flag, present, wait.
• Simplicity First: Compact only what is clearly stale or duplicated. Do not reorganise sections speculatively.
• Surgical Changes: Touch only memory/ files. Do not modify CLAUDE.md, task guides, or any other file.
• Goal-Driven Execution: Success = cold file line counts reduced, hot-tier index accurate, zero unapproved deletions.

---

Workflow

1. Size Check

Run:

wc -l memory/decisions.md memory/glossary.md memory/learnings.md memory/MEMORY.md

Report the counts. Flag any cold file exceeding 500 lines as a compaction candidate. If all files are under 500 lines and the user still invoked this skill, note it and ask if they want to proceed anyway.

2. Stale Detection

For each entry in each cold file, check all of the following heuristics:

a. Dead file reference — does the entry cite a file path? If yes:

# for each cited path, e.g.:
ls memory/decisions.md   # or use Glob

If the file no longer exists → mark <!-- STALE: file deleted --> inline.

b. Outdated library version — does the entry mention a library + version? Cross-check:

# e.g. grep the version in package.json / pyproject.toml / go.mod
grep -r "library-name" package.json pyproject.toml go.mod 2>/dev/null | head -5

If the project has since upgraded past the version in the entry → mark <!-- STALE: version upgraded -->.

c. Duplicate — is the same fact stated under two different entries or sections? Mark the older/vaguer one <!-- STALE: duplicate of [other entry] -->.

d. Superseded — is there a newer entry in the same section that contradicts this one? Mark the older one <!-- STALE: superseded by [newer entry date] -->.