nextjs-optimisation-skilllisted

# Next.js Optimisation Use evidence, preserve truthful semantics, and make the smallest change that fixes a demonstrated problem. Treat discovery, rendering, performance, accessibility, and measurement as one system rather than independent score-chasing exercises. ## Start here 1. Read repository instructions such as `AGENTS.md`. 2. Determine the installed Next.js version from `package.json`. 3. Before changing framework APIs, detect the installed version and use its bundled documentation when available, such as `node_modules/next/dist/docs/`. Do not assume the latest Next.js behavior applies to the target project. 4. Inspect the route, its shared layout/components/data, metadata, generated output, tests, and the current git diff. Preserve unrelated user changes. 5. Classify the task: discovery, structured data, rendering, performance, media, animation, analytics, indexing, publishing, or a combination. 6. Open [index.md](index.md), then load only the references and checklist needed for the task. ## Operating workflow ### 1. Establish intent and evidence - Identify the visible purpose, audience, canonical URL, conversion action, and whether the route deserves independent indexing. - Separate objective defects from strategic choices. A missing canonical or invalid JSON-LD is objective; whether a route should be indexed or an animation retained is strategic. - For performance work, record a baseline or identify a concrete payload/runtime cause. Do not claim a score withou