← all publishers

nexadevapp

@nexadevapp source repo

Report this profile Claim this profile

• 54 skills
• 0 followers
• 15 hours ago last updated

1. ▌
   Software Engineering Report · nexadevapp

   Writes a dated software engineering report for the current repository and adds it as a new entry to docs/software-engineering-report.md. The report covers requirements traceability, quality assurance (the testing pyramid), architecture (existing documentation plus generated C4, 4+1, sequence, and ER diagrams in Mermaid), infrastructure, and CI/CD. Works on any repository and any tech stack. This skill must only be invoked explicitly via /software-engineering-report — never inferred from user messages.
   0 installs
2. ▌
   Audit · nexadevapp

   Runs a comprehensive implementation audit for a delivered use case in a Go web application. Checks Definition of Done, i18n completeness and correctness, error message i18n, accessibility, visual fidelity against the design, htmx loading/error/empty states, and E2E traceability. Run after /deliver-use-case or before /merge-use-case for a quality deep-dive. Use when the user asks to "audit UC-XXX", "run a quality audit", "check accessibility", "check translations", or mentions a deep quality review. Results are advisory — Critical and Major findings should be fixed; Minor findings are observations.
   0 installs
3. ▌
   Implement · nexadevapp

   Implements use cases and fixes bugs in a Go web application: sqlc queries, services, form validation, net/http handlers, templ views with htmx, and routes. Use when the user asks to "implement a use case", "fix a bug", "build the UI", "create an endpoint", "write a handler", "write a page", or mentions Go implementation, templ, htmx, sqlc, or full-stack Go implementation.
   0 installs
4. ▌
   Audit 2 · nexadevapp

   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-dive. Results are advisory — Critical and Major findings should be fixed; Minor findings are observations.
   0 installs
5. ▌
   Evaluate · nexadevapp

   Evaluates whether an implementation satisfies its use case specification and design artifact. Checks functional conformance, design conformance, and completeness with an independent perspective. Use when the user asks to "evaluate the implementation", "check if it matches the spec", "validate the work", or mentions evaluation, conformance check, or spec validation.
   0 installs
6. ▌
   Setup I18N · nexadevapp

   Sets up server-side internationalization for a Go web application with go-i18n: embedded TOML message catalogs, a locale detection middleware for net/http, context helpers that templ views call directly, and pluralization through CLDR rules. Run before implementing use cases so that every templ view and validation message is localized from the start. Use when the user asks to "set up i18n", "add internationalization", "add translations", "set up localization", "add multi-language support", or mentions i18n, internationalization, localization, go-i18n, or multi-language in a Go project.
   0 installs
7. ▌
   Dashboard · nexadevapp bundle

   Generates the project overview — a browsable page that shows every cluster, which of its use cases are delivered, and which are not, plus the technical tasks that support each cluster and the umbrella tasks that support the whole system. Each use case links to its specification, its design, and its acceptance tests. Use when the user asks to "update the dashboard", "generate the overview", "show project status", "what is delivered", "regenerate the report", or mentions the project dashboard, delivery status, or a stakeholder report.
   0 installs
8. ▌
   Merge Queue · nexadevapp

   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 when the user asks to "merge the queue", "land everything that is ready", "merge the open PRs", "drain the merge queue", or when several use cases or clusters were delivered by different agents at the same time.
   0 installs
9. ▌
   Resolve Bug · nexadevapp

   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 Definition of Done. Use when the user asks to "fix this bug", "resolve BUG-XXX", "run the bugfix pipeline", pastes a GitHub issue link and asks to fix it, or mentions an end-to-end bug resolution workflow.
   0 installs
10. ▌
    Report Bug · nexadevapp bundle

    Creates structured bug report documents with reproduction steps, expected vs actual behavior, and severity classification. Use when the user asks to "report a bug", "file a bug", "document a defect", "log an issue", or mentions a bug, defect, regression, or unexpected behavior that needs to be tracked.
    0 installs
