Install and integrate @luolink/footer-badges into an existing Next.js project that already has a footer. Use when Codex needs to add the footer badge system, preserve the site's existing footer layout, discover the right footer and layout files automatically, add runtime badge fetching, add the revalidate route, configure fallback badges, or wire the required environment variables for a project that consumes footer-badges-hub.
Install the footer badge system into an existing project without replacing the project's current footer.
scripts/scan_next_footer_project.py <repo-path> before editing.scripts/scaffold_footer_badges_integration.py <repo-path> --project-id <project-id> --install.@luolink/footer-badges, create fallback config, create the revalidate route, create FooterBadgesSlotServer, patch the preferred layout, and update the env example.FooterBadgesSlotServer pattern for one-shot integration because it avoids rewriting the existing footer internals.FOOTER_BADGES_CONFIG_URLFOOTER_BADGES_PROJECT_IDFOOTER_BADGES_REVALIDATE_SECONDSFOOTER_BADGES_REVALIDATE_TOKENUse the bundled scan script first:
python <skill-path>/scripts/scan_next_footer_project.py <repo-path>
Treat the scan output as the default edit plan unless direct inspection shows a better target.
Then run the scaffold script:
python <skill-path>/scripts/scaffold_footer_badges_integration.py <repo-path> --project-id <project-id> --install
Use --dry-run first when you want a non-destructive preview.
getRemoteFooterBadges() on the server.FooterBadgesMarquee only for the badge area.FooterBadgesSlotServer wrapper inserted immediately after the existing footer in the main layout.handleFooterBadgesRevalidate() for the refresh API.Read references/integration-patterns.md before editing. Reuse those patterns and adapt them to the target repo instead of inventing a new structure.