formax-tool-ui-blocks-workflow

Migrate Formax tools to a centralized blocks-based presenter with tests.

192|7|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/yusifeng/formax --skill formax-tool-ui-blocks-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: formax-tool-ui-blocks-workflow
Source: https://github.com/yusifeng/formax/tree/main/.codex/skills/formax-tool-ui-blocks-workflow
Command: npx skills add https://github.com/yusifeng/formax --skill formax-tool-ui-blocks-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes the tool transcript UI formatting and rendering into a single, reusable blocks-based renderer (ToolUiBlocks) to minimize churn when migrating tools to a blocks pattern.

Core Features & Use Cases

  • Centralized renderer: consolidates ⏺ spacing, ⎿/indent rules, and subline formatting.
  • Blocks-based presenters: enables per-tool customization without touching many files.
  • Migration workflow: provides a repeatable loop for migrating tools to blocks with controlled tests and Codex reviews.

Quick Start

Follow the documented workflow to migrate a target tool to the blocks presenter and verify through focused tests.

Frequently Asked Questions about formax-tool-ui-blocks-workflow

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

FAQPage Schema
How do I migrate tool UI components to a centralized blocks-based presenter?

To migrate tool UI to a blocks-based presenter, apply the provided migration workflow loop. It enforces a centralized renderer for spacing and indentation, followed by targeted tests and Codex reviews to ensure safe, incremental transitions.

What is the best way to standardize tool UI spacing and indentation rules?

Standardize tool UI spacing by migrating to a centralized blocks-based renderer. It consolidates spacing, indent rules, and subline formatting into one reusable component, reducing formatting inconsistencies across tools.

How do I safely manage code churn when migrating multiple tool UIs?

Manage code churn during tool UI migration by using a defined migration workflow with controlled tests and Codex review checkpoints. This ensures safe, incremental migrations without breaking existing tool-specific previews.

Can I customize tool-specific previews using a centralized blocks renderer?

Yes, blocks-based presenters enable per-tool customization without touching many files. The centralized renderer handles standard formatting, while presenters allow specific UI adjustments for individual tools.

When should I not use a centralized renderer for tool UI migration?

Avoid a centralized renderer if your tool UI relies on highly unique formatting logic that cannot conform to standardized spacing, indentation, and subline block rules without losing critical presentation context.