Menú
Token-driven visual-asset producer (icons/banners/logos/data-viz/slides) on DESIGN.md tokens + the aesthetic gate. Use to generate a visual asset when a design system exists. Not for non-visual.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
| name | asset |
| description | Token-driven visual-asset producer (icons/banners/logos/data-viz/slides) on DESIGN.md tokens + the aesthetic gate. Use to generate a visual asset when a design system exists. Not for non-visual. |
The visual-asset producer over the theme system. v6 had five separate gateway-* asset skills
(icon/banner/brand-assets/dataviz/presentation); v7 collapses them into one token-driven producer
that routes by asset type — the same systems-not-skills move that made autopilot thin. Every asset it
emits references the design tokens (no raw hex/px) and conforms to the project's DESIGN.md, so it
passes the aesthetic gate by construction rather than being audited into compliance after the fact.
Does: produce a typed visual asset (icon / banner / brand / dataviz / presentation) from the design
contract — token-referencing, on-style, spec-declared (sizes, safe-zones, formats); write a receipt.
Does not: invent the design system (that's design-brief → DESIGN.md + DTCG tokens), run the
visual verdict (that's the aesthetic gate — asset conforms to it), produce audio/non-visual media
(separate), or emit raw values (the token policy is the whole point).
design-brief first to establish DESIGN.md + tokens.design-brief, not asset.aesthetic gate.gateway-audio is a separate media-domain capability, deferred).| Situation | Reference |
|---|---|
| Per-asset-type specs (icon styles/sizes, banner safe-zones/dims, brand/logo, chart selection, slide layout) | references/asset-specs.md |
| Design KB lookup (style/palette) · token emit · the audit it must pass | ../kb-seed/ · ../dtcg-emit.py · ../../../gateways/aesthetic.md |
DESIGN.md + the validated DTCG token file (from design-brief/dtcg-emit).kb-system query --room ui-style/ui-palette) for style grounding.DESIGN.md + the DTCG tokens. No contract → run design-brief first (do
not invent a palette here).references/asset-specs.md):
currentColor or
var(--token)), consistent stroke width + sizing scale, batch + multi-size export.var(--token)), never a raw
#hex/px. This is what makes the output pass the aesthetic gate's token-compliance BLOCK.../../../gateways/aesthetic.md): contrast, named-style
adherence, no anti-default patterns without rationale. Fix before emit.<workspace>/receipts/asset-receipt.json): base schema + asset_type, tokens_referenced
(bool — no raw values), style_source (DESIGN.md / KB drawer), aesthetic_self_check, outputs.
persistence: Spec-Anchored.DESIGN.md/tokens present: stop and run design-brief — an asset without a contract is a guess
that will fail the aesthetic gate.Done when: the requested asset exists at the product path, every visual value references a token, it
adheres to DESIGN.md's named style, and the aesthetic self-check passes; an asset receipt records the
type + token compliance.
Not done if: any raw #hex/px was emitted; the asset ignores the design contract; a chart type was
chosen by default; it was produced with no DESIGN.md to conform to.
Next step: the aesthetic gate audits the asset in context; executor integrates it into the build.
DESIGN.md + tokens) asset produces against. Run it first.asset conforms by construction; the gate enforces.kb-system, dtcg-emit): the design KB + token emitter asset reads.Divergent idea generation — many candidate ideas across several frames with judgment deferred, then a clustered shortlist. Use to open a solution space wide, or /brainstorm. Not for developing one idea (ideate) or picking one (propose).
Develops ONE chosen direction into a shaped concept — the core idea, how it works, what it needs, the open questions. Use to deepen a single idea, or /ideate. Not for generating many (brainstorm) or deciding among them (propose).
Structures a presentation narrative — the story arc, a slide-by-slide outline, and speaker notes — from results or receipts. Use to shape a talk or deck, or /present. Not for prose reports (report) or rendering visuals (asset).
Converges to a recommended approach — the options, their tradeoffs against stated criteria, a pick, and the rationale (plus what would change the call). Use to decide among approaches, or /propose. Not for generating options (brainstorm) or deep-diving one (ideate).
Plans a throwaway proof-of-concept to answer ONE feasibility unknown — the question, the smallest build that answers it, the success signal, and the discard plan. Use to de-risk before committing, or /prototype. Not for the real build (executor) or deciding (propose).
Produces a REDTEAM-FINDINGS.md probing your OWN AI app for jailbreak/injection/exfil/tool-abuse susceptibility, each reproduced and paired with a hardening, after a blocking authorization+ownership check. Use to red-team an owned AI system defensively.