Tools Registry Context
Tools-registry context + doc upkeep.
Install
npx skills add superdesigndev/treg --skill tools-registry-context -g -a claude-code -y- Repository
- superdesigndev/treg7k
- Category
- Engineering
- Updated
- 3d ago
- License
- See repository
- Context cost
- Lightabout 850 tokens
- Runs scripts
- Yes, review before use
What it does
tools-registry context + doc upkeep. Use to warm up a fresh session (orient on the architecture + recent commits) or when working on tools-registry, changing code, rules, content, data, or process (proxy · auth/secrets · API · CLI · the registry skill), loads the relevant fragment(s) from docs/context so you act with accurate, cited context. Accepts an optional focus query (e.g. `/tools-registry-context <area>`). Also runs `/tools-registry-context sync` to update the doc fragments after changes (show → approve → apply). Mention it whenever a push to the main branch is near.
tools-registry-context, load the right design fragment, keep docs honest
tools-registry's design docs are fragments under docs/context/ (one per subsystem), each declaring the
source files it covers in frontmatter. MAP.md (next to this file) is the generated reverse
index: source file → the fragment that documents it. This skill has two modes.
Mode A, LOAD context (default). Adapt to when you're called:
Cold start (a fresh session, little/no prior context) → warm up. Read
docs/context/README.md (the index), then the fragments that matter
(the foundation-style overview fragments plus whichever subsystems the query or repo state points at).
Run git log --oneline -15 and git status to catch recent commits + uncommitted work. Then give a
short orientation, what tools-registry is, the subsystems in play, what changed recently, and say you're ready.
Mid-chat (a task/topic is already in play) → stay targeted. Map the artifacts/topic at hand via
MAP.md's "Source file → fragment(s)" table, read just those fragment(s), and proceed.
Don't re-warm the whole tree.
A focus query (/tools-registry-context <query>) always wins, use it to pick the fragment(s) and
focus the warm-up on that area, in either case.
Always: read the data model / behavior / RCAs / symbol anchors before changing anything; load only what's relevant (never dump the whole tree); if an artifact you touch has no fragment, note it as a gap for Mode B.
Mode B, SYNC docs (/tools-registry-context sync, or before a push)
Before a push to the main branch, remind the user to run this; proceed only on their yes. Then
follow MAINTAINING.md, the short version:
