claude

nexa-claude-nextjs

Nexa Agentic Engineering plugin for the Next.js stack

6 on GitHubby Marius AchimApache-2.0updated 1 month ago
/

Plugin nexa-claude-nextjs from marketplace nexa-claude-marketplace in nexadevapp/nexa-claude-skills-marketplace. Commands read from the repo's manifest — 1 month ago.

This plugin runs code on your machine — it starts local MCP servers. The exact commands are listed below; read them before installing.

What it installs

Skills (19)

  • audit

    Runs a comprehensive implementation audit for a delivered use case. Checks Definition of Done, i18n completeness and correctness, error message i18n, accessibility, visual fidelity against the design, and loading/error states. Run after /deliver-use-case or before /merge-use-case for a quality deep-

  • code-quality

    Runs oxlint and oxfmt on TypeScript/JavaScript files to fix lint errors, enforce cyclomatic complexity limits, and apply consistent formatting. Use when the user asks to "lint", "format code", "run code quality checks", or mentions code quality, formatting, or static analysis.

  • deliver-cluster

    Delivers a cluster of use cases in parallel. Reads the dependency graph, works out which use cases can run at the same time, creates one git worktree per use case, runs /deliver-use-case in each, and feeds every finished branch to /merge-use-case one at a time. Repeats until the cluster is delivered

  • deliver-use-case

    Orchestrates the full per-use-case delivery pipeline: writes the specification and the design if they are missing, implements the use case, writes E2E tests, and evaluates coverage against the spec. Iterates automatically until quality gates pass. The use case must be elaborated by /engineer-require

  • implement

    Implements use cases and fixes bugs by creating Next.js pages, components, API route handlers, and server actions. Use when the user asks to "implement a use case", "fix a bug", "build the UI", "create an API endpoint", "write a page", or mentions Next.js implementation, App Router, server actions,

  • merge-queue

    Lands every branch that is ready, one at a time, when several agents have been working in parallel worktrees. Discovers the finished worktrees and the open pull requests, orders them so a dependency lands before what depends on it, and sends each through /merge-use-case under the merge lock. Use whe

  • merge-use-case

    Merges a finished work item branch into main through a serial merge gate. Rebases the worktree branch onto main, resolves any conflict, runs the full unfiltered regression suite, fast-forwards main, closes the GitHub issue, and removes the worktree. Works for a use case, a technical task, a bug, or

  • mutation-test

    Runs StrykerJS mutation testing on the business logic delivered for a use case to measure whether the unit tests actually detect broken behaviour, not just execute it. Reports the mutation score and every surviving mutant with the assertion that would kill it. Runs automatically inside /deliver-use-

  • onboard-existing-app

    Retrofits an existing Next.js codebase into the Nexa Agentic Engineering methodology by reverse-engineering a requirements catalog, entity model, use case diagram, and use case specs from the live code (and from BMAD-method artifacts under `_bmad/`, when present), then auditing cross-cutting infrast

  • playwright-test

    Creates Playwright browser-based end-to-end tests for Next.js pages covering complete user journeys from start to finish. Use when the user asks to "write Playwright tests", "create e2e tests", "write integration tests", "test in the browser", or mentions end-to-end testing, browser tests, UI integr

  • prisma-migration

    Creates Prisma schema models and generates database migrations from the entity model. Use when the user asks to "create a migration", "update the schema", "set up database tables", "write a Prisma migration", or mentions schema migration, DB migration, database versioning, or Prisma schema changes.

  • resolve-bug

    Orchestrates the full bugfix pipeline for a BUG-XXX or GitHub issue: an isolated tester reproduces the bug and updates the issue, a senior-dev agent writes a root-cause fix plan while a business-analyst agent links the affected requirement(s) in parallel, then the fix is implemented and gated on Def

  • setup-arch-unit

    Sets up arch-unit-ts architectural testing for a Next.js project. Detects the project layout, proposes a default rule set derived from the Next.js project structure conventions, asks the user to confirm or extend the rules, scaffolds the architecture spec, and installs a dedicated Husky pre-commit h

  • setup-env-profiles

    Sets up environment profiles (local, dev, test) with database connection strings and environment-specific configuration. Local uses Testcontainers, dev uses Supabase. Only prompts the user for the Supabase connection string. Use when the user asks to "set up environments", "configure profiles", "cre

  • setup-i18n

    Sets up server-side internationalization infrastructure for Next.js App Router using next-intl. Creates middleware locale detection, translation file structure, type-safe utilities, and routing configuration. Run before implementing use cases so that all feature code produces localized pages from th

  • setup-playwright-ci

    Generates a GitHub Actions workflow that runs Playwright end-to-end tests on every pull request. The workflow provisions a PostgreSQL database via Testcontainers, installs Chromium, runs the full E2E suite, and uploads trace artifacts on failure. Use when the user asks to "set up CI for Playwright",

  • setup-quality-ci

    Generates a GitHub Actions workflow that gates pull requests on code quality (oxlint, oxfmt) and test coverage (Vitest with v8 coverage thresholds). Use when the user asks to "set up CI for code quality", "enforce coverage in CI", "add quality gates", or mentions CI/CD for linting, formatting, or co

  • setup-web-middleware

    Builds the Next.js request interception layer with authentication, authorization, security headers, error tracking, and request context enrichment. Run before implementing use cases so that feature code can rely on cross-cutting infrastructure. Use when the user asks to "set up middleware", "add aut

  • vitest-test

    Creates Vitest integration tests for Next.js API route handlers, server actions, and components using Testcontainers for external dependencies. Use when the user asks to "write integration tests", "test with a real database", "create Vitest integration tests", or mentions Vitest integration testing

