From pagekit
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?"
npx claudepluginhub hnshah/pagekit --plugin pagekitThis skill uses the workspace's default tool permissions.
You are running step 03 of the PageKit method. **This step is the one that stops the method from quietly defaulting to a homepage.**
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 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.