From pagekit
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.
npx claudepluginhub hnshah/pagekit --plugin pagekitThis skill uses the workspace's default tool permissions.
You are running step 05 of the PageKit method.
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.
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.
Builds 3-5 year financial models for startups with cohort revenue projections, cost structures, cash flow, headcount plans, burn rate, runway, and scenario analysis.
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.