simplify-context
Installation
SKILL.md
Simplify Context
Take the existing CONTEXT.md glossary and make its terms clearer at first glance — without changing behaviour. Distinct from domain-modeling (builds and sharpens the glossary as you design). This skill proposes a vetted rename and hands off; it does not edit by default.
All concrete term names below are illustrative — use the target repo's own domain vocabulary.
Workflow
- Read the glossary.
CONTEXT.md## Languagesection. Note its meta-rules (no schemas / file paths / impl detail) and any reserved words (a word one term forbids another from using, via its_Avoid_). - Flag the opaque terms. First-glance test: would a newcomer guess the meaning from the name alone? Mark jargon-as-noun and names that don't signal their family. Leave already-clear terms alone — clarity, not churn.
- Judge entrenchment (drives scope). Grep each term across the codebase and the docs (ADRs and similar). Many hits — especially symbol names and filenames — mean renaming is a real refactor, not a doc edit.
- Pick scope with the user — three tiers:
- Glosses only — keep names, add a plain-language one-liner per term. Edits one file. Zero code risk.
- Rename everywhere — new names across CONTEXT.md + code symbols + UI strings + docs. Confirm code-churn reach (symbols+strings vs also filenames).
- CONTEXT.md only — fast but introduces drift between the glossary and the code/docs. Discourage.
- Build the rename map. Default lens = family grouping: a shared prefix/suffix makes related terms scannable (
Order Placed/Order Shipped;Billing Address/Shipping Address). Plain-language de-jargon (Payment RetryoverDunning) is the fallback when no natural family exists. Apply the checks below. Present as an old → new → family table. - Confirm names. Contested names →
AskUserQuestion, recommended option first, 2–4 candidates each. Lock the full map before any handoff. - Map the seams (grounds the handoff — see below).
- Hand off.
/to-prd(a wide rename is usually PRD-sized),/to-issues, or direct edits. Whatever applies the rename, finish by confirmingCONTEXT.mdand the docs/ADRs still agree.