Skip to content
cccskills
FreePublished on GitHub

formax-surface-reset-workflow

Use when changing REPL clear/reset/resume/surface behavior (onClearTerminal, transcriptSeq remount, Ink Static paths, Ctrl+O/Ctrl+E transitions). Enforces single-owner reset transaction and prevents black-screen/flicker/duplicate-row regressions.

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

See how to install

Files included (1)

  • SKILL.md3.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Formax Surface Reset Workflow

Goal

Use this skill when changing REPL clear/reset/resume behavior or any transcript surface transition that can remount Static.

Read First

  • docs/contracts/transcript-surface-contract.md
  • docs/runbooks/repl-surface-debugging.md
  • docs/contracts/invariants.md when ownership or sequencing is unclear

These docs are canonical. If stable surface behavior changes, update them before or with code.

Code Map

  • Reset helpers / queue owner:
    • replaceTranscript
    • queueTranscriptSurfaceReplace
    • resetTranscriptSurface
    • queueTranscriptSurfaceReset
    • surfaceOpQueueRef
  • High-risk flows:
    • packages/core/src/features/repl/controller/ui/
    • packages/core/src/features/repl/controller/session/
    • packages/core/src/features/repl/useReplController.ts
    • packages/core/src/screens/repl/
    • packages/core/src/runtime/bootstrap/runLegacyCli.tsx
  • Call sites to watch:
    • onClearTerminal
    • clearTerminal
    • resetInkStaticOutputForStdout
    • transcriptSeq remount behavior in ReplTranscript / ExpandedReplTranscript

Trigger Conditions

Use this skill whenever the change touches any of:

  • /resume, /clear, compact boundary transitions
  • Ctrl+O / Ctrl+E transcript view switches
  • onClearTerminal, clearTerminal, or resetInkStaticOutputForStdout
  • replaceTranscript, queueTranscriptSurfaceReplace, resetTranscriptSurface, queueTranscriptSurfaceReset, or surfaceOpQueueRef
  • files under packages/core/src/features/repl/controller/ui/, packages/core/src/features/repl/controller/session/, packages/core/src/features/repl/useReplController.ts, packages/core/src/screens/repl/, or packages/core/src/runtime/bootstrap/runLegacyCli.tsx

Minimal Workflow

  1. Identify the exact path (/resume, /clear, Ctrl+O / Ctrl+E, compact boundary, etc.).
  2. Route it through replaceTranscript / resetTranscriptSurface instead of local clear / remount sequencing.
  3. Treat reset as one transaction, not scattered side effects.
  4. Add or extend regression tests for ordering and surface reset ownership.
  5. Run the minimum regression set below and at least one real surface smoke path.

Minimum Regression

  • bun run test -- packages/core/src/features/repl/controller/ui/surfaceReset.test.ts
  • bun run test -- packages/core/src/features/repl/useReplController.test.tsx -t "resume|clear|compact"
  • bun run test -- packages/core/src/screens/repl/surfaceSmoke.test.tsx
  • bun run type-check
  • If change touches compact / expanded toggles broadly: bun run test:surface-screen-model

Guardrails

  • Keep one surface owner; do not add a second independent clear / remount path.
  • Do not stack replInstance.clear() and ANSI clear in legacy paths unless ownership is explicit and serialized.
  • Do not accept a Vitest-only fix without running a real surface smoke path.

References

  • docs/pitfalls/summary.md sections covering /clear, compact + Ctrl+O, and resume black-screen regressions
  • docs/pitfalls/repl-transcript-surface-handoff-pitfall.md
  • docs/pitfalls/repl-transcript-static-rootcause.md

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/debugging Ctrl+O Expanded Transcript (second view) and thinking persistence in the REPL.

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

See all skills by yusifeng

Report a problem with this skill