doc-mirror

Plugin doc-mirror from marketplace sancrev-marketplace in sancovp/sancrev-marketplace. Commands read from the repo's manifest — yesterday.

Skills (38)

• check-sophia-progress

  WHAT: check the live status of the Sophia rollup / cohere worker — is the daemon running, how far BEHIND it is (how many journals not yet cohered / the lag between newest journal and newest momentum), and how many issues meta-Sophia has flagged. WHEN: when you want to know if Sophia is running + cau

• distill-to-essential-transform

  WHAT: a thinking move -- collapse a complex system to its one-sentence ESSENTIAL TRANSFORM (input->output->artifact) and rebuild it at the LOWEST sufficient mechanism, borrowing reliability from a substrate you do not own. WHEN: a system feels too heavy/fragile to depend on; a built thing was forgot

• doc-mirror-boot

  WHAT: doc-mirror-boot — the MANDATORY first action of EVERY turn in this container. It primes the CORE LOOP, explains the doc-mirror STATE MACHINE (cursor + state-skills + transition hook), and routes you to the state your cursor names. You are ALWAYS inside this machine; no reading, querying, editi

• doc-mirror-change

  WHAT: change ONE module -- read its full boundary, make the change, re-derive its doc(m), doc-mirror-commit with an ORIGIN, run closure, graduate the realized vision(m) -> doc(m). WHEN: a specific module changed or has code/doc to write -- after seework picks a code gap, or after a prompt produced a

• doc-mirror-init

  WHAT: first-time mirror a codebase that has none (enumerate modules -> write doc(m)=IMPL + vision(m)=VISION -> the 6 context files -> closure test). WHEN: the active repo has NO docs/mirror/ and NO progress-tracker yet (a fresh repo to mirror); reached from seework or boot when the active repo is un

• doc-mirror-install

  WHAT: install/setup wizard -- puts doc-mirror's CLIs (journal, vision, cursor, commit, search) on PATH and records where the plugin lives. WHEN: right after installing/enabling the doc-mirror plugin (first-time setup); or a doc-mirror command is 'command not found'; or 'docmirror search' cannot find

• doc-mirror-memory-net

  WHAT: REHYDRATE by querying the CartON journal/vision graph (ready-to-run Cypher) instead of re-reading flat files -- where-am-i, what-was-decided-about-X, what-spans-repos, concept-neighborhood. WHEN: rehydrating at session start or post-compact (run right AFTER doc-mirror-boot); recalling what was

