fixing-metadatalisted

# fixing-metadata Ship correct, complete metadata. ## how to use - `/fixing-metadata` Apply these constraints to any metadata work in this conversation. - `/fixing-metadata <file>` Review the file against all rules below and report: - violations (quote the exact line or snippet) - why it matters (one short sentence) - a concrete fix (code-level suggestion) Do not introduce new frameworks or SEO libraries unless explicitly requested. Prefer minimal diffs. ## when to apply Reference these guidelines when: - adding or changing page titles, descriptions, canonical, robots - implementing Open Graph or Twitter card metadata - setting favicons, app icons, manifest, theme-color - building shared SEO components or layout metadata defaults - adding structured data (JSON-LD) - changing locale, alternate languages, or canonical routing - shipping new pages, marketing pages, or shareable links ## rule categories by priority | priority | category | impact | |----------|----------|--------| | 1 | correctness and duplication | critical | | 2 | title and description | high | | 3 | canonical and indexing | high | | 4 | social cards | high | | 5 | icons and manifest | medium | | 6 | structured data | medium | | 7 | locale and alternates | low-medium | | 8 | tool boundaries | critical | ## quick reference ### 1. correctness and duplication (critical) - define metadata in one place per page, avoid competing systems - do not emit duplicate title, description, canonical, or ro