From mismagent
mismAgent model movement (successor of mism-build-dag for the architecture-driven build). EMITS the building-block manifest (building-blocks.yaml) — the IDEA-2→build bridge that the Composer reads — as a CONSEQUENCE of the tactical model: aggregates→aggregate block, commands→application-service, Customer/Supplier relationship→port+adapter+boundary, events/views→read-model, screens→ui. Pins the TYPES at the boundaries (Published Language), picks the projection (in-process/cross-deploy) from the profile, attaches the user's tests_nl and the §14 gates. Replaces the file-task dag.yaml. Use after the architecture, before the Composer.
How this skill is triggered — by the user, by Claude, or both
Slash command
/mismagent:mism-build-manifestThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Emits `<output_dir>/<feature>/building-blocks.yaml`: the **Composer's only input**. The manifest is
Emits <output_dir>/<feature>/building-blocks.yaml: the Composer's only input. The manifest is
a consequence of the model (anti-zombie: every row has a consumer = the Composer), not
hand-written. Rationale: redesign/composer-spec.md §8.
context-map.md — tactical model (aggregates/invariants/commands/events) + Customer/Supplier relationships;architetture/ + ADRs (including the §14 enforced_by);<output_dir>/profile.md, default .mismagent/profile.md) —
sides (→ projection), gate, identity/stack.| source in the model | → manifest row |
|---|---|
| aggregate + invariants | aggregate block (+ invariants, invariant_fields, identity, tables) |
| command(s) (per aggregate) | application-service block (commands, consumes) |
| Customer/Supplier relationship | port block (consumer-owned) + adapter + an inter boundary |
| domain event / view | read-model block (+ view_shape) |
| UI screen | ui block (consumes_rm, triggers) |
ProductId (from Catalog) on a Sales port would recreate
Sales→Catalog. The value class lives inside the context; at the seam you speak primitives.
(Wave-1 lesson: an unpinned boundary ⇒ the workers, built blind, do not compose.)in-process if consumer and supplier are the same side
(profile), otherwise cross-deploy (→ the port projects into OpenAPI + generated types + CDC; and
the BE‖FE parallelism re-emerges as an effect, not dogma).invariant-test (aggregate boundary) · consumer-driven (port, read-model).invariant_fields/tables): no writes outside
the adapter; the invariant field is confined → consumers use the named predicate.tests_nl (the worker translates them into
tests). A boundary without tests_nl is not ready: ask.building-blocks.yaml (blocks + boundaries with projection + tests_nl + gates + build_order).
Then the Composer reads it: its Phase 1 (readiness) re-verifies these rules before
building (pinned types, contract_test, projection, gates, tests_nl).
Summary: N blocks per type, M boundaries (with projection), confirmation of pinned types, tests_nl
elicited from the user, and what is missing before launching /mismagent:composer.
npx claudepluginhub lucolucus/mismagent --plugin mismagentProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.