From pagekit
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.
npx claudepluginhub hnshah/pagekit --plugin pagekitThis skill uses the workspace's default tool permissions.
You are running step 02 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 02 of the PageKit method.
./references/prompt.md./references/framework.md — what makes a strong message spine./references/template.mdruns/<run-name>/signal-doc.md from step 01../references/prompt.md.runs/<run-name>/prompts/02-message-spine.md.runs/<run-name>/outputs/02-message-spine-output.md.runs/<run-name>/message-spine.md.working-log.md.A strong message spine:
If the spine sounds like the signal doc rephrased, the reduction did not happen. Push back, or strengthen source briefs and rerun step 01 first.
Watch for "comprehensive solution," "powerful platform," and other category-default phrases sneaking into the spine. The spine should be in the product's own voice as much as possible. See ../pagekit/references/anti-slop.md.
After the spine is in place, invoke pagekit-first-page-decision (step 03). Do not stop here.