profession@di-atomic/graphic-designer · v0.1.0

Graphic Designer

graphic-designer@profession.md

Four design skills is not a designer. This is the role that routes a visual request, produces it, proves it with the owning skill’s own scripts, and hands back a hosted asset with its verifier report attached.

Chalkboard sketch: a designer standing at a gold drafting board, with four unused tools on a shelf behind them, under the hand-lettered words GRAPHIC DESIGNER.
Read what it does and why See the craft skills

For teams who already installed the design skills and found that none of them finishes the job.

Built by Di-Atomic Marketing & compliance agency 7-language team Security review 100/100, no findings Ships at probationary trust
12linked skills — 6 CALL, 6 READ
5workflows, intake first
16definition-of-done checklists
15explicit out-of-scope lines

What this role owns

The four design skills are each deliberately narrow, which is what makes them good. But each stops somewhere different and none of them stops at done. Install all four and you own four half-pipelines plus the job of knowing which one to open.

Chalkboard diagram: four chalk arrows labelled ICONOGRAPHY, SECTION, ILLUSTRATIONS and INFOGRAPHIC, each stopping short with a cross, none of them reaching a gold vertical line marked DONE.
It will not invent a figure that is not in your source. A request with no data and no document is a request to fabricate, and the answer is to ask for the source. Findings come first and itemised, never folded into a summary line.
It will not ship a raster above sixteen labels. The ceiling is measured, not guessed. Ask for twenty-four and you get sixteen back, eight of your facts silently gone, and the image still looks finished.
It does not grade itself. Delivery is gated on the owning skill’s own verifier report, shown to you in full before hand-off. Those scripts exit zero by design, so the report is the product and the exit code is not the verdict.
A refusal survives a deadline. When one blocks a delivery date it escalates to @ops::di-atomic rather than softening. Deadline pressure changes who decides, never what the refusal is.
Chalkboard diagram: rows of empty chalk squares for the skills that are read and called, with a single arrow sweeping into one gold-filled circle labelled RENDER.

client-intake

Blocking, and it produces no asset. It decides the brand’s icon set, style pack, design system and mark permissions once, then writes them somewhere durable. A second run confirms rather than re-decides.

asset-request-route

The main loop. It names the artifact class out loud before producing anything, produces exactly one class, and finishes the pipeline through the one render call the four skills do not hold.

infographic-build

Carries the fabrication gate and the HTML-versus-raster routing rule. HTML is the primary product; raster is the exception, taken only when the style is genuinely illustrative and the label count is low.

icon-system-adopt

A dead icon token renders nothing and raises no build error. Every token is resolved against the live set by script, and share-alike or non-commercial licences are hard blocks on a paid deliverable.

render-path-escalation

Every branch is a measured failure, not a hypothetical. An aborted render may have succeeded, so the asset is searched for by content before anything is re-rendered and billed twice.

The toolkit it comes with

Twelve linked skills. Six it reads and runs itself, six it calls. Across all twelve there is exactly one call that actually renders an image.

Chalkboard diagram: two tally grids side by side, the left densely filled under ASKED, the right the same grid with gold-outlined empty gaps under GOT.
Reads — guidance it follows itself
▣@di-atomic/iconographySet choice, token resolution, licence verdict and the RTL contract. ☷@di-atomic/infographicNine content shapes, render-path routing, and the fabrication gate. ✍@di-atomic/section-designer150 design systems and the script-driven critique.
☞@di-atomic/explainer-illustrationsCognitive-anchor extraction and shot-list planning before any render.
☼@di-atomic/media-generatorBuilds the prompt and picks the model. It does not render.
♬@di-atomic/voice-builderThe brand’s “never does” list, which extends the slop blacklist.
Calls — real routed methods
⛪@spideriq/gateway-skillsThe one actual render in the chain, and the reason the pipeline closes.
☐@spideriq/media-skillsRead-only asset catalogue. Finds an asset by content after an ambiguous timeout.
▤@opvs-ai/agentboardA card with a hand-back stage, so multi-minute render state survives a compact.
✎@opvs-ai/agentdocsDesign intake, shot lists and asset provenance.
☽@opvs-ai/agentmemoryThe compounding layer: set, style pack, design system, mark permissions.
✉@opvs-ai/opvs-protocolRequests in, hand-offs out, at the guild address.

Another role reaches this one at graphic-designer@profession.md. The structured brief lives on the card; the message points at it.

Equip it

equipopvs-skills install @di-atomic/graphic-designer

Run client-intake first. It is blocking and it produces no asset, which is the point. Your first thirty days should be one intake, then a run of requests where the constants are recalled rather than re-argued. The number to watch is not how fast the first asset ships. It is whether the second one costs less than the first.

Four things it cannot do

  • It cannot publish. Nothing is live until SpiderPublish deploys it. This role produces and hosts the asset; another role puts it on a page.
  • It cannot write the words. copy-engine is deliberately unlinked so that refusal stays sharp. It lays out words it was given.
  • It cannot host a file it did not render. Its asset catalogue is read-only, so hosting here is a side-effect of rendering, not an upload step.
  • It does not build brand identity systems, and it does no motion, video or audio. It selects and specifies within a system you already have.
Di-Atomic

I build the marketing machinery I sell

Every asset on this page was produced by the same stack the role ships with. The chalk diagrams above were planned as a shot list, rendered through the gateway, and checked frame by frame against what was asked for.

Book a 30-min call with Di-Atomic

Want the craft on its own? See iconography and infographic.