`/spike <slug>` creates `../<project>-spike-<slug>` on branch `spike/<slug>` and reduces that worktree's `.claude/settings.json` to the hooks `spike.keep_modes` lists. The main checkout never relaxes, and this session stays enforced; the person opens `claude` in the worktree.

- **Date:** 2026-09-10 - **Scenario:** Criar skill responsável por dockerização/containerização. Docker e docker-compose básicos nascem no `project-bootstrap`; extensões (serviço de DB, config de Testcontainers) acontecem depois, disparadas por skills do `/new-feature` quando necessário. -

- **Date:** 2026-09-11 - **Scenario:** "Finalize the skill documented to be created (`messaging-adapter`) — messaging protocols are plural (Kafka, RabbitMQ, SNS, SQS, JMS); decide whether to build one generic skill dispatching to per-tech skills, or one skill per technology; and clarify how broker

- **Date:** 2026-09-30 - **Scenario:** "quero adicionar uma nova skill para ser injetada no agent java-spring-boot-developer de boas praticas de codigos java baseado em regras do sonarqube" — revised mid-interview to: "na verdade nao há configuracao de sonarqube para avaliacao real. Ao invés de

- **Date:** 2026-09-30 - **Scenario:** "quero criar uma skill que é executada a partir do projeto gerado que: 1. rodar sonar 2. extrai relatorio de bugs, issues, duplicacao, cobertura de codigo 3. baseado nas regras do projeto descritas no .claude, gera um arquivo lessons-learning como foco em melh

- **Date:** 2026-10-02 - **Scenario:** "quero criar uma nova skill de conhecimento de codigo para aplicar quando pedido em uma new feature a parte de seguranca com apis rests (spring-security). Se durante entrevista de caso de uso for mencionado ou perguntado por seguranca da api, roles, apenas grup

- **Date:** 2026-10-05 - **Scenario:** "Criar o http-client-architect: skill de design do adapter HTTP de saída (cliente REST) de um caso de uso já modelado, no pipeline /new-feature depois de domain-modeling declarar o port de saída e antes de test-architect. Inclui as famílias de erro de infra

- **Date:** 2026-10-13 - **Scenario:** "Criar a skill de design graphql-api-architect: partial 31-graphql.md, par do 30-rest.md do rest-api-architect — o adapter de entrada GraphQL de um caso de uso já modelado, sobre Spring for GraphQL no stack servlet, schema-first, @Controller com @QueryMappin

Pulls this architecture into the project the session is rooted at. One operation, two starting states: the project has no `.claude/` of this shape yet (install), or it has one and is behind (update). The difference is the provenance stamp, not a different command.

Keeps `docker-compose.yml` and `Dockerfile` in sync with what the project actually needs, **after** they're born. `project-bootstrap` writes the base pair — one `app` service, nothing else — at project creation. Every service added afterward (Postgres, MySQL, a broker) goes through this skill, s

Chooses and implements a design pattern in Java/Spring from the symptom that justifies it. Use when the request involves a design pattern, Strategy, Factory, Decorator, Builder, Specification, "how to structure this class", a growing if/switch chain, or refactoring a class with too many responsibilities.

Creates the complete initial structure of a Spring Boot project from a declarative architecture blueprint. Use when the user asks to create a project from scratch, start a new project, set up a project, scaffolding, "new Spring project", bootstrap, generate a module structure, create a multi-module Maven or Gradle project, build a hexagonal architecture, clean architecture, onion, layered, vertical slice or modular monolith, or when the /init-project command is run.

Designs **how the use case is exposed over HTTP**: what endpoints exist, what DTOs go in and out, what status each result returns, what error body arises from each domain exception, how the collection is paginated, and what OpenAPI has to document. What `domain-modeling` left as an inbound port, thi

Designs **who may call each endpoint and how the caller proves who it is**: the authentication mechanism of the project, the request rules and method-security annotations of each endpoint, the claims-to-authorities mapping, the ownership check a use case runs, and what the API answers when the proof

Runs this project's SonarQube analysis, extracts the quality gate, bugs, vulnerabilities, code smells, duplication and coverage through the SonarQube Web API, traces every group of findings to the norm, template or Checkstyle setting in `.claude/` that produced it, and writes `docs/lessons-learned/sonar-NNN.md` focused on fixing the cause so the next analysis has fewer issues or none. Ends with the `/report-issue` command that files it on the Nerviz repository, where the fix belongs. Explicit invocation only.

Two things, and the argument decides which: