一键导入
formax-test-stability-workflow
Use when adding or fixing Formax tests (especially Ink UI tests) and you need deterministic synchronization in test interactions.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use when adding or fixing Formax tests (especially Ink UI tests) and you need deterministic synchronization in test interactions.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when the user wants a reusable rolling execution pattern (README + TODO-INDEX) like plans/web-reference-react-refactor, and wants to run delivery in small validated loops.
Use when changing web CSS/UI styling so requirements, state ownership, and acceptance checks are locked before edits to prevent rework churn.
Use after task analysis when a non-trivial Formax repository task needs a structured `docs/todolist.md` with [x]/[ ] items, definitions-before-UI ordering, explicit non-goals, tests, and loop-ready execution slices.
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.
Use after receiving WebGPT or another LLM review on a Formax todo and before sending the todo back for another pass. Produce a concise handoff response that says what we adopted, what we reject or question, and what the reviewer should specifically re-evaluate in `docs/todolist.md`.
Use for all frontend and web UI tasks by default to apply a business-agnostic desktop web visual style system with medium-strength guardrails; if an existing design system is present, follow it first and use this skill only as a style harmonizer.
| name | formax-test-stability-workflow |
| description | Use when adding or fixing Formax tests (especially Ink UI tests) and you need deterministic synchronization in test interactions. |
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).