Skip to content
cccskills
FreePublished on GitHub

formax-test-stability-workflow

Use when adding or fixing Formax tests (especially Ink UI tests) and you need deterministic synchronization in test interactions.

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

See how to install

Files included (1)

  • SKILL.md854 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Formax Test Stability Workflow

Goal

  • Write stable UI tests with explicit state sync.

Do

  • Wait for target state before next key (example: wait ❯ 3. before typing feedback).

  • Assert final behavior, not transient cursor frames (example: assert feedback aXb, not a▏b).

  • In multi-step input flows, wait for idle state between steps (example: placeholder/queue-hint settled).

  • Extract repeated sync steps into local helpers (example: selectFeedbackRow, queueMessageWhileLoading).

Don't

  • Do not fix flakes by only increasing timeout.
  • Do not use long sleep as synchronization.
  • Do not bind assertions to fragile render glyphs/spacing.

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