Route visual deliverables with ak:design

Use ak:design when the outcome is a brand or campaign visual and you want one entry point to select the appropriate production route. The Skill contains workflows and bundled knowledge for logos, CIP mockups, slides, banners, social images, icons, and posters, and can coordinate related Marketing Skills for brand and token work.

Choose ak:design for a visual deliverable

Use ak:design when

• The deliverable is a logo concept, CIP mockup, presentation, banner, social image, SVG icon, poster, or a bounded combination of these.
• You want the workflow to classify the request before choosing tools or files.
• You have brand inputs, channel dimensions, copy, and an approval boundary.

Choose another workflow when

• You only need corporate identity applications. Use ak:cip-design for the narrower workflow.
• You need token architecture or component specifications. Use ak:design-system.
• You need working page or component code. Use ak:frontend-design.
• You need design guidance or a UI audit without implementation. Use ak:ui-ux-pro-max or ak:web-design-guidelines.

Prepare the brief and runtime

Provide the target artifact, audience, channel, exact dimensions or aspect ratio, approved copy, brand source, output format, file boundary, and whether external research or generation is allowed. Confirm you have rights to every logo, image, font, and reference supplied.

Complete Onboarding and read Runtime adapters before the first run.

Run the Skill

/ak:design Create three launch-poster directions for the supplied event brief and brand guide. Produce reviewable prompts and layout specs only. Do not generate images, browse, write files, or publish

/ak:design Create three launch-poster directions for the supplied event brief and brand guide. Produce reviewable prompts and layout specs only. Do not generate images, browse, write files, or publish

$ak:design Create three launch-poster directions for the supplied event brief and brand guide. Produce reviewable prompts and layout specs only. Do not generate images, browse, write files, or publish

After choosing a direction, authorize only the needed route and outputs. For example, request two exact-size HTML banner sources and PNG exports in a named directory, while keeping upload and publication out of scope.

Understand the stages

1. Classify the deliverable. The Skill routes logo, CIP, slides, banner, social image, icon, or poster work instead of applying one generic process.
2. Confirm inputs. It gathers brand rules, copy, sizes, formats, asset rights, references, and the boundary between guidance and production.
3. Develop directions. The selected route uses relevant bundled tables and references to form concepts, prompts, layout decisions, or token choices.
4. Review before mutation. You choose a direction and separately approve file writes, provider calls, browser capture, or dependent Skills.
5. Create the approved artifacts. Depending on the route, output can include SVG, PNG, HTML/CSS, prompts, briefs, or presentation files.
6. Verify and report. The workflow inspects dimensions, rendering, copy, contrast, brand consistency, and file paths, then reports remaining risks.

Keep external effects under your control

Do not treat the Skill as permission to alter source files, install packages, rebuild bundled knowledge, contact a platform, upload assets, purchase media, publish, commit, or deploy. Keep generated claims and metrics out of visual copy unless they come from an approved source.

Verify the outputs and evidence

A complete run should identify the selected route, approved inputs, files created or changed, exact dimensions, provider or capture operations performed, and the visual QA used. Review spelling, brand marks, responsive crops, contrast, safe zones, accessible alternatives, and whether editable source is available.

For HTML/CSS-to-image routes, inspect both the source and exported pixels. For model-generated images or SVG, inspect the actual artifact rather than accepting the prompt or model response as proof.

Troubleshoot or continue

Continue with the Marketing Kit overview or review Projects, artifacts, and checkpoints before recovery.

Know the current limits

• Stable and beta contain byte-identical ak:design content in the inspected releases.
• Bundled styles, sizes, palettes, formulas, and reference data are starting points. Verify current platform specifications and the actual brand source.
• Some references contain historical provider, model, price, performance, and platform wording. This page makes no guarantee about them.
• The poster route emits prompts before any separate image-model call; a prompt is not a finished poster. Social and banner routes also require successful rendering and visual QA before an export is complete.
• This Marketing page describes the whole Marketing Skill field. It does not import outcome semantics from an Engineer page with the same Skill name.