Skip to content
cccskills
FreePublished on GitHub

formax-expanded-transcript-workflow

Use when implementing/debugging Ctrl+O Expanded Transcript (second view) and thinking persistence in the REPL.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md3.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

formax-expanded-transcript-workflow

Goal

Use this skill when changing Ctrl+O expanded transcript behavior, thinking persistence, or compact / expanded projection boundaries in the REPL.

Read First

  • docs/contracts/transcript-surface-contract.md
  • docs/contracts/semantics-contract.md
  • docs/runbooks/repl-surface-debugging.md when the change can affect clear / remount behavior

These 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.

Code Map

  • Key handling: packages/core/src/screens/repl/hotkeys.ts
  • View wiring + footer: packages/core/src/screens/REPL.tsx
  • Compact projection: packages/core/src/screens/repl/compactProjection.ts
  • Transcript rendering: packages/core/src/screens/repl/transcript.tsx
  • Thinking persistence: packages/core/src/features/repl/controller/streaming/streaming.ts
  • Expanded Transcript panels: packages/core/src/screens/repl/panels.tsx
  • Compact command lifecycle: packages/core/src/features/repl/controller/send/send.ts
  • Surface reset owner: packages/core/src/screens/repl/useSurfaceTransitionManager.ts

High-Signal Patterns

  • No fake thinking:
    • thinking_delta is the only source of truth
    • never synthesize thinking rows from timers or summaries
  • Avoid Static hacks for toggles:
    • Static is append-only; if content must disappear, use reset / remount ownership instead of trying to "unrender" it
  • One footer:
    • prefer a single global footer; avoid per-panel footer duplication
  • Compact ordering contract:
    • keep banner -> summary (expanded only) -> > /compact ... -> compact subline
  • UI vs LLM orthogonality:
    • transcript slicing and ui.kind remain independent from prompt-history packing and reminder injection

Minimal Workflow

  1. Lock the semantic source first: thinking_delta persistence and transcript projection rules before renderer polish.
  2. Keep default transcript low-noise and Expanded Transcript read-only.
  3. Preserve compact / expanded ordering before adjusting footer or panel layout.
  4. If clear / remount logic changes, route through the shared surface reset path instead of local Static workarounds.
  5. Run the regression set below before review.

Minimum Regression

  • 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.tsx
  • bun run test -- packages/core/src/screens/repl/surfaceSmoke.test.tsx
  • bun run test:surface-screen-model
  • bun run type-check

Guardrails

  • Do not introduce synthetic thinking or show thinking when the model did not emit thinking_delta.
  • Do not let Ctrl+O steal input while prompt mode or overlays are active.
  • Do not move header / messages outside Static to “fix” duplication; solve ownership and remount boundaries instead.
  • Expanded Transcript stays read-only; do not quietly turn it into an interactive input surface.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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.

The English summary is being prepared. Showing the original description.

yusifeng/formax194Updated Jul 25, 2026

Use when adding or changing any Approval prompt/presenter.

The English summary is being prepared. Showing the original description.

yusifeng/formax194Updated Jul 25, 2026

Use when implementing or extending /config (storage, prompt injection, request params, UI-only toggles) with tests and strict UI parity.

The English summary is being prepared. Showing the original description.

yusifeng/formax194Updated Jul 25, 2026

Use when working on Formax code changes and you need a disciplined dev loop: keep a single mainline task, avoid scope drift, run only targeted tests (no coverage), avoid partial staging (MM), run mandatory review before commit, include an incremental optimization check, and keep commits small and reviewable.

The English summary is being prepared. Showing the original description.

yusifeng/formax194Updated Jul 25, 2026

Use when implementing or debugging Formax permissions/policy/approval behavior and UI (allow/ask/deny rules, workspace boundaries, approval prompts, and /permissions overlay parity with Claude Code).

The English summary is being prepared. Showing the original description.

yusifeng/formax194Updated Jul 25, 2026

Use when preparing a Formax code handoff: selecting files, generating repomix bundles, and writing a high-quality prompt for WebGPT or another coding agent with clear constraints and validation scope.

The English summary is being prepared. Showing the original description.

yusifeng/formax194Updated Jul 25, 2026

See all skills by yusifeng

Report a problem with this skill