Project skills and specifications

Project skills are stored in generated/skills/; specifications belong in landscape.
For code reviews, read and follow generated/skills/code-review/SKILL.md. If no dedicated Skill tool is available, load the file directly.
Use grill-me only when the user explicitly requests it, for example Use grill-me to review this plan or Gebruik grill-me voor dit ontwerp.
Before using it, read generated/skills/grill-me/SKILL.md and its dependency generated/skills/grilling/SKILL.md. If no dedicated Skill tool is available, load these files directly and follow their instructions within the available tools.
Installing or mentioning a skill does not start an interview. Do not apply grilling automatically to ordinary development requests.
Keep the upstream skill files unchanged. Source revision and license are recorded in generated/skills/upstream.json and generated/skills/LICENSE.mattpocock.

Backend changes and reviews

Before changing backend Java, read CODING_STANDARDS.md.
For reviews, use generated/skills/code-review/SKILL.md together with docs/backend-review.md. Keep upstream skills unchanged.
Obtain maintainer agreement before adding any standards waiver; record its narrow scope and reason alongside the affected code or configuration.

Read current landscape guidance, including applicable ADRs and specifications. This repository owns its implementation.
Engineering resources are pinned by engineering.lock.json. Do not edit generated/; change engineering and deliberately adopt a released version.
Regenerate with mvn -N -Pregenerate-engineering validate; check with python3 scripts/engineering.py --check. No sibling checkout is needed.