Menu
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.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | pagekit-first-page-draft |
| description | 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. |
You are running step 06 of the PageKit method. This is where slop prevention bites. The drafting constraints in ../pagekit/references/anti-slop.md are not optional.
./references/prompt.md../pagekit-page-argument-shape/references/framework.md (drafting constraints live here)../pagekit/references/anti-slop.md (the patterns to avoid)All five upstream artifacts:
runs/<run-name>/signal-doc.mdruns/<run-name>/message-spine.mdruns/<run-name>/first-page-decision.mdruns/<run-name>/page-argument-shape.mdruns/<run-name>/proof-map.md./references/prompt.md. Note the embedded anti-slop constraints; do not strip them when substituting inputs.runs/<run-name>/prompts/06-first-page-draft.md.runs/<run-name>/outputs/06-first-page-draft-output.md.runs/<run-name>/first-page-draft.md.scripts/slop-check.sh runs/<run-name>/first-page-draft.md immediately. Resolve every flagged pattern by rewriting the line. Re-run until clean.working-log.md.*[verification flag: ...]*.A strong draft:
*[verification flag: ...]* for any product-specific claim not verified against briefsscripts/slop-check.sh clean before being handed to step 07If the draft is weak: stop, ask what upstream artifact is too thin. Rarely fix at the draft level, fix at the source.
The draft is not the deliverable. The logged run is. After the draft is clean, do not stop. Continue the chain:
pagekit-slop-check on the draft. Resolve any flags.pagekit-claim-check (step 07) at a severity you choose and log. This produces claim-check.md and, if any line was rewritten, first-page-draft-corrected.md.evaluation.md — the run's own honest read of what worked and what stayed thin.pagekit-evaluator-pass to produce evaluator-pass.md — the adversarial second read.working-log.md across every step (replace all scaffold *[Fill in]* placeholders).pagekit-run-check — it must return tier: FULLY LOGGED or tier: PUBLISHABLE.Only once run-check reports FULLY LOGGED (or PUBLISHABLE) is the run done. Stopping at this step leaves the run at ARTIFACT-ONLY, which does not count.
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?"
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.