Scaffold a Next.js project configured for static export to GitHub Pages.
npx skills add https://github.com/M4RC0Sx/claude-skills --skill nextjs-static-init
Please help me install this Agent Skill. Skill: nextjs-static-init Source: https://github.com/M4RC0Sx/claude-skills/tree/main/skills/nextjs-static-init Command: npx skills add https://github.com/M4RC0Sx/claude-skills --skill nextjs-static-init
Manually configuring a Next.js project for static export deployment to GitHub Pages requires setting up dozens of interdependent settings, including build output configuration, path handling for project pages, Jekyll bypass, CI/CD workflows, and strict linting/type checking baselines. Missing any of these steps leads to broken deployments, incorrect asset paths, or use of features incompatible with static hosting.
Use the nextjs-static-init skill to scaffold a new static Next.js project fully configured for automatic deployment to GitHub Pages.
High-intent search queries and answers about installing and using this skill.
Configuring Next.js static export for GitHub Pages requires setting build output options, basePath, asset prefixes, and a CI/CD workflow. This process ensures correct asset path handling and automated push-to-deploy hosting without external services.
Broken asset paths in a Next.js static export on GitHub Pages typically occur when the basePath and asset prefixes are not configured for the repository URL structure. Correctly setting these path handling properties ensures assets resolve properly.
Next.js features incompatible with static export include API routes, server actions, and middleware. These features require a backend runtime and will cause broken builds when deploying a static site to serverless hosting like GitHub Pages.
Setting up TypeScript and Tailwind CSS 4 for a Next.js static site requires configuring strict ESLint, Prettier, and TypeScript baselines. This configuration provides guardrails against common bugs like unsafe type casts and manual React memoization.
You do not need a backend runtime to host a Next.js documentation site or portfolio if you use static export. This approach enables free, serverless hosting on GitHub Pages, provided you avoid incompatible full-stack features like API routes.
To bypass Jekyll processing when deploying a static site to GitHub Pages, you include a .nojekyll file in your build output directory. This prevents GitHub Pages from ignoring files with underscores and ensures raw static assets are served correctly.
TbK0ngInitialize Trellis AI workflow scaffolding with .trellis structure, memory, and CLI hooks.
therealbillAutomate Hugo site deployment to GitHub Pages with a GitHub Actions workflow.
patricio0312revConfigure ESLint and Prettier for TypeScript and React projects.
AIDotNetGenerate Next.js 14+ App Router components, API routes, and middleware.
