Menú
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.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
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.
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-proof-map |
| description | 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. |
You are running step 05 of the PageKit method.
./references/prompt.md./references/framework.md./references/template.mdruns/<run-name>/first-page-decision.mdruns/<run-name>/page-argument-shape.mdruns/<run-name>/sources/05-proof-brief.md (if it exists)./references/prompt.md.runs/<run-name>/prompts/05-proof-map.md.runs/<run-name>/outputs/05-proof-map-output.md.runs/<run-name>/proof-map.md.working-log.md.A strong proof map:
If the proof map is "we have testimonials" and not much more, the upstream proof brief is too thin. Add specifics or accept a narrower draft.
Do not invent proof. If the page wants to say something that the proof map cannot support, the draft step will mark it with *[verification flag: ...]*. This map is where those gaps are surfaced first.
After the proof map is in place, invoke pagekit-first-page-draft (step 06). Do not stop here.