remarque

Build a new page in a project that consumes `remarque-tokens` — pick the right archetype, fetch registry items instead of transcribing markup, wire the page per AGENT_RULES pitfalls, and gate on remarque-audit plus the registry's own markup-contract assertions. Use when the user says "new page", "add a page", "build an essay", "build an archive page", "build a landing page", "use an archetype", or asks for a page in a Remarque-consuming project. Companion to the `remarque` loader skill — load that one first for the tier rules and the two build-time pitfalls; this skill is the page-building procedure on top of it, not a restatement of it.

Run the remarque-tokens consumer-conformance playbook — the exact procedure for bumping a project's remarque-tokens pin and getting back to a passing audit. Use when the user says "bump remarque-tokens", "upgrade the design system", "adopt remarque in an existing site", "update to the latest remarque-tokens", or when `remarque-audit`/`npm run audit` starts failing after a version bump (missing-token failures). Distinct from the `remarque` skill, which is the build/review contract for pages already on the current version — load this one specifically for the migration itself, then defer to `remarque` for any actual page work the migration surfaces.

Load the Remarque design system's implementation contract before building, editing, or reviewing any page in a Remarque-based project — a typography-first system for editorial, technical, and personal sites (17px body floor, three-font system, four-then-seven page archetypes, strict token tiers). Use when the user says "remarque", "design system", "build a new page", "new archetype page", "style this like the site", or asks for a page/component in a project that imports `remarque-tokens`. Also use before reviewing a PR that touches design-system tokens or page layout in such a project.