Communitygithub.com

BIGboss248/nextjs-wordpress

>- Bootstrap, configure, and verify the complete Next.js App Router development environment, developer tooling, testing suites, MCP servers, Docker containerization, and CI/CD. Triggers on "/nextjs-dev-setup", "setup nextjs dev environment", "start a nextjs project", or "containerize nextjs app".

What is nextjs-wordpress?

nextjs-wordpress is a Antigravity agent skill that >- Bootstrap, configure, and verify the complete Next.js App Router development environment, developer tooling, testing suites, MCP servers, Docker containerization, and CI/CD. Triggers on "/nextjs-dev-setup", "setup nextjs dev environment", "start a nextjs project", or "containerize nextjs app".

Works with~Claude Code~Codex CLI~Cursor✓Antigravity✓Gemini CLI
npx skills add https://github.com/BIGboss248/nextjs-wordpress/tree/HEAD/.agents/skills/nextjs-dev-setup

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

Next.js Development Setup (nextjs-dev-setup)

A structured, end-to-end orchestration runbook for discovering, configuring, and verifying the Next.js App Router development environment, reverse proxy routing (Traefik / Nginx), and single source of truth at docs/project.json.


Pre-Conditions & Discovery

  • Zero-Interruption Scan: Scan existing repository files (package.json, lockfiles, stylesheets, docs/adr/*.md, docs/plan.md, CONTEXT.md) before asking questions.
  • Consult project-json-schema.md for metadata structure and automated deduction rules.

Phase 0: Multi-Round Setup Interview (Grilling) & Plan Generation

Conduct the interactive interview in progressive, adaptive rounds (waiting for user response after each round) to tailor the setup:

  1. Round 1 (Scope & Tooling): Probe target testing suites (Jest, Playwright, Storybook), MCP servers, and @shadcn/lint enforcement.
  2. Round 2 (Reverse Proxy & Production Hosting): Probe domain name, port, and reverse proxy strategy:
    • Traefik via Docker Compose: Automated container discovery using Compose labels reading from environment variables (${DOMAIN_NAME}, ${TRAEFIK_ENTRYPOINT}, ${TRAEFIK_CERTRESOLVER}) with anti-buffering.
    • Nginx via Host System: Standalone configuration in /etc/nginx/sites-available/<domain> using Certbot SSL certificates.
  3. Round 3 (CI/CD, Git Hooks & Registry): Probe Husky pre-push test suites, Commitlint, and GitHub Actions Release Please / GHCR workflows.
  4. Consult setup-interview-rounds.md for complete question sets and branching logic.
  5. Plan & Execution: Generate and present an implementation_plan.md artifact detailing all planned file creations, configurations, and packages before applying changes, and proceed directly with execution without waiting for manual confirmation.

Step-by-Step Execution Flow

Stage 1: Project Metadata & Developer Tooling (docs/project.json)

  1. Initialize docs/project.json using project.template.json based on user interview choices.
  2. Configure .vscode/launch.json using vscode-launch.json.template.
  3. Scaffold app/providers.tsx with <ProgressBarProvider> using providers.tsx.template and composite <Link> using Link.tsx.template.
  4. Scaffold .env.example using env.example.template for production and .env.local using env.local.template for local development.
  5. App Icons, Apple Icon & PWA Manifest: Deploy manifest.ts.template to app/manifest.ts. Configure the user-provided favicon across root app/favicon.ico, app/icon.png, and app/apple-icon.png (or dynamic ImageResponse icon). Consult app-icons-and-pwa-guide.md.

Stage 2: Testing Suites (Jest, Playwright & Instant Navigation)

[!IMPORTANT] No Dummy Test Files (Rule 3): Do not create placeholder/sample test files in the workspace. Configure framework files and scripts only. Sample patterns are available in sample-component.test.tsx, sample-navigation.spec.ts, and sample-component.stories.tsx.

  1. Jest Unit Testing: Configure jest.config.ts.template and jest.setup.ts.template.
  2. Playwright E2E & Instant Navigation: Install @playwright/test and @next/playwright (pnpm add -D @playwright/test @next/playwright), configure playwright.config.ts.template, and install browsers.
  3. Next.js Instant Config: Configure cacheComponents: true, partialPrefetching: true, and instant insights in next.config.ts.
  4. Storybook Workshop: Configure .storybook/main.ts and .storybook/preview.tsx.
  5. Review architectures in testing-guide.md and storybook-guide.md.

Stage 3: Dual MCP Server Configuration

[!IMPORTANT] Antigravity Global MCP Loading Rule: AG only loads MCP servers configured globally on the host system (~/.gemini/antigravity/mcp_config.json and ~/.gemini/config/mcp_config.json). Workspace mcp.json is maintained for portability. Both must be configured.

  1. Configure next-devtools, playwright, storybook, and codebase-memory-mcp.
  2. Stutter Prevention: Set auto_watch = false via codebase-memory-mcp config set auto_watch false and deploy root .cbmignore.
  3. Review full specs in mcp-configuration-guide.md.

Stage 4: Agent-First Design System Linting (@shadcn/lint)

  1. Install @shadcn/lint and configure ESLint flat config using eslint.config.mjs.template.
  2. Review mechanics in styling-and-linting-guide.md.

Stage 5: Standalone Production Docker & Reverse Proxy (Traefik / Nginx)

  1. In next.config.ts: resolve Git commit hash (getGitCommitHash() with CI fallbacks) and package version, inject NEXT_PUBLIC_APP_VERSION and NEXT_PUBLIC_GIT_COMMIT_HASH under env, enable output: "standalone", set deploymentId for version skew protection (${pkg.version}-${gitHash}), configure headers with X-Accel-Buffering: no, and set experimental.serverActions.allowedOrigins.
  2. Document NEXT_SERVER_ACTIONS_ENCRYPTION_KEY in .env.example and pass it to runtime environments.
  3. Deploy Dockerfile.template (with STOPSIGNAL SIGTERM) and docker-compose.yml.template (with stop_grace_period: 30s).
  4. Reverse Proxy Configuration:
    • Traefik: Deploy docker-compose.prod.yml.template with dynamic environment variable labels (${DOMAIN_NAME}, ${TRAEFIK_ENTRYPOINT}, ${TRAEFIK_CERTRESOLVER}) and anti-buffering middleware.
    • Nginx: Deploy or output nginx-site.conf.template for /etc/nginx/sites-available/<domain> with Certbot SSL certificates.
  5. Review architecture and multi-container cache drift callout in docker-containerization-guide.md.

Stage 6: Git Hooks & Credit-Optimized CI/CD

  1. Install husky, @commitlint/cli, @commitlint/config-conventional.
  2. Configure commitlint.config.mjs.template, .husky/commit-msg, and .husky/pre-push (pnpm run test:all).
  3. Deploy .github/workflows/release-please.yml with .next/cache build caching and multi-arch matrix publishing.
  4. Review caching in cicd-and-release-automation-guide.md.

Stage 7: Final Execution Report & Verification

  1. Execute the configuration verification script and ensure all checks pass.
  2. Stage all created/modified files in git (git add .) per Rule 36.
  3. Mandatory Final Output: Render the complete, structured Next.js Dev Setup Execution Report markdown table summarizing all implemented files, verification check results, and next development steps.

Verification & Sanity Check

  • Execute configuration verification script:
    • Windows (PowerShell): powershell -ExecutionPolicy Bypass -File .agents/skills/nextjs-dev-setup/scripts/verify-project-config.ps1
    • Linux / macOS (Bash): bash .agents/skills/nextjs-dev-setup/scripts/verify-project-config.sh
  • Fix any reported errors and re-verify until all checks pass.

Edge Cases & Known AI Pitfalls

  • Chained Commands: Never chain commands with && or ; on a single line in terminal execution.
  • MCP Disabling: In AG global configs, agy.exe ignores "disabled": true inside mcpServers. Move disabled servers outside mcpServers.
  • Docker Image Names: Docker OCI naming strictly requires lowercase repository names (IMAGE_NAME=$(echo ... | tr '[:upper:]' '[:lower:]')).
  • Storybook Intl Context: Always wrap Storybook stories rendering Link or useTranslations with NextIntlClientProvider.

Mandatory Final Output: Execution Report Template

Always output this report upon completing the skill workflow:

## 🛠️ Next.js Dev Setup Execution Report

| Step / Component                     | Target File(s) / Resource                                                                              | Status                          | Notes / Details                                                                  |
| :----------------------------------- | :----------------------------------------------------------------------------------------------------- | :------------------------------ | :------------------------------------------------------------------------------- |
| **1. Project Metadata**              | `docs/project.json`                                                                                    | `[IMPLEMENTED]` / `[UNTOUCHED]` | Configured package manager, directories, animation & i18n metadata.              |
| **2. App Icons & PWA Manifest**      | `app/manifest.ts`, `app/favicon.ico`, `app/apple-icon.png`, `app/icon.png`                             | `[IMPLEMENTED]` / `[UNTOUCHED]` | Configured root favicon, Apple touch icon, and Web App Manifest using user favicon. |
| **3. Core Dependencies**             | `package.json`, Lockfile                                                                               | `[IMPLEMENTED]` / `[UNTOUCHED]` | Verified React, Next.js, styling, and motion libraries.                          |
| **4. Next.js Dev Server MCP**        | `~/.gemini/antigravity/mcp_config.json`, `mcp.json`, `.agents/plugins/workspace-tools/mcp_config.json` | `[IMPLEMENTED]` / `[UNTOUCHED]` | Configured Next.js Dev Server (`next-devtools`) globally for AG & in workspace.  |
| **5. Playwright & Instant Testing** | `playwright.config.ts`, `@next/playwright`, `mcp.json`, `~/.gemini/antigravity/mcp_config.json` | `[IMPLEMENTED]` / `[UNTOUCHED]` | Verified runner, browsers, Playwright MCP & `@next/playwright` instant navigation helper. |
| **6. Codebase Memory & Stutter Fix** | `.cbmignore`, `mcp.json`, `~/.gemini/antigravity/mcp_config.json`, `auto_watch=false`                  | `[IMPLEMENTED]` / `[UNTOUCHED]` | Registered MCP, configured .cbmignore exclusions, and disabled session watcher.  |
| **7. Jest Unit Testing**             | `jest.config.ts`, `jest.setup.ts`                                                                      | `[IMPLEMENTED]` / `[UNTOUCHED]` | Configured Next.js Jest transformer, jsdom environment & test-dom.               |
| **8. Storybook & Storybook MCP**     | `.storybook/main.ts`, `.storybook/preview.tsx`, `mcp.json`, `~/.gemini/antigravity/mcp_config.json`    | `[IMPLEMENTED]` / `[UNTOUCHED]` | Configured Storybook Vite, a11y, themes & Storybook AI MCP globally & workspace. |
| **9. Agent-First Tailwind Linter**   | `eslint.config.mjs`, `package.json`                                                                    | `[IMPLEMENTED]` / `[UNTOUCHED]` | Configured `@shadcn/lint` for agent verification of design tokens and contracts. |
| **10. Docker & Reverse Proxy**       | `Dockerfile`, `docker-compose.prod.yml`, `nginx-site.conf`, `.dockerignore`                            | `[IMPLEMENTED]` / `[UNTOUCHED]` | Standalone container, Traefik labels / Nginx HTTPS with Certbot SSL.             |
| **11. Husky Git Hooks**              | `.husky/commit-msg`, `.husky/pre-push`                                                                 | `[IMPLEMENTED]` / `[UNTOUCHED]` | Enforces dual pre-push test suite (Jest + Playwright) & commitlint.              |
| **12. Commitlint Config**            | `commitlint.config.mjs`                                                                                | `[IMPLEMENTED]` / `[UNTOUCHED]` | Configured `@commitlint/config-conventional`.                                    |
| **13. Release & CI Build Caching**   | `.github/workflows/release-please.yml`                                                                 | `[IMPLEMENTED]` / `[UNTOUCHED]` | Next.js build cache (.next/cache), SemVer release PRs & GHCR multi-arch pkg.     |
| **14. Environment Verification**     | `scripts/verify-project-config.ps1` / `.sh`                                                            | `[PASSED]`                      | Sanity check passed with zero errors.                                            |

#### Status Definitions:
- **`[IMPLEMENTED]`**: Freshly created, installed, or modified during this setup run.
- **`[UNTOUCHED]`**: Already properly configured prior to running the skill; preserved as-is.
- **`[SKIPPED]`**: Intentionally omitted based on user preference.

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

BIGboss248/nextjs-wordpress

Create, configure, manage, and validate Google Antigravity customizations including skills, rules, MCP servers, lifecycle hooks, plugins, and custom JSON configs. Use when adding new capabilities to Antigravity, configuring MCP servers, writing rules, creating skills, setting up hooks, or modernizing legacy workflows.

BIGboss248/nextjs-wordpress

Spawn multiple agents into a shared conversation where they debate, disagree, and converge on a solution via a shared chat.json file. Use for architecture decisions, code review debates, design trade-offs, or any problem that benefits from adversarial reasoning. Triggers on "chatroom", "agent debate", "have agents discuss", "agent chatroom", "debate this", or /agent-chatrooms. Also triggers on phrases like "have 3 agents argue about", "multi-agent discussion", or "let them debate".

BIGboss248/nextjs-wordpress

Always-active code intelligence, search, and navigation skill utilizing the codebase-memory MCP server. Enforces an index-first protocol (verifying and refreshing the knowledge graph via index_repository or index_status before searching, required because background auto_watch is disabled to eliminate editor stutter and system lag), followed by graph-first exploration (search_graph, trace_path, get_code_snippet, query_graph, get_architecture, detect_changes) instead of naive text grep or full-file reads. Always activate before searching the codebase, inspecting unknown architecture, finding symbols, or tracing callers/callees.

BIGboss248/nextjs-wordpress

>- Discover, interview, and craft comprehensive UX/UI design specifications (design-spec.md) and design tokens for web components. Triggers on "/component-design", "design component", "design section", "design UI", "wireframe component", or "create design spec".

BIGboss248/nextjs-wordpress

>- Configure and query WooCommerce APIs including WPGraphQL, WooGraphQL, and JWT auth for headless frontends. Use when connecting Next.js to WooCommerce or fetching store catalog data.

BIGboss248/nextjs-wordpress

Orchestrate parallel browser automation using multiple Chrome DevTools MCP instances. Use when a task requires doing the same browser action across many targets simultaneously (e.g., submitting contact forms, filling applications, scraping pages that need JS rendering). Spin up 1-5 parallel Chrome agents.

BIGboss248/nextjs-wordpress

Workflow for spawning an independent subagent to conduct unbiased code reviews and inject adversarial edge-case tests ([ComponentName].edge.test.tsx).

BIGboss248/nextjs-wordpress

>- Build Next.js App Router React components with Suspense skeletons, semantic OKLCH tokens, Jest + RTL unit tests, Playwright visual/hydration checks, and Tailwind logical styling. Triggers on "/nextjs-component-dev", "create component", "new component", "build component", or "develop component".

BIGboss248/nextjs-wordpress

>- Configure production health monitoring endpoints (/api/health), Docker Compose probes, and runtime metrics in Next.js App Router applications. Use when asked to "setup health check", "add health endpoint", "docker compose healthcheck nextjs", "configure health monitor", or "/nextjs-healthcheck".

BIGboss248/nextjs-wordpress

Bootstrap, configure, and verify next-intl App Router internationalization (proxy.ts/middleware.ts, next/root-params, [locale] layout, routing). Triggers on "/nextjs-i18n-setup", "setup i18n", "install next-intl", "configure next-intl", "add internationalization", "setup locale routing", "migrate to [locale]".

BIGboss248/nextjs-wordpress

Read/write translation dictionaries (messages/[locale].json), next-intl hooks (getTranslations/useTranslations), providers (Storybook/tests/subtrees), and BiDi styling. Triggers on "/nextjs-i18n-usage", "i18n dictionary", "use translations", "read dictionary", "i18n provider", "next-intl hooks", "storybook i18n", "test i18n", "add translation keys", "localize component", "create a component", "update a component".

BIGboss248/nextjs-wordpress

>- Configure, test, and verify OpenTelemetry (OTel) observability in Next.js App Router applications. Triggers on "/nextjs-otel", "setup otel", "configure opentelemetry", "test otel", or "verify opentelemetry".

BIGboss248/nextjs-wordpress

Step-by-step workflow for designing and building Next.js App Router pages (RSC page.tsx, loading skeleton, metadata, JSON-LD schema, and dynamic static params). Triggers on "/nextjs-page-dev", "create page", "new page", "develop page", "build route", or "implement page".

BIGboss248/nextjs-wordpress

>- Orchestrate end-to-end planning for Next.js App Router projects, generating canonical specifications, design systems, and a 7-phase modular implementation roadmap in docs/plan/. Triggers on "/nextjs-plan", "plan a nextjs project", "plan nextjs app", "create nextjs project plan", "outline nextjs architecture", or "generate plan".

BIGboss248/nextjs-wordpress

Workflow and engineering standards for crafting co-located Storybook CSF3 stories ([ComponentName].stories.tsx) with interactive controls, action spies, and 4 canonical theme variants.

BIGboss248/nextjs-wordpress

>- Build Next.js e-commerce frontends backed by WooCommerce APIs, handling ISR catalogs, cart sessions, and JWT authentication. Use when building or querying Next.js stores with WooCommerce.

BIGboss248/nextjs-wordpress

Self-correcting rules engine and feedback loop that learns from user corrections, mistakes, and project-specific constraints by maintaining a persistent autofix ruleset. Scans learned rules before starting any task, resolves conflicts, and automatically appends new rules upon corrections. Triggers on user corrections ("no, do it this way", "never do X", "always use Y"), /learn, "self repair", "add rule", "update rules", or when diagnosing assumptions and bugs. CRITICAL ALWAYS-ACTIVE LIFECYCLE SKILL. Must always be kept in context, loaded at session start, and consulted before starting ANY task to read and apply active constraints from autofix.json. MUST ALWAYS be triggered immediately whenever the user provides ANY correction, preference, criticism, rejection of an approach, or adjustment ("no", "don't do X", "use Y", "remember", "prefer"), or when any mistake/bug is identified. Automatically and immediately formulates and appends the new imperative rule to the project's autofix.json ruleset file.

BIGboss248/nextjs-wordpress

Setup, automate, and execute SEO audits, CI/CD pre-push/pre-deploy checks, and ranking optimizations using the seo CLI and MCP server.

BIGboss248/nextjs-wordpress

End-to-end repository onboarding and development environment setup skill. Scans repository structure, configures project metadata (docs/project.json), sets up the codebase-memory-mcp code intelligence knowledge graph server (in workspace mcp.json and globally for AGY only), configures git hooks with Husky and Commitlint, establishes multi-stage production Docker containerization, and automates credit-optimized Release Please CI/CD with multi-arch (AMD64 & ARM64) GHCR package deployment. Triggers on "/setup-repository", "setup repository", "setup repo", "initialize repository", "new repo setup", or when preparing any repository for development and AI agent workflows.

BIGboss248/nextjs-wordpress

AI screen scaffolding, layout generation, and variant exploration workflow powered by Google Stitch (StitchMCP). Consumes a component design specification (docs/design/components/[page name]/[component name]/design-spec.md), verifies and reuses the central Stitch project in docs/project.json (or creates/persists one if absent), seeds the project's design system into Stitch, synthesizes layout prompts to generate a screen and create one variant of the given design spec file, downloads and saves Stitch JPG screenshots and HTML code files directly into docs/design/components/[page name]/[component name]/stitch/ using binary-safe PowerShell Invoke-WebRequest, outputs image prompts to the user if visual assets are needed (without calling generate_image to conserve tokens), updates design-spec.md with Stitch layout benchmarks, and audits asset download integrity with an independent subagent. Triggers on "/stitch-design", "generate stitch screen", "create stitch variant", "scaffold screen with stitch", or "stitch...

Related Skills