菜单
Build a PageKit signal doc from a product description and any source briefs. Step 01 of the PageKit method. Use when the user asks to "build a signal doc," "extract signal from this material," or is starting a PageKit run on a new object.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Run a skeptical claim-check pass on a PageKit first-page draft, at light/normal/hard severity. Step 07 of the PageKit method. Use after a first-page draft exists and you want to validate it before treating it as publishable. Delegates to the pagekit-claim-checker subagent.
Decide which page should exist first for the object, without defaulting to homepage. Step 03 of the PageKit method. Use when the user has a signal doc + message spine and needs to choose the first page, or asks "should this be a homepage?" or "what page should we build first?"
Draft the first page from the full PageKit chain. Step 06 of the PageKit method. Use when steps 01-05 are done and you are ready to write the page itself. The draft must respect the anti-slop drafting constraints.
Reduce a PageKit signal doc into a message spine. Step 02 of the PageKit method. Use when the user asks to "reduce this signal to a spine," "build a message spine," or has finished step 01 and is ready for step 02.
Design the page argument shape — what sections the chosen first page should and should not have. Step 04 of the PageKit method. Use when the first-page decision is made and you need a structure for the draft.
Map proof to the chosen first page section by section. Step 05 of the PageKit method. Use after the page argument shape exists and before drafting.
| name | pagekit-signal-doc |
| description | Build a PageKit signal doc from a product description and any source briefs. Step 01 of the PageKit method. Use when the user asks to "build a signal doc," "extract signal from this material," or is starting a PageKit run on a new object. |
You are running step 01 of the PageKit method.
./references/prompt.md — the canonical prompt for this step./references/framework.md — what makes a signal doc strong./references/template.md — the artifact shape./references/wedge-definition-template.md — use when the first signal pass is too category-levelruns/<run-name>/sources/ (especially 02-product-brief.md)../references/prompt.md.[PASTE HERE].runs/<run-name>/prompts/01-signal-doc.md.runs/<run-name>/outputs/01-signal-doc-output.md.runs/<run-name>/signal-doc.md per ./references/template.md.runs/<run-name>/working-log.md.A strong signal doc:
If the doc is too generic or too category-level, do not advance to step 02. Create a wedge-definition brief (./references/wedge-definition-template.md) or a sharper product brief, then rerun this step.
Signal docs themselves rarely produce slop, but if the output uses confident-sounding empty words ("comprehensive," "deeply understands," "transforms"), strip them. Real signal is specific. See ../pagekit/references/anti-slop.md for the full catalog.
After this step's artifact is in place, invoke pagekit-message-spine (step 02). Do not stop here. The signal doc is not the deliverable; the draft is, and the chain must run to completion (see the orchestrator's self-check).