nextjs-static-init

What problem does it solve?

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.

Core Features & Use Cases

• Strict baseline setup: Pre-configured TypeScript, ESLint, Prettier, and Tailwind 4 configurations with guardrails against common bugs and anti-patterns like unsafe type casts and manual React memoization.
• GitHub Pages native deployment: Auto-configured basePath, asset prefixes, .nojekyll file, and GitHub Actions workflow for seamless push-to-deploy without external hosting services.
• Static export compatibility guardrails: Clear guidance on incompatible Next.js features (API routes, server actions, middleware) to avoid broken builds, plus instructions for migrating to full-stack hosts if needed.
• Use Case: Ideal for developers building personal blogs, documentation sites, portfolios, or marketing sites that need free, serverless hosting on GitHub Pages with no backend runtime.

Quick Start

Use the nextjs-static-init skill to scaffold a new static Next.js project fully configured for automatic deployment to GitHub Pages.