---
name: page
description: Create or refine one page from a selected design repository's approved brief, relevant components and native tokens. Use for an explicitly scoped page task or authorized audit corrections.
---

# Create or refine a page

Read [the shared operating contract](../../references/operating-contract.md) and
[the input contract](../../references/inputs.md) first. Read current workspace
instructions and design core, the repo's common contract and **only** its `page`
template. Use one matching brief/profile and relevant components/layouts/tokens.

Additional required input: `pageTask`, intended user task and exact change
scope. Optional currentArtifact, reference, content, audience, primary action,
viewports and language stay attributable. An absent matching brief is
unresolved; do not copy requirements from another page.

Axes default `5 / 5 / 5`; explicit values are integers 1–10. Without a reference
or established structure, explain why structuralCopying is inactive while
preserving the supplied integer. Axes cannot relax locks, rules, required
states, accessibility or verified facts.

1. Resolve shared inputs, destination edits, locks and actual capabilities.
   The optional read-only [context helper](../../scripts/context.py) addresses
   this MVP's catalog/profile/native-token layout; use equivalent manual
   selection for other repos, without claiming a universal adapter.
2. Determine audience, one main task, primary action, supported facts, section
   order, conditional visibility, navigation and states from the brief. A new
   feature remains a proposal until verified requirements support it.
3. Map each section's intent, content/evidence, action, component anatomy,
   tokens, states and responsive behavior. Reuse approved variants; never
   fabricate IDs, CSS declarations or unavailable runtime primitives.
4. Complete the authorized page within the resolved destination. Use native
   layout primitives: parent gap/padding, per-axis Fill/Hug, auto-height text,
   short labels Hug and a reflowing ordered list for conditional sections, or
   verify their equivalents in the actual codebase. Preserve unrelated work.
5. Review Before → After → Why → Principle → Verification and the scoped diff.
   Run meaningful project checks and inspect actual widths, long copy, states,
   containment, bindings, measured contrast pairs, keyboard and focus. Static
   prose is not evidence of rendering or current Figma bindings.
6. Return the shared envelope, ordered section inventory, responsive rules,
   navigation/state coverage, actual checks and exact remaining dependencies.

If implementation access or definitions are absent, complete a bounded draft
specification and state the missing dependency. No automatic commit, push,
deploy, publish, delete, installs or persistent permissions. Design-system
compliance is mandatory **100%**, never a score or guarantee.