↑ ↓ to move · Enter to open · Esc to closeTap a result

Back to Architecture
§ architecture · skills and agents

Every skill and every agent

A generated project ships 32 skills and 7 agents. Each has a page of its own: what it reads and writes, what the guard does with it, and where it sits on the chains. This page is the way in.

Skills

19 skills in two groups: the design skills of /new-feature, and the pieces of /init-project with /git-publish.

design · /new-feature 13

use-case-design

Turns a request into one use case: its boundary, flow and canonical names.

opus
domain-modeling

Models the aggregate, its invariants, ports and events from the use case.

opus
rest-api-architect

Designs the HTTP contract: endpoints, DTOs, error map, pagination, idempotency and versioning.

opus
graphql-api-architect

Designs the GraphQL adapter: schema, inputs and payloads, connections, batch loads and the error map.

opus
security-architect

Designs who may call what: the mechanism, authorities, the filter chain and the failure responses.

opus
http-client-architect

Designs the outbound HTTP adapter: client, pool, timeouts, retry, resilience and outbound authentication.

opus
ai-architect

Designs the AI ports: the model or vector store, prompts, the answer type, data sent and failure families.

opus
search-architect

Designs the search index as a rebuildable projection: mapping, queries, writes, rebuild and lag.

opus
messaging-architect

Designs the Kafka adapters: topic, partition key, delivery, consumer idempotency, retry and DLQ.

opus
jobs-architect

Designs the scheduled and background jobs: technology, coordination across instances and execution guarantees.

opus
persistence-architect

Designs how the aggregate reaches disk and comes back: schema, mapping, adapters and migrations.

opus
cache-architect

Designs the application cache as a decorator of a port: keys, provider, expiry, invalidation and failure.

opus
test-architect

Designs the tests: what is tested at which level, the data, the doubles and the coverage gaps.

opus

/init-project and /git-publish 6

Commands and tools

13 skills that sit on neither chain.

new-feature

Orchestrates the design of a feature: one use case per run, the design skills in order, to an approved spec the executor can build.

opus
new-feature-implement

Implements one approved spec: a setup pre-flight, then the executor in three chained block groups, then it prints the git-publish command.

sonnet
arch-adopt

Installs or updates this architecture's .claude/ in a Java project that /init-project did not generate: norms, skills, agents, the hook and its schema.

opus
platform-upgrade

Takes a Maven or Gradle project on a Spring Boot line below the floor up to it, and leaves the build green and the diff uncommitted.

opus
new-project

Prepares a new project's generation without a clone: fetches the source at its latest tag, records the ref and commit, and hands over to /init-project.

sonnet
project-config

Shows and changes what a project configures in its own .claude/, through ArchHook.jar config, the only writer.

sonnet
arch-doctor

Diagnoses the setup on this machine: hooks, boundary rules, the build wrapper, java, which .claude/ the project came from, and whether the compose stack runs.

sonnet
audit-usage

Reads the execution trail across runs: billable tokens per skill and agent, duration, failures, permissions, and which report to open next.

sonnet
report-issue

Files an issue on the Nerviz repository from inside a generated project, from a description or a lessons-learned file, and refuses a report with no evidence a maintainer can verify.

opus
triage-issue

Triages one issue skeptically: every claim goes to the read-only issue-verifier, and a verdict is posted only after you confirm.

sonnet
sonar-lessons

Runs the project's SonarQube analysis, traces every group of findings to the norm or setting that produced it, and writes a lessons file.

opus
gof-design-patterns

Chooses and implements a design pattern in Java and Spring from the symptom that justifies it.

opus
claude-code-architect-designer

Decides which Claude Code extension resolves a scenario (skill, subagent, rule, hook, MCP server, permission or mod) and writes the files only after you approve.

opus