matrize

Plugin matrize from marketplace werkstoff in Anselmoo/werkstoff. Commands read from the repo's manifest — 11 days ago.

Skills (12)

• matrize-brief

  Use to synthesise a design-system derivation into the approval artefact a human signs: target taxonomy, chosen direction, what is deliberately NOT adopted and why, and falsification criteria stating what would show the system does not hold. Trigger on 'write the design brief', 'what are we actually

• matrize-collect

  Use to take reference exemplars into a design-system derivation with full provenance — what was taken from where, when, under which extraction-reliability grade and which rights grade — and then lock the reference store read-only. Trigger on 'collect these references', 'add this site as a reference'

• matrize-decode

  Use to MEASURE what collected references actually do — type scale as ratios rather than px, spacing as a base unit plus steps, colour as roles before values, radii as a series, motion as duration and easing classes, density — emitting one Design Card per finding with its source, its selector-or-page

• matrize-dolmetsch

  Use to translate between vague design instruction and the precise terms of a derived system, in both directions — 'make it airier' into named tokens and numbers on the way in, and named tokens back into plain language on the way out. Trigger on 'make it airier', 'what does that mean in actual number

• matrize-echo

  Use when the design direction is already settled and only its expression is open, to produce variations inside one idiom — same premise, same roles, different execution — each rendered in the system's own inherited shell. Trigger on 'show me a few versions of this', 'same direction, different execut

• matrize-emit

  Use to render a derived design system to a concrete target by running the plugin's committed formatter scripts against its DTCG token file — html and pdf produce the landscape sketchbook that carries the approval block, css and vitepress produce platform output, and provenance produces the graph vie

• matrize-name

  Use to INTERPRET measured Design Cards into a named lexicon: every recurring element gets a name, a purpose, a rule and an anti-rule, written machine-addressably so matrize-dolmetsch can read it back. Trigger on 'name these elements', 'give every element a purpose and a rule', 'write the lexicon', '

• matrize-preflight

  Use to find out what a design-system derivation can honestly measure in this project before any tokens are spent: the questions no reference can answer (what artefact, screen or print, which render targets, what is already fixed, what is off limits), the existing CSS/token/framework footprint alread

• matrize-retrofit

  Use to lift an existing project's ad-hoc CSS into the design-system taxonomy WITHOUT changing anything visually — naming what is already there, recording where each value came from, and proving zero visual diff rather than asserting it. Trigger on 'organise this project's scattered CSS', 'name what

• matrize-spread

  Use when the design direction is genuinely still open and several deliberately divergent idioms should be compared side by side, each presented in one fixed shell so the comparison is of systems rather than of presentations. Trigger on 'show me a few different directions', 'four properly different o

• matrize-status

  Use to report where a design-system derivation stands — which artefacts exist and when they were written, which are stale against inputs they derive from, whether the survey is past its expiry and which claim forces it, whether the approval block is signed, and whether a spread choice is still unans

• matrize-survey

  Use to scan the current state of the art in design-system delivery — token formats and tooling, build and bundler conventions per target, component distribution, the accessibility baseline, and how systems are actually documented today — because a design handbook does not go stale on style, it goes

Subagents (6)

• decode-referee

  Independently re-derives one Design Card''s measurement from the source it cites, blind to the reasoning that produced it, so a card nobody can reproduce is dropped before it becomes a token. One card per dispatch, and it receives only the cited source location and the claim — never the authoring ag

• design-critic

  Adversarially reviews proposed Design Cards and lexicon entries for the two failures that make a derived system worthless — copying dressed as principle, and design added where none was asked for. It has standing to reject an entry outright, and the rejection test is explicit: a purpose naming neith

• fact-checker

  Runs the mechanical checks matrize's confabulation gate depends on — whether a named package, tool, specification or API actually exists, whether a cited URL resolves, whether two names collide by string match, and whether an artefact is past its recorded expiry. Verifies by resolving the thing itse

• lexicon-keeper

  Interprets one measured dimension into lexicon entries — each carrying a name, a purpose, a rule and an anti-rule, with the purpose drafted against the named-principle vocabulary rather than against what a reference happened to do. One dimension per dispatch, so the dimensions stay independent. Read

• reference-decoder

  Measures one collected reference into Design Cards — type as ratios, spacing as a base plus steps, colour as roles before values, radii as a series, motion as duration and easing classes, density — each card citing its source location and carrying an extraction-reliability grade. One reference per d

• token-emitter

  Authors a formatter for one matrize emit target — a committed script that turns the DTCG token file into that target deterministically. This is how a target that does not exist yet gets built: matrize ships css, vitepress, html, pdf and provenance, while Tailwind, SCSS, JSON and TOML are named in th

Hooks (1)

• PreToolUse

  python3 -B "${CLAUDE_PLUGIN_ROOT}/hooks/matrize_guard.py"

Similar plugins