菜单
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?"
用 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.
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.
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.
| name | pagekit-first-page-decision |
| description | 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?" |
You are running step 03 of the PageKit method. This step is the one that stops the method from quietly defaulting to a homepage.
./references/prompt.md./references/framework.md — the full decision framework./references/template.mdruns/<run-name>/signal-doc.mdruns/<run-name>/message-spine.mdruns/<run-name>/sources/04-mechanism-brief.md, 05-proof-brief.md, 06-comparison-brief.md (if they exist; absence is itself a signal that the decision will be weaker)../references/prompt.md.runs/<run-name>/prompts/03-first-page-decision.md.runs/<run-name>/outputs/03-first-page-decision-output.md.runs/<run-name>/first-page-decision.md.working-log.md with the chosen page and one-sentence-each rationale for rejected candidates.The decision MUST list at least three candidate first pages. Minimum candidates for a trust-heavy object:
Candidates must be peer first-page alternatives (same intent-commitment level as a homepage), NOT later-funnel pages. A pricing page, features page, docs page, integrations page, or comparison page is NOT a first-page alternative. If the rejected candidates are downstream pages, the step has not been done.
For each candidate, the chosen one and every rejected one, write one paragraph stating the case FOR the candidate BEFORE any reason to reject. If you cannot write a credible case for a candidate, you have not really considered it. Either think harder about what would make that candidate strong for this object, or drop it and replace it with one you can argue for.
If any candidate is dismissed in one sentence, the step has not been done.
The canonical worked example is runs/vegan-dog-food-verdel/first-page-decision.md. Four labeled candidates (A: homepage, B: trust/safety landing, C: allergy landing, D: nutrition deep-dive), a paragraph-long case for each, a deliberate non-homepage choice with specific reasoning against the other three, plus a confidence basis. If the output you are producing does not match that shape, go back and rework it.
A strong first-page decision:
If the chosen page is "homepage," the rationale must explain why homepage earns it for this object, not simply because that is what people usually build first. If you cannot articulate the why, the message spine is probably too thin; go back to step 02.
After the decision is in place, invoke pagekit-page-argument-shape (step 04). Do not stop here.