11. ▌
    Code Quality · nexadevapp

    Runs golangci-lint v2 on Go files to fix lint errors, enforce a cyclomatic complexity limit with gocyclo, and apply consistent formatting with gofumpt and goimports; formats templ files with templ fmt. Use when the user asks to "lint", "format code", "run code quality checks", "run golangci-lint", or mentions code quality, formatting, gofmt, or static analysis in a Go project.
    0 installs
12. ▌
    DB Migration · nexadevapp

    Creates goose SQL migrations and sqlc queries from the entity model, then regenerates the type-safe Go database code. Use when the user asks to "create a migration", "update the schema", "set up database tables", "write a goose migration", "add sqlc queries", or mentions schema migration, DB migration, database versioning, goose, or sqlc.
    0 installs
13. ▌
    Code Review · nexadevapp

    Reviews code changes for quality, correctness, security, and maintainability with an independent perspective. Use when the user asks to "review the code", "check my changes", "review the implementation", or mentions code review, PR review, or quality check.
    0 installs
14. ▌
    Nexa Skills · nexadevapp

    Discovers and invokes Nexa skills. Use when starting a session or to identify which skill is appropriate for the task at hand. This is the orchestrator skill which governs how all Nexa skills are discovered and invoked.
    0 installs
15. ▌
    Mutation Test · nexadevapp

    Runs gremlins mutation testing on the Go business logic delivered for a use case to measure whether the unit tests actually detect broken behaviour, not just execute it. Reports the test efficacy and every surviving mutant with the assertion that would kill it. Runs automatically inside /deliver-use-case right after implementation, before the E2E gate; can also be invoked directly. Use when the user asks to "run mutation testing", "check test quality", "run gremlins", "are my tests actually testing anything", or mentions mutation score, test efficacy, or surviving mutants.
    0 installs
16. ▌
    Implement 2 · nexadevapp

    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, or full-stack implementation.
    0 installs
17. ▌
    Entity Model · nexadevapp

    Creates entity model documents with Mermaid.js ER diagrams and attribute tables defining entities, relationships, data types, and validation rules. Use when the user asks to "create an entity model", "design a data model", "draw an ERD", "define database schema", "model entities", or mentions entity-relationship diagram, ER diagram, database design, or data modeling.
    0 installs
18. ▌
    Requirements · nexadevapp bundle

    Gathers, organizes, and documents software requirements into structured catalogs with functional requirements (user stories), non-functional requirements (measurable quality attributes), and constraints. Use when the user asks to "write requirements", "create a PRD", "gather requirements", "document feature specs", "write user stories", "define NFRs", "list constraints", or mentions requirements catalog, requirements analysis, product requirements document, or feature specification.
    0 installs
19. ▌
    Merge Use Case · nexadevapp

    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 a change request. Use when the user asks to "merge the use case", "land the branch", "run the merge gate", "merge UC-XXX", or mentions the merge queue. Invoked by /deliver-cluster after every pipeline that finishes green.
    0 installs
20. ▌
    Setup I18N 2 · nexadevapp

    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 the start. Use when the user asks to "set up i18n", "add internationalization", "add translations", "set up localization", "add multi-language support", or mentions i18n, internationalization, localization, or multi-language.
    0 installs
21. ▌
    Use Case Spec · nexadevapp bundle

    Creates detailed use case specification documents with actors, preconditions, main success scenarios, alternative flows, postconditions, and business rules. Use when the user asks to "write a use case", "specify a use case", "document system behavior", "define scenarios", "write a functional spec", or mentions use case specification, acceptance criteria, or user scenarios.
    0 installs
22. ▌
    Deliver Cluster · nexadevapp

    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. Use when the user asks to "deliver a cluster", "deliver the use cases", "start delivery", "build the next cluster", or mentions parallel delivery, the delivery queue, or delivering several use cases at once.
    0 installs
