jardis-mcp-consumerlisted

## Scope This skill is the headless twin of driving the Jardis Designer by hand. There is deliberately no "Designer-Companion" persona in this bundle (`docs/SKILL-FORMAT.md` §3a) — an AI that drives `jardis mcp` end to end is doing that companion's job through a different transport. It keeps the `post-active`/`C` label deliberately: the moment `build` succeeds, this same AI is already the Persona-C implementer that `platform-implementation` addresses next. The stretch is the transport (MCP calls instead of UI clicks), not the phase. ### 1. The surface: Tools act, Resources read `jardis mcp` exposes two primitive kinds, both stateless per call (no server-side session): - **Tools** perform an action (create, save, validate, build) and return a result or a structured error envelope (§6). - **Resources** (plain or templated, e.g. `jardis://tree`, `jardis://schema/{domain}/{bc}`) are read-only projections of the current on-disk state — call them again after a write to see the effect, there is no push/subscribe. The full catalogue (on the order of 60 tools plus 50+ resources/templates — do not hardcode them from memory, they grow with every strategic-design increment; how the count is pinned and kept honest: [[beschreibt-bauweise-von::builder-mcp-bauweise]] §9, mirrored in `INVENTAR.md`'s Budget-Tracking section) is a lived artefact, not something to memorise here — consult it before guessing a name (see Reference). ### 2. End-to-end workflow One walk from an empty wor