nexa-claude-core

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

Skills (16)

• change-request

  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 v

• code-review

  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.

• conventional-commit

  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 mess

• dashboard

  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

• design-screens

  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

• engineer-requirements

  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 tracea

• entity-model

  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

• evaluate

  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 wo

• generate-wireframe

  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

• nexa-skills

  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.

• report-bug

  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 track

• requirements

  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

• setup-project-rules

  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 use

• technical-task

  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", "a

• use-case-diagram

  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

• use-case-spec

  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",

Subagents (1)

• evaluate

  Independent QA evaluator that compares an implementation against its use case specification and design artifact. Has not seen the implementation process and must not assume passing tests imply conformance. Follows evaluate/SKILL.md as its binding operating manual.

MCP servers (1)

• context7

  connects to: https://mcp.context7.com/mcp

Hooks (1)

• SessionStart

  bash ${CLAUDE_PLUGIN_ROOT}/hooks/session-start.sh