Agent skill

Formax Semantics Parity Workflow

by yusifeng in yusifeng/formax

A skill your agent uses when implementing or modifying behavior that must stay consistent across TUI and Web (mode/input/tool/replay/order).

MITAuto-check passed

Install Formax Semantics Parity Workflow

skills CLI
$ npx skills add yusifeng/formax --skill formax-semantics-parity-workflow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install yusifeng/formax formax-semantics-parity-workflow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/yusifeng/formax.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/formax-semantics-parity-workflow .claude/skills/formax-semantics-parity-workflow && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
formax-semantics-parity-workflow
GitHub stars
195
Token cost
~1.1k tokens
SKILL.md length
400 words
Files
2 (incl. references)
Skills in repo
21
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when implementing or modifying behavior that must stay consistent across TUI and Web (mode/input/tool/replay/order).

  • Works in 5 steps: Semantic single source of truth → App-server contract emit / restore → TUI adapter (renderer can differ,… → …
  • Modifying behavior that must stay consistent across TUI and Web (mode/input/tool/replay/order)
  • SKILL.md covers Goal, Read First, Code Map and High-Signal Patterns, plus 3 more sections
  • Calls bun and npm

What it does

Formax Semantics Parity Workflow is an agent skill from yusifeng/formax. Use when implementing or modifying behavior that must stay consistent across TUI and Web (mode/input/tool/replay/order). Require canonical semantics first, then TUI/Web adapters, then renderer-specific UI.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/fixtures-checklist.md`).

It works with React. The repository describes itself as: Terminal-first AI assistant for software engineering tasks (inspired by Claude Code v2.0.67). The licence is MIT.

When your agent uses it

  • Modifying behavior that must stay consistent across TUI and Web (mode/input/tool/replay/order)

Example prompts

  • “/formax-semantics-parity-workflow”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Semantic single source of truth
  2. App-server contract emit / restore
  3. TUI adapter (renderer can differ, semantics cannot)
  4. Web adapter (renderer can differ, semantics cannot)
  5. Canonical docs to keep in sync

What it can do on your machine

Read from SKILL.md and the folder at commit 1b0c3f3. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • bun
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Formax Semantics Parity Workflow loads about 1.1k tokens when it runs, and up to ~2.1k if it reads all its reference files. Until then it costs about 60 tokens; SKILL.md has 400 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~60
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from yusifeng/formax at commit 1b0c3f3, republished under its MIT licence (© yusifeng). 400 words, ~1,133 tokens.

Download SKILL.mdSave it as .claude/skills/formax-semantics-parity-workflow/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
formax-semantics-parity-workflow
description
Use when implementing or modifying behavior that must stay consistent across TUI and Web (mode/input/tool/replay/order). Require canonical semantics first, then TUI/Web adapters, then renderer-specific UI.

formax-semantics-parity-workflow

Goal

Use this skill when changing behavior that must stay consistent across TUI, app-server, and Web: mode, input lifecycle, tool sequencing, replay, or ordering.

Read First

  • docs/contracts/semantics-contract.md
  • docs/contracts/app-server-interaction-contract.md
  • docs/frontend/app-server-ui-spec.md
  • docs/contracts/interactive-input-contract.md when input lifecycle changes

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

Code Map

1) Semantic single source of truth
  • packages/core/src/features/semantics/*
    • canonicalEvents.ts
    • transcriptProjection.ts
    • modeSemantics.ts
    • replModeTransition.ts
    • turnInputBuilder.ts
    • inputStateMachine.ts
2) App-server contract emit / restore
  • packages/core/src/app-server/turnRunner.ts
  • packages/core/src/app-server/server.ts
  • packages/core/src/app-server/threadStore.ts
  • packages/core/src/app-server/store/sessionEventReader.ts
  • packages/core/src/app-server/turn/inputStore.ts
3) TUI adapter (renderer can differ, semantics cannot)
  • packages/core/src/features/repl/controller/send/send.ts
  • packages/core/src/features/repl/controller/streaming/streaming.ts
  • packages/core/src/features/repl/useReplController.ts
4) Web adapter (renderer can differ, semantics cannot)
  • packages/web-reference-react/src/eventAdapters.ts
  • packages/web-reference-react/src/App.tsx
  • packages/web-reference-react/src/store.ts
  • packages/web-reference-react/src/turnEventCursor.ts
5) Canonical docs to keep in sync
  • docs/contracts/semantics-contract.md
  • docs/contracts/app-server-interaction-contract.md
  • docs/frontend/app-server-ui-spec.md
  • docs/contracts/interactive-input-contract.md when input lifecycle changes

High-Signal Patterns

  • Semantic-first implementation order:
    1. define contract / event shape / state transition
    2. update shared semantics
    3. update app-server emit / replay state
    4. update TUI and Web adapters
    5. update renderer-only UI last
  • Ordering discipline:
    • replaySeq is the primary ordering key
    • traceId/seq are diagnostics and turn-local hints, not global order
    • on replay gap, rebuild from semantic baseline; do not keep stitching stale tails
  • Tool semantics discipline:
    • keep toolUseId -> toolName sticky behavior in semantics / adapter path
    • never depend on UI copy to infer tool state
  • Mode/input discipline:
    • mode is a semantic transition, not just a visual toggle
    • input lifecycle remains a finite-state machine, not ad-hoc UI flags
Show full SKILL.md (181 more words)Show less

Minimal Workflow

  1. Define the event / state transition in canonical docs and the shared semantics layer first.
  2. Update app-server emit / replay state so the semantics remain recoverable.
  3. Update TUI and Web adapters to consume the shared semantics; update renderer-only UI last.
  4. If packages/core/src/features/repl/** semantic-flow files move, run the REPL semantic gate before review.
  5. Run the minimum regression set below, then review via AGENTS.md.

Minimum Regression

  • bun run type-check
  • bun run test -- packages/core/src/features/semantics
  • bun run test -- packages/core/src/features/semantics/__tests__/projectionParity.test.ts
  • bun run test -- packages/core/src/app-server/turnRunner.test.ts packages/core/src/app-server/server.test.ts packages/core/src/app-server/turn/inputStore.test.ts
  • npm --prefix packages/web-reference-react run type-check
  • npm --prefix packages/web-reference-react run test -- src/App.test.tsx src/store.test.ts src/turnEventCursor.test.ts src/toolEventNormalizer.test.ts
  • bun run test:repl-semantic-gate when packages/core/src/features/repl/** semantic-flow files change

For fixture selection and parity assertions, use references/fixtures-checklist.md.

Guardrails

  • Do not patch one renderer in isolation when the bug belongs to shared semantics.
  • Do not add a second semantic state machine inside TUI or Web.
  • Do not use UI text or copy as semantic-state input.
  • Do not introduce new ordering rules outside the shared semantics layer.
  • Do not call a parity change done until app-server, TUI, and Web consume the same semantic rule.

© yusifeng, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in .codex/skills/formax-semantics-parity-workflow of yusifeng/formax.

  • SKILL.md
  • references/fixtures-checklist.md

Open the folder on GitHubat commit 1b0c3f3

Compare with similar skills

Formax Semantics Parity Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Formax Semantics Parity Workflow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Formax Semantics Parity Workflow this skillyusifeng/formax195—~1.1kAutomated safety check: PassMIT
Web Artifacts Builderanthropics/skills180k41 repos~769Automated safety check: PassApache-2.0
Vercel Composition Patternssupabase/supabase111k58 repos~726Automated safety check: PassMIT
React Doctormakeplane/plane61k12 repos~657Automated safety check: PassAGPL-3.0
React Router Developmentremix-run/react-router57k1 repos~1.5kAutomated safety check: PassMIT
React UI State PatternsChrisWiles/claude-code-showcase6.1k8 repos~1.6kAutomated safety check: PassNone

Similar skills

  • Web Artifacts Builder

    anthropics/skills

    Official

    Builds multi-component claude.ai HTML artifacts as a small React, TypeScript and Tailwind project, then bundles it into one shareable HTML file.

    180k GitHub starsUsed in 41 repos~769 tokens
    Frontend & DesignAuto-check passed
  • Official

    React composition patterns that scale. An agent skill from supabase/supabase.

    111k GitHub starsUsed in 58 repos~726 tokens
    DevelopmentAuto-check passed
  • React Doctor

    makeplane/plane

    Scans React code for lint, accessibility, bundle size and architecture issues, reports a health score and checks that changes do not lower it.

    61k GitHub starsUsed in 12 repos~657 tokens
    Frontend & DesignAuto-check passed
  • React Router Development

    remix-run/react-router

    Guides work on React Router apps by first identifying whether the app uses Framework, Data or Declarative mode, then loading the matching reference and the installed package docs.

    57k GitHub starsUsed in 1 repo~1.5k tokens
    Frontend & DesignAuto-check passed
  • React UI State Patterns

    ChrisWiles/claude-code-showcase

    Sets patterns for React interfaces: when to show loading spinners or skeletons, how to surface errors, how to disable buttons during async work and how to handle empty lists.

    6.1k GitHub starsUsed in 8 repos~1.6k tokens
    Frontend & DesignAuto-check passed
  • Tells the agent where new code belongs in an Electron multi-process project and which APIs each process may use, with rules for new bridges, services, agents and workers.

    33k GitHub starsUsed in 1 repo~1.8k tokens
    DevelopmentAuto-check passed

More from yusifeng/formax

All 21 skills in this repo
  • A skill your agent uses 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…

    195 GitHub stars~1.2k tokensUpdated 2 mo ago
    Auto-check passed
  • Formax Skill Capture

    yusifeng/formax

    A skill your agent uses when we want to turn a just-finished Formax workflow (e.g.

    195 GitHub stars~530 tokensUpdated 2 mo ago
    Auto-check passed
  • Analyze Task

    yusifeng/formax

    A skill your agent uses 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…

    195 GitHub stars~1.2k tokensUpdated 2 mo ago
    Auto-check passed
  • A skill your agent uses 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…

    195 GitHub stars~686 tokensUpdated 2 mo ago
    Auto-check passed
  • Implement or refactor Formax tool transcript UI using the Tool UI Blocks (C-lite) pattern (ToolUiBlocks renderer + blocks presenters) to avoid touching many tool presenter files; use when adjusting…

    195 GitHub stars~1.3k tokensUpdated 2 mo ago
    Auto-check passed
  • A skill your agent uses when designing, refactoring, or debugging Formax system prompt assembly, system-reminder injection, or skills/deferred-tool prompt exposure semantics; mandatory for any…

    195 GitHub stars~1k tokensUpdated 2 mo ago
    Auto-check passed

Works with

Questions about Formax Semantics Parity Workflow

What does Formax Semantics Parity Workflow do?

A skill your agent uses when implementing or modifying behavior that must stay consistent across TUI and Web (mode/input/tool/replay/order). Formax Semantics Parity Workflow is an agent skill from yusifeng/formax. Use when implementing or modifying behavior that must stay consistent across TUI and Web (mode/input/tool/replay/order).

When should I use Formax Semantics Parity Workflow?

Formax Semantics Parity Workflow fits situations like: modifying behavior that must stay consistent across TUI and Web (mode/input/tool/replay/order).

How do I install Formax Semantics Parity Workflow in Claude Code?

Run `npx skills add yusifeng/formax --skill formax-semantics-parity-workflow -a claude-code`. Or copy the skill folder (.codex/skills/formax-semantics-parity-workflow in yusifeng/formax) into .claude/skills/formax-semantics-parity-workflow in your project. Claude Code loads it when a task matches its description.

How do I install Formax Semantics Parity Workflow in Codex?

Run `npx skills add yusifeng/formax --skill formax-semantics-parity-workflow -a codex`. Or copy the skill folder (.codex/skills/formax-semantics-parity-workflow in yusifeng/formax) into .agents/skills/formax-semantics-parity-workflow in your project. Codex loads it when a task matches its description.

Can I use Formax Semantics Parity Workflow in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add yusifeng/formax --skill formax-semantics-parity-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/formax-semantics-parity-workflow, .gemini/skills/formax-semantics-parity-workflow, .github/skills/formax-semantics-parity-workflow and .opencode/skills/formax-semantics-parity-workflow in your project.

What does Formax Semantics Parity Workflow need to run?

Going by SKILL.md and its folder, Formax Semantics Parity Workflow needs the command-line tools its instructions call (bun and npm).

Does Formax Semantics Parity Workflow access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Formax Semantics Parity Workflow safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Formax Semantics Parity Workflow use?

Formax Semantics Parity Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Formax Semantics Parity Workflow use?

About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 997 tokens, read only when the agent opens those files.

What are the alternatives to Formax Semantics Parity Workflow?

Skills that share tags, products or a category with Formax Semantics Parity Workflow: Web Artifacts Builder (anthropics/skills, 180k stars), Vercel Composition Patterns (supabase/supabase, 111k stars), React Doctor (makeplane/plane, 61k stars) and React Router Development (remix-run/react-router, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Formax Semantics Parity Workflow?

yusifeng (a GitHub user) maintains it in yusifeng/formax, which has 195 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on July 24, 2026.

Source: yusifeng/formax on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.