jardis-start-herelisted

## Scope This skill has one job: orientation. It does not teach any phase itself — every phase links to the skill that does. Read this first in a fresh Jardis project, or whenever you are unsure which skill answers the question in front of you. It stretches slightly past a pure cross-cutting concern (it also names two concrete CLI commands), because a master entry point that cannot say "run this" is not actually an entry point — the alternative (a second, thinner skill just for that) would only fragment the routing table this skill exists to provide. ### 1. The four phases 1. **Discover** — before hand-building any infrastructure piece (cache, queue, HTTP client, validation, …), check whether a Jardis package already covers it. → `jardis-catalog`. 2. **Schema** — model the domain's tables from a plain-text idea, or introspect an existing database. → `schema-authoring`. 3. **Design** — draw Aggregates and Processes in the Jardis Designer (`jardis ui`). The same tool also carries the strategic layer: Domain/Subdomain structure with Core/Supporting/Generic classification, a per-BC Ubiquitous-Language glossary and canvas ("Steckbrief"), planned (not-yet-built) BCs, and a per-Domain Context Map with the eight canonical DDD relationship patterns — including an on-demand Abgleich-Sicht (reconcile lens) that checks the declared boundaries against the real coupling of the built system. This is click-work in the browser; there is deliberately no dedicated AI