菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
"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 when the user asks to render a video from a blog post (any of)."
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 team).
"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 hand-writes the blog markdown). WHEN: when producing the blog post for a framework, when the nightly blog organ fires, or when the user mentions the blog organ, the fixpoint post, skill2framework, or making a framework blog (any of)."
"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 mechanics ONLY from what the impl docs say IS (not vision, not invented). WHEN: when producing the deep-dive half of a framework chapter, when you need the technical how-it-works post that Blog 1 links to, or when the user mentions blog 2 / the deep dive / skill2framework (any of)."
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: when a blog/journey needs its JourneyBlog AIDA write-up and platform posts (the unicorn socials organ fires this), or the user says 'write the blog' / 'use the blog writer' / 'fill the JourneyCore' (any of).
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 been generated (the unicorn_socials_pack automation fires this), or the user says 'make the socials posts for this blog' / 'socials pack' (any of).
| name | backfill-vision-from-journal |
| description | 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. |
You are catching the durable vision layer up to the thinklog. A doc-mirror journal month-file
has accumulated DECISION/FINDING/INTENT entries that were written BEFORE the journal→vision
projection existed (so they sit only in the journal, not in any vision(m)). Project the
substantive ones into the right vision(m) files so the geometry coheres.
<repo-root>/context/journal/2026-05.md).<repo-root>; export DOCMIRROR_MONOREPO).2026-05-31).journal -t <FLAVOR> --tags <tag1>,<tag2>,... "<concise one-line restatement>"
doc(m) exists at <repo>/docs/mirror/<tag>.md) → the entry is
appended as a tags:[...] line to the paired <repo>/docs/vision/<tag>.md.tags:[...] clause so vision <tag> resolves the
hyperedge.doc(m) does nothing (no projection) — that's fine.doc(m)): find the module path(s) — verify
<MONOREPO>/**/docs/mirror/<relpath>.md exists. Project with
journal -t <FLAVOR> --tags <relpath>,<concept...> "<restatement>".doc(m)): append it
to a cross-cutting vision file <repo>/docs/vision/_<topic>.md as a - <restatement> tags:[...]
line (create the file if absent; this is a legal vision kind). Pick the repo it most belongs to
(e.g. doc-mirror-system architecture → the doc-mirror-system repo).doc(m) yet (un-booted repo): do NOT force-project. Add it to a
needs-doc(m)-first list in your report.grep the target vision(m) for an entry already covering it; skip if present.vision <key-concept> for 3–5 of the concepts you used and
confirm they resolve to the expected files. Paste the output.vision(m) / _<topic>.md file.needs-doc(m)-first list (entries that couldn't project because their module isn't booted).vision <concept> verification output for the concepts you projected.vision CLI resolves the projected entries.vision strong_compression/observation-chain/EAA/dumb-versions/MSC + read samples: concise one-liners, user terms preserved, hyperedges stitch module↔cross-cutting correctly, cat_gate de-duped (2 not 3). No prompt fix needed.