Skill

pagekit-proof-map

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.

Install

npx claudepluginhub hnshah/pagekit --plugin pagekit

Tool Access

This skill uses the workspace's default tool permissions.

Preview

You are running step 05 of the PageKit method.

Supporting Assets

references/framework.mdreferences/prompt.mdreferences/template.md

SKILL.md

Similar Skills

ui-ux-pro-max

Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.

ui-ux-pro-max

57.6k

context7-mcp

Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.

context7-plugin

51.8k

startup-financial-modeling

Builds 3-5 year financial models for startups with cohort revenue projections, cost structures, cash flow, headcount plans, burn rate, runway, and scenario analysis.

startup-business-analyst

32.9k

Stats

Stars5

Forks2

Last CommitApr 16, 2026

Actions

View Source View Plugin View on GitHub View README

PageKit step 05 — Proof Map

You are running step 05 of the PageKit method.

Read first

./references/prompt.md

./references/framework.md

./references/template.md

Inputs

runs/<run-name>/first-page-decision.md

runs/<run-name>/page-argument-shape.md

runs/<run-name>/sources/05-proof-brief.md (if it exists)

Procedure

Load ./references/prompt.md.

Substitute the artifacts above.

Save the substituted prompt to runs/<run-name>/prompts/05-proof-map.md.

Prompt the model.

Save the raw response to runs/<run-name>/outputs/05-proof-map-output.md.

Distill into runs/<run-name>/proof-map.md.

Update working-log.md.

Quality gate

A strong proof map:

commits to what the page can honestly claim today

names what the page cannot yet support

maps proof to specific argument moves, not to the page in general

makes the gap between available proof and needed proof visible

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.

Hard rule

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.

PageKit step 05 — Proof Map

You are running step 05 of the PageKit method.

Read first

./references/prompt.md
./references/framework.md
./references/template.md

Inputs

runs/<run-name>/first-page-decision.md
runs/<run-name>/page-argument-shape.md
runs/<run-name>/sources/05-proof-brief.md (if it exists)

Procedure

Load ./references/prompt.md.
Substitute the artifacts above.
Save the substituted prompt to runs/<run-name>/prompts/05-proof-map.md.
Prompt the model.
Save the raw response to runs/<run-name>/outputs/05-proof-map-output.md.
Distill into runs/<run-name>/proof-map.md.
Update working-log.md.

Quality gate

A strong proof map:

commits to what the page can honestly claim today
names what the page cannot yet support
maps proof to specific argument moves, not to the page in general
makes the gap between available proof and needed proof visible

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.

Hard rule

After the proof map is in place, invoke pagekit-first-page-draft (step 06). Do not stop here.