# Project skills and specifications

- Project skills are stored in `skills/`; specifications belong in `specs/`.
- For code reviews, read and follow `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 `skills/grill-me/SKILL.md` and its dependency
  `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 `skills/upstream.json` and `skills/LICENSE.mattpocock`.

# Backend changes and reviews

- Before changing backend Java, read `CODING_STANDARDS.md`.
- For reviews, use `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.