Claude Skills by ice-lfernandes

Diagnoses the AI setup and architecture enforcement on this machine: active hooks, loaded boundary rules, Maven wrapper, `java` on PATH. Explicit invocation only.

Reads the execution trail the `audit` hook writes into `.claude/audit-usage/` and consolidates it across runs — spend per skill and agent, duration, failure rate, permissions granted, and which report to open next. Answers "what has this project cost me so far", which no single report answers. Explicit invocation only.

Decides which Claude Code extension resolves a scenario — auto-invocable skill, manually-invoked skill, subagent, rule in `rules/`, `CLAUDE.md` section, or MCP server connecting to an external system — and writes the files only after approval. Interviews first, proposes scored options with sources, writes afterward. Explicit invocation only.

Extends a project's docker-compose.yml and Dockerfile after project-bootstrap's base generation — adds the database or messaging service a modeled use case needs, keeps the compose-side image tag consistent with the one test-architect pins in TestcontainersConfiguration.java, and syncs with 20-persistencia.md / 40-testes.md. Use when the request involves adding a service to docker-compose, containerizing a new dependency, configuring Testcontainers at the compose level, or "docker-compose is ...

Details the domain and application layer of an already-designed use case — aggregate, value objects, invariants, ports, and events — into the `10-dominio.md` partial. Use when the request involves modeling the domain, defining an aggregate or value object, designing a use case's ports, or detailing a spec already created by `use-case-design`. Piece of the `/new-feature` pipeline: requires `00-caso-de-uso.md` in the given folder and stops without it.

Offers to git init/commit the current project and, optionally, create a GitHub repo (via `gh`) and push — always behind two explicit confirmations, one for the local commit and one for the remote create+push. Use right after a project was just generated by `/init-project`, right after `java-spring-boot-developer` reports a feature implemented successfully, when `/new-feature` ends with an approved spec, or whenever the user asks to create a git repo, commit, or push the current project.

Initializes a Spring Boot project from scratch with a selectable architecture. Manual ritual — interview, validate the blueprint, generate the structure, install the hooks and verify the build. Explicit invocation only.

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.

Designs the Kafka producer/consumer adapter for an already-modeled domain event — topic, partition key, serialization, consumer group, delivery semantics, retries and DLQ — into the `25-mensageria.md` partial. Use when the request involves publishing a domain event to Kafka, consuming a Kafka topic, designing a producer or consumer adapter, deciding topic/partition/serialization, or wiring retry/DLQ for a message listener. Piece of the `/new-feature` pipeline: requires `10-dominio.md` in the ...

Orchestrates the feature pipeline — one use case per run, 5 design skills → spec.md for the executor

Designs the persistence layer of an already-modeled use case — tables, aggregate mapping, migrations, queries, indexes, and datasource configuration — into the `20-persistencia.md` partial. Use when the request involves modeling the database, mapping an aggregate to JPA, writing or reviewing migrations, deciding indexes and keys, diagnosing N+1 or slow queries, or tuning the pool and datasource properties. Piece of the `/new-feature` pipeline: requires `10-dominio.md` in the given folder and ...

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 the inbound REST adapter for an already-modeled use case — endpoints, DTOs, status codes, error map, pagination, idempotency, and OpenAPI — into the `30-rest.md` partial. Use when the request involves exposing a use case via HTTP, designing an endpoint or controller, deciding status and error body, paginating a collection, applying `Idempotency-Key`, or fixing the OpenAPI contract. Piece of the `/new-feature` pipeline: requires `10-dominio.md` in the given folder and stops without it.

Designs the tests for an already-modeled use case — what test exists at what level, what data, what error cases — into the `40-testes.md` partial, and installs the architecture tests in a project that doesn't yet have them. Use when the request involves writing or designing tests, coverage, ArchUnit, boundary tests, integration tests, or "this is missing tests". Piece of the `/new-feature` pipeline: in design mode requires `10-dominio.md` in the given folder and stops without it.

Delimits a use case's boundary and emits the parent spec that the layer skills detail — trigger, payload, response, side effects, invariants, errors, and canonical names. Use when the request involves "new use case", "design before implementing", "implementation spec", a new endpoint/event/job, or when a request bundles several actions and it's necessary to know whether it's one use case or several. First piece of the `/new-feature` pipeline.