skills.rest
yusifeng
yusifengCOMMUNITY
Explore all skills by this author →
GitHub

formax-expanded-transcript-workflow

Enforce contracts for thinking_delta persistence and panel wiring in the REPL.

192|7|Updated Dec 30, 2025
Search Tags:#debugging#repl#code-review#expanded-transcript#thinking-persistence#surface-management
One-click install
npx skills add https://github.com/yusifeng/formax --skill formax-expanded-transcript-workflow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: formax-expanded-transcript-workflow
Source: https://github.com/yusifeng/formax/tree/main/.codex/skills/formax-expanded-transcript-workflow
Command: npx skills add https://github.com/yusifeng/formax --skill formax-expanded-transcript-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides guidance and structure for implementing and debugging Ctrl+O Expanded Transcript (second view) and thinking persistence within the REPL, helping teams reason about transcript boundaries, state management, and remount ownership.

Core Features & Use Cases

  • Define and enforce contracts for thinking_delta persistence, surface transitions, and panel wiring in the REPL.
  • Reference canonical docs and runbooks to keep changes aligned with architecture and testing expectations.
  • Provide debugging guidance and a clear workflow to validate deterministic transcript rendering across revisions.

Quick Start

Review the canonical contracts and source code, then apply the expanded-transcript workflow to stabilize Ctrl+O behavior in your REPL.

Frequently Asked Questions about formax-expanded-transcript-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug Ctrl+O expanded transcript behavior in the REPL?▼

Debug Ctrl+O expanded transcript behavior in the REPL by applying canonical contracts for thinking_delta sources, surface ownership, and panel wiring to ensure deterministic rendering across revisions.

What is thinking persistence in REPL transcript workflows?▼

Thinking persistence in REPL transcript workflows defines and enforces contracts for thinking_delta sources to ensure state management and remount ownership remain deterministic and testable across code revisions.

How do I enforce contracts for thinking_delta sources and surface transitions?▼

Enforce contracts for thinking_delta sources and surface transitions by referencing canonical docs and runbooks, keeping changes aligned with architecture expectations for deterministic transcript rendering.

Why does my REPL expanded transcript view fail to render deterministically across revisions?▼

Expanded transcript views fail to render deterministically when surface ownership boundaries and panel wiring contracts are violated, requiring structured debugging workflows to stabilize remount behavior.

Can I use expanded transcript workflows for code review sessions?▼

Expanded transcript workflows apply to code review sessions where thinking persistence and transcript boundaries must be reasoned about, ensuring deterministic updates survive across code revisions.

What's the best way to stabilize Ctrl+O behavior in a REPL?▼

Stabilize Ctrl+O behavior in a REPL by reviewing canonical contracts and source code, then applying the expanded-transcript workflow to enforce deterministic panel wiring and thinking_delta persistence.

Related Skills

Explore More Software Engineering Skills→
ResearAIResearAI
3.3k

baseline

Standardize a reference object for quest evaluation with plan and checklist requirements.

Community
Advanced
ProteoWizardProteoWizard
17

debugging

Enforce a verifier-driven workflow to isolate software faults before fixes.

Official
Advanced
adriandarianadriandarian

ui-operations

Scaffold and integrate reusable UI panels and Web Components for 3Lens.

Community
Intermediate
hthor213hthor213

refresh

Capture mid-session AI development state and detect spec drift.

Community
Intermediate