ReddRadar
Agent skill
formax-skill-capture
Use when we want to turn a just-finished Formax workflow (e.g. commands, overlays, tools, hooks, permissions, UI parity) into a reusable Codex Skill under .codex/skills, including scaffolding, guardrails, and the minimum test checklist.
Install this agent skill to your Project
npx add-skill https://github.com/yusifeng/formax/tree/main/.codex/skills/formax-skill-capture
SKILL.md
Formax skill capture (create skills from our workflow)
What this is
This skill is a Formax-specific wrapper around skill authoring: it helps us reliably convert “we just figured out how to do X” into a repo-local skill under .codex/skills/<skill-name>/.
It complements the built-in skill-creator (system skill) by adding Formax conventions:
- repo-local skills (checked into git)
- “where to change what” file map
- invariants (UI parity, model injection orthogonality, etc.)
- minimum regression tests to lock behavior
When to use
Trigger this when the user says:
- “把这个流程沉淀成 skill”
- “以后别再忘了怎么改 /xxx”
- “给我一个复用的修改清单/固定套路”
Minimal questions to ask (do not proceed until answered)
- Skill name (kebab-case), e.g.
formax-slash-command-workflow - 1–2 sentence description: when should Codex use it?
- Scope: which subsystem? (pick one)
- slash commands / overlays
- tools (spec/handler/presenter)
- hooks
- permissions/policy
- stability/input routing
- Any explicit “don’t change” constraints? (UI copy/spacing/colors, contracts, etc.)
Output requirements
The resulting skill must include:
- a short “Goal” section
- “Where to change what” (file list)
- “Patterns” (2–4 common patterns)
- “Tests to update” (minimum regression set)
- “Guardrails” (what must not regress)
Avoid long prose; prefer checklists.
Create a new skill (scaffold)
Use the scaffold script:
bash .codex/skills/formax-skill-capture/scripts/new-skill.sh <skill-name> "<description>"
Then fill SKILL.md body with the content above.
Refactor policy for skills
When a skill is created from a workflow we already shipped:
- Do not broaden scope (no extra features)
- Do not rewrite UI (unless explicitly requested)
- Write/extend tests first if behavior has regressed before
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
yusifeng/formax
formax-dev-loop-workflow
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.
yusifeng/formax
formax-rework-convergence-workflow
Use when code has gone through repeated rework and may contain redundant logic, style drift, or tangled structure. Trigger when user asks for "返工收敛", "cleanup-pass", or requests a focused cleanup pass that reduces churn without changing behavior.
yusifeng/formax
formax-tool-ui-blocks-workflow
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 ⏺/⎿ spacing, indent rules, or migrating additional tools to blocks presenters with targeted Ink/Vitest tests and Codex review before commit.
yusifeng/formax
formax-web-css-convergence-workflow
Use when changing web CSS/UI styling so requirements, state ownership, and acceptance checks are locked before edits to prevent rework churn.
yusifeng/formax
formax-config-settings-workflow
Use when implementing or extending /config (storage, prompt injection, request params, UI-only toggles) with tests and strict UI parity.
yusifeng/formax
formax-semantics-parity-workflow
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.
Didn't find tool you were looking for?