mapping-invariants
Intro skill for designing and implementing assertions. Use when starting a new protocol to map invariants before writing assertions or tests.
npx skills add majiayu000/claude-skill-registry --skill mapping-invariants --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Mapping Invariants Start here before designing or implementing assertions. This skill defines the invariant‑mapping workflow and hands off to the other skills. ## When to Use - Starting a new protocol assertion effort. - You need a structured method to discover invariants. - You want the step‑by‑step path before `designing-assertions` and `implementing-assertions`. ## When NOT to Use - You already have a vetted invariant list. - You only need implementation details. Use `implementing-assertions`. - You only need testing guidance. Use `testing-assertions`. ## Quick Start 1. Build the protocol map (assets, roles, entrypoints, state, routers). 2. Enumerate invariants by category (access control, accounting, pricing, solvency, limits, modes). 3. Rank invariants by impact and likelihood (losses, control‑plane, liveness). 4. Identify exceptions and acceptable violations. 5. Pick data sources (state, logs, call inputs, slots). 6. Choose enforcement location (chokepoint vs per‑contract). 7. Produce the invariant matrix and trigger map. 8. Hand off to `designing-assertions` → `implementing-assertions` → `testing-assertions`. ## Workflow - **Protocol map**: read docs/specs/audits/tests; li
- When to Use
- When NOT to Use
- Quick Start
- Workflow
- Heuristics
- Deliverables
- Rationalizations to Reject
- References
What does the mapping-invariants skill do?
Intro skill for designing and implementing assertions. Use when starting a new protocol to map invariants before writing assertions or tests.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill mapping-invariants --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.