page-creation-and-review

name	page-creation-and-review
user-invocable	false
description	Use when creating a new website page or reviewing an existing page; when deciding page purpose, required content, structural ownership, UX fit, or whether the page should exist at all.

Page Creation and Review

What this skill is for

Use this skill when a task is about adding a new page or reviewing a page before it ships.

It covers:

• deciding whether a page should exist,
• defining the page purpose,
• mapping the page to the responsibility matrix,
• checking the page against the review checklist,
• and resolving conflicts with the site’s tenets and system design.

Default file targets

• docs/content-and-information-architecture/page-responsibility.md
• docs/content-and-information-architecture/page-responsibility.md
• docs/website-tenets.md
• docs/content-and-information-architecture/system-design.md
• docs/design-system/ux-patterns.md
• docs/quality-and-growth/content-and-sidebar-strategy.md

When to use

Use this skill for questions such as:

• should this page exist,
• what job should this page do,
• what content must it include,
• what content must it avoid,
• which existing page owns this responsibility,
• and whether the proposed page matches the site’s long-lived rules.

Workflow

1. Identify the page type and primary job.
2. Check the page against docs/content-and-information-architecture/page-responsibility.md.
3. Review the page with docs/content-and-information-architecture/page-responsibility.md.
4. If the page introduces a new structural rule, confirm the change against docs/content-and-information-architecture/system-design.md and website-tenets.md.
5. If the page affects reading flow, sidebar behavior, or monetization placement, coordinate with docs/quality-and-growth/content-and-sidebar-strategy.md and docs/design-system/ux-patterns.md.

Decision rules

If the question is "should we create this page and what must it do," start here.

If the question is "how does this page fit the site architecture," coordinate with system-design.

If the question is "how should this page look or read," coordinate with ux-patterns.

If the question is "how should monetization, sidebars, or related modules behave," coordinate with content-and-sidebar-strategy.

Output expectation

When using this skill, explain:

• whether the page should exist,
• what the page’s primary job is,
• what it must include and avoid,
• whether the matrix or checklist needs updating,
• and whether any system or UX doc must change first.