META·SUITE ← all nine
overview / skills / meta-design
Skill 03 · make axis

meta-design

A medium-specific design schema, executed into an audited artifact — plus the system that keeps making more like it.

SCHEMA → grid type color motion → ARTIFACT audit passed WHAT'S HAPPENING 1 · Decide the medium's rules first — grid, type, color, motion. 2 · Build the artifact by following those rules, block by block. 3 · Audit the result back against the rules — drift gets flagged. The rules are reusable — the next piece starts from a proven system, not a blank page.
FIG — schema drives assembly; an audit sweep checks every region against it
// what it does

Design is medium-shaped — a slide deck, an app screen, and a poster obey different rules. meta-design writes the schema for the medium first — grid, type, color, motion — then executes it into a real artifact and audits that artifact back against the schema.

You get two things, not one: the finished piece, and the reusable system that will make the next ten pieces consistent with it.

// the anatomy
schema

The medium's rules — grid, type, color, motion — decided before any pixel.

artifact

The real thing, assembled by following the schema block by block.

audit

A pass that checks the result against its own rules and flags drift.

// invoke it
/meta-suite:meta-design <what to design> for <which medium>

Returns a medium-fit design schema, an executed artifact built from it, and an audit report — so the next piece starts from a proven system, not a blank canvas.

Medium-first

Rules fit the format.

Self-auditing

Checks its own output.

Two outputs

The piece and the system.

It compounds

Consistent by construction.

Grounding

The ideas here aren't invented — the skill generalizes established practice into one reusable, task-agnostic move. Below: the prior art it builds on, and the in-repo contract it actually runs on.

Prior art
Structure-preserving maps (functors) — a brief is an object; its design schema is the image under a map that preserves structure, so composed briefs compose their schemas. kept internal
WCAG 2.1 — contrast (≥ 4.5:1), target size, reduced-motion — computed as pass/fail, never estimated. w3.org →
Render-and-verify — the design analogue of running code: no claim about a component is trusted until it has been rendered and audited.
In this suite
The operating contract meta-meta-design-prompt.xml — the Proposer → Executor → Auditor sequence, three phases, and the seven typed acceptance predicates.