FAQ

What is PAGEWELL.md?

PAGEWELL.md is the unified Pagewell context file for a repo: product facts, claim rules, site implementation details, route taxonomy, page patterns, generation rules, and QA expectations in one durable place.

$ bunx skills add ReScienceLab/pagewell --skill pagewell

Installs the Pagewell agent skill via skills.sh.

Set up context

Source of truth

One file for page generation context

Instead of scattering product facts, route rules, and site conventions across separate notes, Pagewell points agents to PAGEWELL.md before planning or QA.

Claim control

Supported and prohibited claims stay explicit

The file tells agents what the site can say, what remains unknown, and which claims require proof before copy or schema can use them.

Repo-native

It adapts to the current website

PAGEWELL.md records the actual framework, routes, components, metadata conventions, discovery files, and commands in the repo.

What it contains

PAGEWELL.md captures the facts agents need before writing a page.

Product/company facts, audiences, CTAs, supported claims, and prohibited or unknown claims.
Site implementation details such as framework, rendering mode, route folders, components, layouts, metadata, and discovery files.
Route taxonomy for product, use-case, FAQ, glossary, docs, alternatives, landing pages, private pages, and free tools.
Reusable page/component patterns plus generation, anti-generic QA, and final QA rules.

How agents use it

Generation starts with context, not a blank prompt.

A Pagewell run reads PAGEWELL.md with DESIGN.md, normalizes the brief, selects the right playbook, then implements the route using the site conventions already documented in the repo.

pagewell context loop

PAGEWELL.md + DESIGN.md + page brief
→ page architecture and evidence map
→ implementation in the current stack
→ metadata, schema, internal links, QA
→ sitemap / robots / llms.txt updates when needed

Migration

PAGEWELL.md replaces separate context and product fact files.

Older Pagewell setups may have kept framework notes, product facts, and page patterns in separate files. The current default is to consolidate that useful context into PAGEWELL.md, while DESIGN.md remains separate because it follows the external design contract spec.

File	Role	Status
PAGEWELL.md	Product, site, route, claim, pattern, generation, and QA truth	Default Pagewell context
DESIGN.md	Visual tokens, typography, layout, components, and design constraints	Separate design source
Page brief	The specific route, intent, audience, CTA, and constraints	Per request