01 context
Unified context
PAGEWELL.md, DESIGN.md, and the page brief tell the agent what to build, where it belongs, which patterns to reuse, and what claims are allowed.
For teams shipping pages with coding agents
Your agent can write code. Can it ship the whole page?
Pagewell gives the agent the missing contract: product facts, design rules, page playbooks, and QA gates. It turns a brief into routes, metadata, schema, internal links, and discovery updates your team reviews as code.
bunx skills add ReScienceLab/pagewell --skill pagewell - MIT licensed. Free to use.
- Astro, Next.js, Workers, static HTML
- No platform lock-in. Your pages stay in your repo.
- QA for metadata, schema, and claims before you merge
Direct answer
Pagewell is a repo-native skill pack for coding agents. It turns a page brief into reviewable website code — route, content, metadata, schema, internal links, QA notes, and discovery-file updates — while PAGEWELL.md and DESIGN.md keep the agent tied to real facts and site rules.
How Pagewell works
A repeatable path from brief to merge.
Use the same agent workflow for one landing page, a free tool, a comparison page, or an entire SEO/GEO cluster.
02 plan
Spec before code
Pagewell asks for route, coverage, evidence, metadata, schema, links, CTA, and QA requirements before implementation starts.
03 build
Normal website code
The agent edits your Astro, Next.js, Worker, or static site instead of creating a hosted page you have to recreate later.
04 review
SEO/GEO QA
Titles, schema, claims, citations, crawlability, internal links, and discovery files are checked before merge.
What you get
Not a mockup. A route your team can review.
Every run can produce the page structure, copy, metadata, schema, links, and discovery notes as normal repo work — not a generic export pasted into a builder.
| Page type | Output |
|---|---|
| landing page | route, copy, metadata, schema, CTA |
| comparison page | fair positioning, proof, claim QA |
| free tool | working utility UI, SEO shell, WebApplication schema |
| docs/FAQ/glossary | answer-first content, schema, internal links |
| private ABM | noindex page, account brief, shareable route |
Generated page
Landing pages
Campaign pages that match the visitor’s intent and ship with one clear CTA.
Generated page
Comparison pages
Alternatives and vs pages that position honestly and keep claims tied to sources.
Generated page
Docs and tutorials
Task-focused routes with setup steps, examples, and stack-specific guidance.
Generated page
FAQ and glossary
Short, crawlable answers and definitions built for search engines and AI answer surfaces.
Generated page
Free tools
No-signup utilities where the tool does real work before the product CTA appears.
Generated page
Private ABM
Personalized sales pages that stay out of search while following the same design and QA standards.
Your repo, your stack
Keep pages where review already happens.
Pagewell does not move your site into another platform. Agents work inside your Astro, Next.js, Workers, or static HTML setup and follow the route, layout, metadata, and component conventions already there.
adapters/astro.md
adapters/nextjs.md
adapters/cloudflare-worker.md
adapters/static-html.md
adapters/unknown-framework.md
output: routes, components, content, metadata
no runtime, hosted builder, or lock-inDESIGN.md
colors: #000000 #ffffff #0099ff #a6a6a6
typography: Geist + Inter + Geist Mono
components: pill CTAs, dark cards, blue rings
PAGEWELL.md
product facts, claims, routes, patterns, QA rulesOn-brand, every page
Generated pages that look like your site — not a template with your logo swapped in.
DESIGN.md is your visual contract: colors, typography, components, spacing. Agents follow it so every page feels native, not AI-exported.
Ship fast. Don't ship broken.
Check the page before it joins search.
Titles, descriptions, canonicals, schema, claims, links, crawlability, and private-page rules are checked before a route is considered done.
QA gate
Intent match
Every page starts with route, primary query or use case, audience, and CTA before code.
QA gate
Metadata & schema
Titles, descriptions, canonicals, Open Graph, and supported JSON-LD are part of the spec.
QA gate
Claim verification
Agents only use facts from product docs, briefs, or user-provided proof, not invented stats.
QA gate
Discovery updates
Internal links, sitemap, robots, and future discovery files stay aligned with generated routes.
FAQ
Common questions, answered directly.
What is Pagewell?
A repo-native skill pack that teaches your coding agent how to turn page briefs into routes, metadata, schema, links, and QA notes inside your existing website repo.
Who is Pagewell for?
Developers and growth teams who want AI-assisted pages without moving their site into a hosted builder or breaking their stack.
How is Pagewell different from an AI landing page builder?
Builders move the page system into their platform. Pagewell works inside your repo, follows your framework, and outputs code or content your team can review before merge.
What can Pagewell generate?
Landing pages, product pages, use-case pages, comparison pages, docs, FAQs, glossary pages, free tools, and private ABM pages.
What files do Pagewell agents need?
DESIGN.md for your visual rules. PAGEWELL.md for your product facts, claims, and site conventions. Plus a brief for the specific page.
How does SEO/GEO QA work?
Before a page ships, Pagewell checks titles, descriptions, schema, factual claims, internal links, crawlability, and discovery files.
Get started
Ship pages from your repo today.
Install Pagewell and give your agent the context it needs to generate real pages — metadata, schema, and QA included.
- MIT licensed
- Normal repo code
- No hosted builder
- QA for metadata, schema, and claims
bunx skills add ReScienceLab/pagewell --skill pagewell Installs the Pagewell agent skill via skills.sh.