FAQ

Does Pagewell work with Next.js?

Yes. Pagewell is framework-agnostic and includes Next.js adapter guidance, so the agent should follow the target repo's App Router or Pages Router conventions, metadata patterns, components, and styling rules.

$ bunx skills add ReScienceLab/pagewell --skill pagewell

Installs the Pagewell agent skill via skills.sh.

Astro support

Adapter-based

Pagewell does not assume Astro

The router selects the closest adapter from the discovered repo context. Next.js repos should use the Next.js adapter guidance.

Repo conventions

App Router and Pages Router are different

Pagewell should detect whether routes live in app/**/page.* or pages/* and implement the page using that site's convention.

Same QA

Metadata, schema, and claims still matter

Next.js pages need the same Pagewell QA: title, description, canonical, crawlability, schema, internal links, and supported claims.

Direct answer

Pagewell can generate pages in a Next.js repo when the repo conventions are clear.

The discovery step should record whether the project uses App Router, Pages Router, MDX/content files, route handlers, shared layouts, and metadata helpers. Generation then follows those patterns instead of introducing a new structure.

What Pagewell checks

The context file should tell the agent where pages and metadata belong.

Area	What to document	Why
Routes	app/*/page. or pages/*	Prevents files from landing in the wrong router
Metadata	metadata exports, head helpers, SEO components, or layout conventions	Keeps titles, descriptions, canonicals, and Open Graph consistent
Content	MDX/content folders or inline page components	Matches how the existing site publishes durable pages
Styling	CSS modules, global CSS, Tailwind, design tokens, or component library	Avoids one-off visual systems

Recommended prompt

Ask Pagewell to discover the Next.js site before generating pages.

agent prompt

Use Pagewell to discover this Next.js repo and create PAGEWELL.md.
Detect App Router vs Pages Router, metadata conventions, route patterns, components, styling, and discovery files.
Then generate /use-cases/<slug>, run QA, and update sitemap/robots/llms.txt if the page is indexable.