Free tool

PAGEWELL.md validator for agent context.

Paste a PAGEWELL.md draft and get a browser-only check for the sections agents need before generating search-ready pages as code.

Start validating View all tools

No signup
Runs in browser
No upload

PAGEWELL.md draft

# PAGEWELL.md

Generated: 2026-05-02
Last reviewed: 2026-05-02

PAGEWELL.md is the Pagewell source of truth for this repo. Use it with DESIGN.md before planning, generating, QAing, or maintaining pages.

## Product facts
- Name: Example Product
- Primary CTA: Try Example

## Supported claims
| Claim | Source | Confidence |
|---|---|---|
| Example Product publishes normal website code. | README.md | High |

## Prohibited or unknown claims
- Do not claim guaranteed rankings, revenue, customer counts, or unsupported integrations.

## Site implementation
- Framework: Astro
- Routes: src/pages
- Metadata: layout props
- Design source: DESIGN.md
- Recommended adapter: references/adapters/astro.md

## Route taxonomy
| Intent | Route pattern | Notes |
|---|---|---|
| Docs | /docs/<slug> | Task pages |

## Page and component patterns
- Reuse the existing layout, CTA, FAQ, and card components.

## Generation rules
- Always read DESIGN.md and PAGEWELL.md before generating pages.

## Anti-generic QA rules
- Fail copy that could describe any product after swapping the name.

## QA rules
- Check title, description, canonical, schema, internal links, and discovery files.

Runs locally in your browser. No signup and no upload.

Context QA result Click “Validate PAGEWELL.md” to score the draft.

How to use

Check the context file before asking an agent to generate more routes.

The validator catches missing context sections, weak claim controls, missing route taxonomy, and absent QA rules. It is a first pass, not a substitute for repo discovery.

Paste context

Use your repo's PAGEWELL.md draft or the sample structure generated by the discover-site workflow.

Review required fixes

Missing required sections and claim-control gaps should be fixed before page generation starts.

Run Pagewell discovery

If the validator finds thin site conventions or unknown claims, ask Pagewell to rediscover the repo.

What it checks

A usable context file needs facts, routes, patterns, and QA gates.

Pagewell generation becomes generic when product facts, allowed claims, route patterns, or component rules are missing. This tool scores those areas explicitly.

required sections

Product facts
Supported claims
Prohibited or unknown claims
Site implementation
Route taxonomy
Page and component patterns
Generation rules
Anti-generic QA rules
QA rules

Keep agent context current

Need the context generated from the repo instead?

Install Pagewell and ask the discover-site module to inspect the framework, routes, components, content files, product facts, claims, and discovery files.

$ bunx skills add ReScienceLab/pagewell --skill pagewell

After installing, ask: Use Pagewell to discover this repo and create PAGEWELL.md.

FAQ

Common questions, answered directly.

What does the PAGEWELL.md validator check?

It checks whether a PAGEWELL.md draft has the core sections Pagewell agents need: product facts, supported claims, prohibited or unknown claims, site implementation, route taxonomy, page patterns, generation rules, anti-generic QA rules, and QA rules.

Does this upload my PAGEWELL.md content?

No. This validator runs in your browser with a small client-side script and does not submit the text to a server.

Can this replace Pagewell discovery?

No. It is a quick quality check. The Pagewell discover-site workflow should still inspect the repo and write or update PAGEWELL.md with repo-specific facts.