菜单
Use when implementing/debugging Ctrl+O Expanded Transcript (second view) and thinking persistence in the REPL.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | formax-expanded-transcript-workflow |
| description | Use when implementing/debugging Ctrl+O Expanded Transcript (second view) and thinking persistence in the REPL. |
Use this skill when changing Ctrl+O expanded transcript behavior, thinking persistence, or compact / expanded projection boundaries in the REPL.
docs/contracts/transcript-surface-contract.mddocs/contracts/semantics-contract.mddocs/runbooks/repl-surface-debugging.md when the change can affect clear / remount behaviorThese docs are canonical. If stable expanded-transcript behavior changes, update them before or with code.
If the change touches clear / remount ownership directly, also use formax-surface-reset-workflow.
packages/core/src/screens/repl/hotkeys.tspackages/core/src/screens/REPL.tsxpackages/core/src/screens/repl/compactProjection.tspackages/core/src/screens/repl/transcript.tsxpackages/core/src/features/repl/controller/streaming/streaming.tspackages/core/src/screens/repl/panels.tsxpackages/core/src/features/repl/controller/send/send.tspackages/core/src/screens/repl/useSurfaceTransitionManager.tsthinking_delta is the only source of truthStatic hacks for toggles:
Static is append-only; if content must disappear, use reset / remount ownership instead of trying to "unrender" itbanner -> summary (expanded only) -> > /compact ... -> compact sublineui.kind remain independent from prompt-history packing and reminder injectionthinking_delta persistence and transcript projection rules before renderer polish.Static workarounds.bun run test -- packages/core/src/screens/repl/compactProjection.test.ts packages/core/src/screens/repl/expandedTranscript.test.tsx packages/core/src/screens/repl/hotkeys.test.tsxbun run test -- packages/core/src/screens/repl/surfaceSmoke.test.tsxbun run test:surface-screen-modelbun run type-checkthinking_delta.Ctrl+O steal input while prompt mode or overlays are active.Static to “fix” duplication; solve ownership and remount boundaries instead.Use when the user wants a reusable rolling execution pattern (README + TODO-INDEX) like plans/web-reference-react-refactor, and wants to run delivery in small validated loops.
Use when changing web CSS/UI styling so requirements, state ownership, and acceptance checks are locked before edits to prevent rework churn.
Use after task analysis when a non-trivial Formax repository task needs a structured `docs/todolist.md` with [x]/[ ] items, definitions-before-UI ordering, explicit non-goals, tests, and loop-ready execution slices.
Use when a Formax repository task is non-trivial and you should analyze goals, non-goals, boundaries, data/type/interface impact, contract impact, test strategy, and whether an xhigh subagent is actually needed before writing a todo or code.
Use after receiving WebGPT or another LLM review on a Formax todo and before sending the todo back for another pass. Produce a concise handoff response that says what we adopted, what we reject or question, and what the reviewer should specifically re-evaluate in `docs/todolist.md`.
Use for all frontend and web UI tasks by default to apply a business-agnostic desktop web visual style system with medium-strength guardrails; if an existing design system is present, follow it first and use this skill only as a style harmonizer.