route-metadata-favicons

To set per-route metadata and favicons in Next.js, define the route metadata in a SKILL.md file and trigger the route-metadata tooling. Utilities like createRouteMetadata and createDynamicRouteMetadata apply consistent titles and social previews across layouts.

Auditing missing metadata across a Next.js route tree involves using route-metadata utilities to detect inconsistent titles and broken social previews. The skill enforces metadata best practices to ensure all routes have proper OpenGraph and Twitter card configurations.

Yes, configuring OpenGraph and Twitter card data for individual Next.js routes is supported. The skill applies per-route favicons and social preview metadata, ensuring each route generates the correct social sharing cards and tab titles.

Wiring metadata to Next.js layouts uses createRouteMetadata and createDynamicRouteMetadata utilities to declare and apply metadata hierarchically. This ensures layouts inherit consistent tab titles, favicons, and social previews across the application route tree.

Inconsistent tab titles and broken social previews in Next.js occur when per-route metadata is not centrally managed. Using route-metadata utilities to apply favicons and OpenGraph data enforces best practices and ensures consistent titles and social previews across the route tree.