Help us improve
Share bugs, ideas, or general feedback.
From doc-mirror
WHAT: a thinking maneuver for taking a complex system you already built and unveiling its stupid-simple ESSENTIAL TRANSFORM — one sentence of pure input→output→(published artifact) — then re-realizing that transform at the LOWEST sufficient mechanism (usually just INSTRUCTIONS / a skill, sometimes a thin util), borrowing reliability from an execution substrate you do NOT own rather than your own stack. The implementation you built was incidental complexity wrapped around a simple, statable transform; name the transform and you can rebuild it minimally and reliably. WHEN: when a system feels too heavy / complex / unreliable to depend on; when a thing you built got FORGOTTEN but its FUNCTION keeps recurring as a live CONCEPT elsewhere; when you want to turn a built system into a reusable util or skill; when you're about to depend on a fragile in-house stack for something simple; or when the user says distill / collapse / simplify / 'what does this actually do' / 'make it just instructions' / 'make it a util/skill/plugin' (any of).
npx claudepluginhub sancovp/doc-mirror --plugin doc-mirrorHow this skill is triggered — by the user, by Claude, or both
Slash command
/doc-mirror:distill-to-essential-transformThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. **State the essential transform** in ONE sentence of pure I/O — strip ALL implementation:
Guides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.
Share bugs, ideas, or general feedback.
S takes {X} → returns {Y} → (produces/publishes {Z}).
Everything not in that sentence is incidental. (Worked example — mcp-squared: "takes an MCP → returns the workflow-skills for it → publishes them as a plugin.")instructions (a skill/prompt) ≤ a thin util/library ≤ an MCP ≤ a harness ≤ an OS.
Most "systems" collapse to instructions. (mcp-squared → just a skill: "take an MCP, return its workflow-skills, publish a plugin." No library even required.)This is the inverse-descent companion to the complexity-ladder (complexity-thinking-the-mechanism-ladder). The ladder says: climb only to the lowest rung that CAUSES a behavior. This maneuver catches the OPPOSITE failure — you (or a past lifetime) over-built: a simple transform got wrapped in an MCP / OS / multi-codebase implementation. Distilling re-states the transform and descends to the rung that actually delivers it.
autorealization-and-progressive-disclosure: core vs confabulated shell).Run it on EVERY system in the inventory: state its transform → decouple substrate → descend to instructions + borrowed-reliability → re-realize as a util/skill. Each pass turns a heavy "thing" into a clean, reusable, composable component (a stated transform + a thin realization). This is how the whole ecosystem unifies — every compiler/util becomes a one-line transform plus a minimal realization, composable as Links.
Composes with: complexity-thinking-the-mechanism-ladder (the climb; this is the descent), every-build-ends-in-a-development-flow-skill, the framework definition (essence = a-skill-a-human-can-do), autorealization-and-progressive-disclosure (core vs shell).
The per-system maneuver above is the tactic. The general pattern is an ENVIRONMENT shift:
Generalization vs the tactic: distill descends the ladder for ONE over-built system; the general pattern recognizes the substrate-shift (the platform now provides what you were forced to self-build), so the WHOLE inventory collapses at once AND every discarded substrate becomes biography. PAYOFF: the fossils ARE content — the Blog-1 narrative spine of the framework chapters (the publishing arc) and the funnel/positioning material. Distilling the inventory simultaneously unifies the live system and generates the biographical proof.