Subagents (6)

  • bug-analyst

    Independent senior-dev root-cause analyst. Reads a reproduced bug and the codebase, then posts a fix plan as a GitHub issue comment — never edits code. Follows bug-analyst's role in resolve-bug/SKILL.md as its binding operating manual.

  • bug-tester

    Independent bug reproduction tester. Follows a bug report's reproduction steps against the running application — via browser for UI bugs, via HTTP for API-only bugs — and reports a Reproducible / Not Reproducible / Insufficient Information verdict with evidence. For docs auto-created from a raw GitH

  • mutation-tester

    Independent mutation testing analyst for a delivered use case. Runs StrykerJS over the business logic delivered for the use case and reports the mutation score plus every surviving mutant with the assertion that would kill it. Never writes tests and never edits production code. Follows mutation-test

  • playwright-test

    Independent Playwright E2E test author for a single use case. Reads only the use case specification and frontend design — never implementation reasoning — so tests validate what was designed, not what was built. Follows playwright-test/SKILL.md as its binding operating manual.

  • requirement-linker

    Independent business-analyst agent. Cross-references a reproduced bug against docs/requirements.md and docs/use_cases/ to identify the affected requirement(s), links them into the bug report and the GitHub issue. Follows requirement-linker's role in resolve-bug/SKILL.md as its binding operating manu

  • use-case-archaeologist

    Independent reverse-engineering agent. Given one feature cluster (a set of routes/handlers, optionally seeded by a matching BMAD story), writes a single grounded UC-XXX spec cited to file:line, never invented. Writes only its own UC file — never touches shared docs. Follows use-case-archaeologist's

MCP servers (1)

  • playwright

    runs: npx @playwright/mcp@latest

View source on GitHub

More from nexadevapp/nexa-claude-skills-marketplace

All 4 plugins →

Nexa Agentic Engineering plugin for the Go stack (net/http, templ, htmx, sqlc, goose)

19 skills · 6 agents · 1 MCP server

6

Nexa Agentic Engineering stack-agnostic core SDLC methodology

16 skills · 1 agent · 1 MCP server · hooks

6

Nexa Agentic Engineering audit plugin: QA, requirements traceability, architecture, infrastructure, CI/CD, code metrics, test efficacy, and mutation audit reports for any repository

8 skills

6

Maintain nexa-claude-nextjs?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins4 plugins