23. ▌
    Playwright Test · nexadevapp bundle

    Creates browser-based end-to-end tests for a Go web application (templ + htmx) with Playwright for Go, covering complete user journeys from start to finish. The tests are Go tests behind the `e2e` build tag and run with `go test`. Use when the user asks to "write Playwright tests", "create e2e tests", "test in the browser", or mentions end-to-end testing, browser tests, UI integration tests, or Playwright for a Go app.
    0 installs
24. ▌
    Setup Arch Unit · nexadevapp

    Sets up architecture rules for a Go project with the depguard and forbidigo linters of golangci-lint v2. Detects the package layout, proposes a default rule set derived from the Nexa Go conventions (no database access outside sqlc in feature code, no HTTP or templ in services, only internal/config reads the environment, shared packages never import features), asks the user to confirm or extend it, writes the rules into .golangci.yml, and installs a git pre-commit hook that runs them before every commit. Use when the user asks to "set up arch-unit", "add architecture tests", "enforce module boundaries", "enforce package boundaries", "add an architecture lint", or mentions ArchUnit, depguard, import rules, dependency rules between packages, or layered / hexagonal architecture enforcement in Go.
    0 installs
25. ▌
    Resolve Bug 2 · nexadevapp

    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 Definition of Done. Use when the user asks to "fix this bug", "resolve BUG-XXX", "run the bugfix pipeline", pastes a GitHub issue link and asks to fix it, or mentions an end-to-end bug resolution workflow.
    0 installs
26. ▌
    Vitest Test · nexadevapp bundle

    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 or Testcontainers. Unit tests are created by the implement skill.
    0 installs
27. ▌
    Change Request · nexadevapp bundle

    Creates structured change request documents for intentional modifications to already-implemented use cases. Use when the user asks to "create a change request", "log a CR", "document a change", or describes a stakeholder-requested modification to existing behavior (e.g., renaming a field, changing validation rules, restructuring data). A change request always references exactly one use case and describes only the delta — the original use case remains immutable.
    0 installs
28. ▌
    Design Screens · nexadevapp bundle

    Creates screen design specifications as standalone HTML artifacts from the project wireframe. Uses Playwright to open the wireframe, identify the section relevant to the current use case, and produces a self-contained HTML design file faithful to the wireframe's layout and enriched with states, data mappings, and interactions from the use case specification. Uses a separated CSS theming approach — HTML references a theme switcher CSS file and a Tailwind config, so changing the theme across all designs requires only swapping CSS files. Use when the user asks to "design a screen", "create a wireframe", "define the UI", "design the frontend", or mentions screen design, wireframes, UI layout, or frontend design.
    0 installs
29. ▌
    Technical Task · nexadevapp bundle

    Creates technical task specification documents for engineering work that has no user-facing scenario: configuration, cleanup, dependency updates, infrastructure, and developer experience improvements. Use when the user asks to "create a technical task", "set up the database", "bump a dependency", "add a dev profile", "clean up code", or mentions infrastructure tasks, configuration changes, or maintenance work.
    0 installs
30. ▌
    Deliver Use Case · nexadevapp

    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-requirements first, and delivery runs in its own git worktree on a uc/UC-XXX branch. This skill must only be invoked explicitly via /deliver-use-case or by /deliver-cluster — never inferred from user messages.
    0 installs
31. ▌
    Integration Test · nexadevapp bundle

    Creates Go integration tests for net/http handlers, services, and sqlc queries against a real PostgreSQL database started with testcontainers-go. Use when the user asks to "write integration tests", "test with a real database", "create Go integration tests", or mentions Go integration testing, testcontainers-go, or database-backed tests. Unit tests are created by the implement skill.
    0 installs
32. ▌
    Setup Quality CI · nexadevapp bundle

    Generates a GitHub Actions workflow that gates pull requests on Go code quality (golangci-lint, gofumpt/goimports and templ formatting, generated-code drift for sqlc and templ) and test coverage (go test with integration tests and an 80% threshold). Use when the user asks to "set up CI for code quality", "enforce coverage in CI", "add quality gates", "run golangci-lint in CI", or mentions CI/CD for linting, formatting, or coverage in a Go project.
    0 installs
