nerviz

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

Architecture
skill · class design · opus

cache-architect

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

skill · designopuswrites 22-cache.mdonly inside docs/use-cases/UC-*/**
§ the file it writes

22-cache.md, block by block

bank-app has no 22-cache.md yet. These are the blocks SKILL.md says the partial contains.

## 1 · Cached reads

One row per read, every column of step 5

## 2 · Provider

The provider, the matrix row that chose it, the rejected ones in one line each, transaction awareness, and whether it was inherited

## 3 · Expiry and size

Per cache: expiry next to its tolerance, maximum size, jitter, refresh ahead

## 4 · Invalidation

Every writer of the cached data, its path, its eviction, its staleness bound

## 5 · Failure and load

Error handler, client timeout, what the source does without the cache

## 6 · Serialization

Per cache: serializer and format version (Redis); none for a local cache of immutable records

## 7 · Observability

Metric names, and the alarm each one exists for

## 8 · Declared dependencies

Coordinates, version empty when managed

## 9 · Configuration

Every property the cache reads, its value, and which partial owns the value

## 10 · Deferred

Same shape as every partial. none when nothing was deferred

## Compose services

The redis row, or none for a local cache

## Design patterns

The Decorator over each port, with its classes — step 9b

§ behavior

What it reads, writes and refuses

The skill's own contract, from SKILL.md, in the original wording.

Class

design — the territory is skill_classes.design in @.claude/schemas/extensions.json, and ArchHook.java guard enforces it. Writes inside the use case folder and nothing else.

Reads

docs/use-cases/UC-NNN-<slug>/00-use-case.md (mandatory), 10-domain.md (mandatory), 20-persistence.md, 28-http-client.md and 35-jobs.md (when present), the Components tables and 22-cache.md of earlier cases, pom.xml, docker-compose.yml, the active blueprint's packages.map, @.claude/rules/caching.md, @.claude/rules/architecture-ddd.md, @.claude/rules/observability.md, @.claude/rules/secrets.md, @.claude/skills/docker-architect/references/compose-service-decision.md, and this skill's references/.

Writes

docs/use-cases/UC-NNN-<slug>/22-cache.md. Nothing else.

Owns

which reads are cached and the key of each, the cache provider of the project, expiry and size per cache, the list of writers that must evict, failure and load handling of the cache, the cache serialization and format version, cache metrics, and the redis compose row.

Does not decide

the freshness tolerance (00-use-case.md), the port or the record it returns (10-domain.md), the query or the call behind the port (20-persistence.md, 28-http-client.md), the replica count when a partial already recorded it, or the tests (40-tests.md). Does not write Java, pom.xml, application.yml or docker-compose.yml — the executor and docker-architect do, from this partial. Doesn't touch .claude/rules/**.

Source: SKILL.md § Contract, at nerviz e4cae27.

§ guard and hook

What the guard does with it

design is the skill's class. ArchHook opens a phase when the skill is called and checks every write against the class's territory. The text on the right is the hook's own.

write_allow of class design

  • ✓docs/use-cases/UC-*/**
  • ✓docs/use-cases/BACKLOG.md
  • src/**: migrations and classes are the executor's
  • docker-compose.yml: another class's file
  • a use case already approved: its specs are frozen

A refusal exits with code 2 and the message goes back to the model.

PreToolUse  Skill(cache-architect)
  audit call                       exit 0
  guard call                       exit 0
# a skill of another class replaces the phase
# write_allow: docs/use-cases/UC-*/**, docs/use-cases/BACKLOG.md
§ orchestration

Where it sits on the rail

Each card is a step of /new-feature; the arrow carries the partial one step hands to the next. Dashed steps run only when the use case needs them.

/new-feature orchestrator · opus
/new-feature-implement Who reads the partial next

After approval, /new-feature-implement has the executor build the code. The spec is consolidated by reference and wins where it and a partial disagree; the partial is read, by section, for detail.

22-cache.mddocs/use-cases/UC-NNN-…/
read by section, for detail
java-spring-boot-developeragent · executor
writes the code
src/**designs one use case into a spec, writes no code
← back to the chains