From pagekit
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.
npx claudepluginhub hnshah/pagekit --plugin pagekitThis skill uses the workspace's default tool permissions.
You are running step 01 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 01 of the PageKit method.
./references/prompt.md — the canonical prompt for this step./references/framework.md — what makes a signal doc strong./references/template.md — the artifact shape./references/wedge-definition-template.md — use when the first signal pass is too category-levelruns/<run-name>/sources/ (especially 02-product-brief.md)../references/prompt.md.[PASTE HERE].runs/<run-name>/prompts/01-signal-doc.md.runs/<run-name>/outputs/01-signal-doc-output.md.runs/<run-name>/signal-doc.md per ./references/template.md.runs/<run-name>/working-log.md.A strong signal doc:
If the doc is too generic or too category-level, do not advance to step 02. Create a wedge-definition brief (./references/wedge-definition-template.md) or a sharper product brief, then rerun this step.
Signal docs themselves rarely produce slop, but if the output uses confident-sounding empty words ("comprehensive," "deeply understands," "transforms"), strip them. Real signal is specific. See ../pagekit/references/anti-slop.md for the full catalog.
After this step's artifact is in place, invoke pagekit-message-spine (step 02). Do not stop here. The signal doc is not the deliverable; the draft is, and the chain must run to completion (see the orchestrator's self-check).