33. ▌
    Code Quality 2 · nexadevapp

    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.
    0 installs
34. ▌
    Mutation Test 2 · nexadevapp bundle

    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-case right after implementation, before the E2E gate; can also be invoked directly. Use when the user asks to "run mutation testing", "check test quality", "run Stryker", "are my tests actually testing anything", or mentions mutation score or surviving mutants.
    0 installs
35. ▌
    Use Case Diagram · nexadevapp

    Creates or updates PlantUML use case diagrams defining actors, use cases, and their relationships from requirements. Use when the user asks to "create a use case diagram", "draw a UML diagram", "map actors to use cases", "generate a .puml file", or mentions PlantUML, use case overview, actor diagram, or system use cases.
    0 installs
36. ▌
    Setup Env Profiles · nexadevapp bundle

    Sets up environment profiles (local, dev) for a Go project with database connection strings and environment-specific configuration, and scaffolds the config loader and the `cmd/dev` entry point. Local uses Testcontainers, dev uses Supabase. Only prompts the user for the Supabase connection strings. Use when the user asks to "set up environments", "configure profiles", "create .env files", "set up local/dev", or mentions environment profiles, environment configuration, or database connection setup.
    0 installs
37. ▌
    Merge Use Case 2 · nexadevapp

    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 a change request. Use when the user asks to "merge the use case", "land the branch", "run the merge gate", "merge UC-XXX", or mentions the merge queue. Invoked by /deliver-cluster after every pipeline that finishes green.
    0 installs
38. ▌
    Setup Playwright CI · nexadevapp bundle

    Generates a GitHub Actions workflow that runs the Playwright for Go end-to-end tests of a Go application on every pull request. The workflow sets up Go, installs Chromium through the pinned `go tool playwright`, runs `go test -tags=e2e` (which provisions PostgreSQL via Testcontainers), and uploads trace artifacts on failure. Use when the user asks to "set up CI for Playwright", "run e2e tests in CI", "add a GitHub Actions workflow for Playwright", or mentions CI/CD for end-to-end tests.
    0 installs
39. ▌
    Deliver Cluster 2 · nexadevapp

    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. Use when the user asks to "deliver a cluster", "deliver the use cases", "start delivery", "build the next cluster", or mentions parallel delivery, the delivery queue, or delivering several use cases at once.
    0 installs
40. ▌
    Playwright Test 2 · nexadevapp bundle

    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 integration tests, or Playwright for Next.js.
    0 installs
41. ▌
    Setup Arch Unit 2 · nexadevapp bundle

    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 hook that runs the rules before every commit. Use when the user asks to "set up arch-unit", "add architecture tests", "enforce module boundaries", "set up arch-unit-ts", "add an architecture lint", or mentions arch-unit, ArchUnit, architectural rules, dependency rules between modules, layered architecture enforcement, or hexagonal architecture testing in TypeScript.
    0 installs
42. ▌
    Generate Wireframe · nexadevapp bundle

    Generates a high-quality wireframe as a single-page HTML file showing all screens, their spatial layout, and navigation flow. The wireframe establishes screen structure, component placement, and information hierarchy with production-grade visual design powered by the frontend-design skill. Supports incremental updates: new screens can be added without destroying existing sections. Use when the user asks to "create a wireframe", "generate a wireframe", "sketch the screens", "layout the UI", or mentions wireframe, screen layout, UI skeleton, or low-fidelity mockup.
    0 installs
43. ▌
    Onboard Existing App · nexadevapp

    Retrofits an existing Go web application 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 (routes, handlers, views, services, SQL migrations, and queries), and from BMAD-method artifacts under `_bmad/`, when present. Then audits cross-cutting infrastructure and creates thin-pointer GitHub issues for already-shipped work. Use when the user asks to "onboard this codebase", "onboard this Go app", "onboard an existing app", "retrofit Nexa onto my project", "adopt the Nexa pipeline for an existing Go app", "reverse-engineer requirements from code", or mentions bringing a brownfield or already-built Go project under Nexa/`/deliver-use-case`/`/resolve-bug` for future work.
    0 installs
