원클릭으로 Manus에서 모든 스킬 실행

formax-skill-capture

스타193

포크7

업데이트2026년 1월 28일 16:27

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.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

yusifeng

yusifeng/formax

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

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

이 저장소의 다른 Skills

같은 저장소

formax-rolling-plan-loop-workflow

yusifeng/formax

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.

2026-06-04193

formax-web-css-convergence-workflow

yusifeng/formax

Use when changing web CSS/UI styling so requirements, state ownership, and acceptance checks are locked before edits to prevent rework churn.

2026-06-04193

write-task-todo

yusifeng/formax

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.

2026-06-04193

analyze-task

yusifeng/formax

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.

2026-05-23193

webgpt-todo-response

yusifeng/formax

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`.

2026-05-23193

formax-web-style-system

yusifeng/formax

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.

2026-03-19193

name	formax-skill-capture
description	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.

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