• doc-mirror-prompts

  WHAT: the reliability-scored prompt-skill library for getting an AGENT to DO a task. WHEN: you need to dispatch an agent to do a task; or you say 'find / add / score / goldenize a prompt-skill for X' -- from change (dispatch the worker), seework (a gap that is an agent task), or init (the doc-gen te

• compare-doc-corpora

  WHAT: compare two documentation corpora and produce a structured gap/overlap analysis — what ideas in A are present/partial/absent in B, what B has that A lacks, where they agree vs diverge. WHEN: when you need to compare a reference/older corpus against a current one (e.g. an old design corpus vs o

• gnomorphogenetic-hermeneutics

  WHAT: a hermeneutics (interpretive method) and a forge for NAMING an unlabeled recursive / self-referential / holographic pattern — stack cross-domain analogies, triangulate the invariant, coin a NEW word by mixing morphemes, and install it as a semantic-attractor BLOCK (an 'eigenword block') that d

• natural-language-code-egregore

  WHAT: the prompt-engineering STYLE for writing a prompt that INSTANTIATES an agent instead of instructing it — a 'natural language code egregore': code-shaped natural language that, by being read, RUNS, so the model becomes the thing the prompt describes. Covers the concrete tricks (initiation stagi

• onboarding-rewrite

  WHAT: rewrite a SYSTEM PROMPT / agent onboarding file (a CLAUDE.md / persona entry) that fails to onboard — it references named components and jargon before the reader knows them, never orients the reader to the situation, never says how to START operating the system, and is formatted as a wall of m

• build-a-course

  WHAT: builds a complete teach-while-showing-your-system COURSE — the kind that teaches a generic skill for free and sells your advanced system through the GAP, by walking primitives beginner->advanced, showing your system do each one 'right and forever', with the funnel woven in (lead magnets throug

• recohere-meaning-layer

  WHAT: a procedure that sends a coding subagent to fix the MEANING/NAMING layer of a module (the type names, label maps, description strings, and other strings that only carry meaning) to a corrected canonical — WITHOUT touching the MECHANICS (the algorithms that operate on structure: traversal, slot

• backfill-vision-from-journal

  Project an existing doc-mirror journal month-file's accumulated DECISION/FINDING entries into the vision(m) layer (catch the durable layer up to the thinklog). Use when the journal->vision projection was added after a session's thinking already piled up untagged in the journal.

• deconfabulate-and-fill-stub

  WHAT: a procedure that sends a carton-MCP-equipped subagent to REPAIR one CartON AUTO-CREATED stub (a :Wiki node that exists only because a term was MENTIONED but never EXPLAINED — thin/placeholder description, few or no real edges) by TIMELINE ARCHAEOLOGY: trace the action timeline (Iteration_Summa

• verify-rehydration-before-compact

  WHAT: the EMPIRICAL continuity test — before compacting (or AFK/handoff), dispatch a fresh subagent to REHYDRATE a target from the durable layer ALONE (journal + the files it points to, no other context) and report what it reconstructed; you compare that to what it ACTUALLY needs to know, and patch

• deep-code-investigation

  WHAT: a procedure that sends a subagent to answer ONE precise question about how an EXISTING codebase actually works, by reading the real code to its COMPLETE operational boundary — never concluding from a grep line, a filename, a signature, or a comment (all surface attractors), only from fully-rea

• map-system-architecture

  WHAT: a procedure that sends a subagent to produce the OVERALL ARCHITECTURE MAP of a whole codebase/system — every module's role, the real import/call dependency graph (who-uses-what), what is LIVE vs DEAD (by importer count), the core data/control flow, and how named subsystems of special interest

• prove-or-disprove-property-from-code

  WHAT: a self-contained prompt that sends a mathematician subagent to READ a construct in a codebase enough to understand WHAT IT IS and WHAT IT DOES, and then — by ABSTRACT IMPLICATION / INVARIANT DEDUCTION — prove whether the structure that construct's existence-and-operation ABSTRACTLY INSTANTIATE

• apply-referee-fixes-presentation-only

  WHAT: a procedure that sends a precise paper-organizer subagent to apply a referee's PRESENTATION fixes to a math/technical paper — to publication standard — while FREEZING the mathematics byte-for-byte: every Definition/Lemma/Theorem/Proposition/Corollary STATEMENT and PROOF body is unchanged (bloc

• judge-paper-publishability

  WHAT: a procedure that sends a COLD, fully-blind subagent (no knowledge of where the paper came from or what it is for) to referee a self-contained mathematical/technical paper and judge whether it is PUBLISHABLE — reading the WHOLE paper, verifying every definition is given before use and every the

• deep-research-accumulate

  WHAT: a research procedure that sends a subagent to deeply explain how an external software system, tool, or codebase is built — by web-searching architecture/internals blog posts AND shallow-cloning the repo to read the actual source — and accumulates the findings into per-subsystem markdown files

• blog-writing

  WHAT: THE blog writing skill — a dispatchable agent prompt that fills ONE JourneyCore + ONE JourneyBlog (the AIDA-within-AIDA blog format) from a source blog/journey, so the deterministic suite renderer derives the AIDA blog + the twitter/linkedin/discord posts from the single filled core. WHEN: whe

• narrative-blog-from-aios

  WHAT: the BLOG ORGAN — produces THE FIXPOINT POST for a framework (the ONE invariant blog format: OVERVIEW + JOURNEY + FRAMEWORK, explicit hero's-journey structure) by reconstructing the journey from the journal/durable layer, FILLING the JourneyCore model, and rendering deterministically (it never

• assemble-chapter

  WHAT: assembles a framework CHAPTER from the two already-rendered blog posts — combines Blog 1 (narrative) and Blog 2 (deep dive) into a chapter directory, wires the cross-links (Blog1<->Blog2, and both -> the plugin on the monorepo + the framework's skills) and litters in CTAs, producing the chapte

• deepdive-blog-from-impl-docs

  WHAT: produces Blog 2 of a framework CHAPTER — the mechanical DEEP-DIVE technical article ('how it actually works') — for an already-built AIOS by reading its impl docs (doc(m) + SYSTEM.md + STATE_GRAPH) and assembling a faithful how-it-works explanation that links back to Blog 1. It explains mechan

• generate-framework-skill

  WHAT: generates the FRAMEWORK SKILL for an already-built AIOS — a single skill that indexes the AIOS's skill-tree + rules + how they relate (as a diagram), gives a DECISION TREE telling the agent what to do, and ROUTES the agent into the AIOS dir for those skills/rules. It is the front-door index +

• package-framework-plugin

  WHAT: packages a framework into a Claude Code PLUGIN — assembles a plugin dir (plugin.json manifest + skills/<framework-skill>/SKILL.md + the chapter bundled as resources) from a generated framework skill + its chapter, and repaths the framework skill's chapter links to the bundled location. A frame

• socials-images-from-pack

  WHAT: a dispatchable agent prompt that renders the actual PNG images for a blog's socials pack — hero, social-share, and thumbnail — as rich Excalidraw diagrams rendered via the render.py Playwright pipeline, visually verified. WHEN: when a socials pack exists (pack.md with IMAGE PROMPTS) but its im

• socials-pack-from-blog

  WHAT: a dispatchable agent prompt that turns ONE published blog post into a ready-to-post socials pack — a Twitter/X thread, a LinkedIn post, a Discord post, and image prompts — following the 6-link mimetic desire chain quality bar. WHEN: when a blog is live on the site and its socials pack has not

• fold-into-tome

  WHAT: folds a framework into the author's SkillTome (legacy name: nomicon) — the top-level holder + search of all of {user}'s frameworks (its {aios}-volumes). Creates the {user}-tome holder skill if it does not exist, then registers/updates the framework's entry (one-line + links to its framework sk

• video-from-blog

  WHAT: the VIDEO ORGAN prompt — produces an explainer VIDEO from a published blog post using the proven video pipeline (script -> TTS audio + timing -> excalidraw diagrams -> remotion composition -> render -> ffmpeg assembly). WHEN: when the nightly video organ fires on an images_rendered blog, or wh

• doc-mirror-seework

  WHAT: the backlog dispatcher -- read the vision-minus-impl gap, take the next tracker pointer, route to the state that does it. WHEN: deciding what to do next / 'what needs doing?' -- after init, after a change lands, after a prompt task finishes, or right after boot when the cursor names no pending

• doc-mirror

  WHAT: THE LAW of doc-mirror -- the 4 legal doc-layer file kinds, deterministic addressing, the doc(m) template, the closure test, fork-on-change. The invariant every state operates under. WHEN: you need the rule for what a doc(m)/vision(m)/journal/tracker IS or where it lives; classifying a doc-laye

• make-ai-operating-system

  WHAT: the architect/compiler for AI operating systems (AIOS, a 'claude system') -- reads the option space, picks the shape, interviews you, emits the directory + operating program. WHEN: 'make me a system / harness / agent-environment for X'; designing a new way of running Claude; building any new c

• ship-a-plugin

  WHAT: the dev-flow for building AND distributing a Claude Code plugin + marketplace (ONE catalog that REFERENCES plugins, not a monorepo of their code); the full build -> commit -> install -> dogfood flow + the gotchas. WHEN: creating, packaging, publishing, installing, or distributing a plugin or m

• understand-metastack

  WHAT: metastack (pydantic-stack-core) -- generate structured text (blog/README/doc/prompt/report) by composing small TYPED renderable pieces into a self-rendering tree, NOT hand-rolled f-strings that garble/duplicate. WHEN: building or FIXING any structured-text renderer; output is garbled/duplicate

Hooks (5)

• PreToolUse

  python3 ${CLAUDE_PLUGIN_ROOT}/hooks/docmirror_readonly_guard.py

• PreToolUse

  python3 ${CLAUDE_PLUGIN_ROOT}/hooks/docmirror_transition_guard.py

• Stop

  python3 ${CLAUDE_PLUGIN_ROOT}/hooks/docmirror_brainhook.py

• SessionStart

  python3 ${CLAUDE_PLUGIN_ROOT}/hooks/docmirror_session_start.py

• SessionStart

  python3 ${CLAUDE_PLUGIN_ROOT}/hooks/docmirror_session_start.py

Similar plugins