44. ▌
    Setup Web Middleware · nexadevapp

    Builds the Go net/http middleware chain with authentication, authorization (RBAC), CSRF protection, security headers, structured slog logging, and panic recovery. 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 auth middleware", "build the middleware layer", "add security headers", "protect my routes", "add login redirect", "set up route guards", or mentions middleware, authentication guard, route protection, CSRF, or RBAC middleware.
    0 installs
45. ▌
    Deliver Use Case 2 · nexadevapp

    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-requirements first, and delivery runs in its own git worktree on a uc/UC-XXX branch. This skill must only be invoked explicitly via /deliver-use-case or by /deliver-cluster — never inferred from user messages.
    0 installs
46. ▌
    Prisma Migration · nexadevapp

    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.
    0 installs
47. ▌
    Setup Quality CI 2 · nexadevapp bundle

    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 coverage.
    0 installs
48. ▌
    Conventional Commit · nexadevapp

    Writes every git commit message in Conventional Commits v1.0.0 format with an ASD-STE100 Simplified Technical English subject line. Use before running any `git commit`, `git commit --amend`, or `gh pr merge --squash`, and whenever the user asks to "commit", "commit the changes", "write a commit message", "amend the commit", or mentions commit conventions, commit format, or commit message style. Applies in any git repository, Nexa project or not.
    0 installs
49. ▌
    Setup Project Rules · nexadevapp

    Writes Nexa workflow enforcement rules into the target project's CLAUDE.md to prevent the AI agent from bypassing the methodology. Ensures the agent never skips the requirements-to-spec pipeline, never proposes jumping straight to implementation, always checks for duplicate use cases, and always uses the next available use case number. Run once at project inception; re-run if rules need updating. Use when the user asks to "set up project rules", "enforce workflow rules", "configure CLAUDE.md rules", "add Nexa rules to the project", or mentions project rules, workflow enforcement, or CLAUDE.md setup.
    0 installs
50. ▌
    Setup Env Profiles 2 · nexadevapp

    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", "create .env files", "set up local/dev", or mentions environment profiles, environment configuration, or database connection setup.
    0 installs
51. ▌
    Engineer Requirements · nexadevapp

    Lead Requirements Engineer that systematically elaborates all use cases through structured analysis, probing questions, and iterative refinement. Processes use cases in thematic clusters, applies CRUD matrix analysis, actor-goal completeness, exception path probing, MoSCoW prioritization, and traceability checks. Spawns a Product Owner sub-agent to answer clarification questions — only genuinely ambiguous decisions reach the human. Updates requirements, entity model, and use case diagram as living documents. Use when the user asks to "engineer requirements", "elaborate use cases", "analyze use cases", "validate use case completeness", "deep-dive on requirements", "prioritize requirements", or mentions requirements engineering, use case elaboration, MoSCoW, or completeness analysis.
    0 installs
52. ▌
    Setup Playwright CI 2 · nexadevapp bundle

    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", "run e2e tests in CI", "add a GitHub Actions workflow for Playwright", or mentions CI/CD for end-to-end tests.
    0 installs
53. ▌
    Onboard Existing App 2 · nexadevapp

    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 infrastructure and creating thin-pointer GitHub issues for already-shipped work. Use when the user asks to "onboard this codebase", "onboard an existing app", "retrofit Nexa onto my project", "adopt the Nexa pipeline for an existing Next.js app", "reverse-engineer requirements from code", or mentions bringing a brownfield or already-built Next.js project under Nexa/`/deliver-use-case`/`/resolve-bug` for future work.
    0 installs
54. ▌
    Setup Web Middleware 2 · nexadevapp

    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 auth middleware", "build the middleware layer", "add security headers", "protect my routes", "add login redirect", "secure my API routes", "set up route guards", or mentions middleware, authentication guard, route protection, or RBAC middleware.
    0 installs