Create corporate identity mockups with ak:cip-design

Use ak:cip-design to plan how an approved identity appears across stationery, signage, apparel, vehicles, packaging, digital assets, and other brand touchpoints. The Skill can search its bundled CIP knowledge, prepare a brief, generate selected mockup images through Gemini, and assemble PNG results into a single HTML presentation.

Choose ak:cip-design for brand applications

Use ak:cip-design when

• You have a brand name, audience or industry context, and a defined identity direction.
• You need a CIP brief or guidance for specific identity deliverables.
• You want mockups that apply an approved logo to selected touchpoints.
• You want a review artifact before commissioning production-ready files.

Choose another workflow when

• The logo or wider brand direction is not approved. Establish that source of truth before applying it across a CIP.
• You need a broad visual asset such as a poster, slide deck, banner, or icon. Start with ak:design.
• You need reusable interface tokens or component specifications. Use ak:design-system.
• You need working frontend code rather than identity mockups. Use ak:frontend-design.

Generated mockups are review aids, not print-ready artwork, fabrication drawings, accessibility certification, trademark clearance, or proof that a logo was reproduced exactly.

Prepare the brand inputs and runtime

Before you start:

• Complete Onboarding, and confirm Marketing Kit is installed for the runtime and scope you are using.
• Provide the approved brand name, industry context, desired style, and exact deliverables. Include dimensions or production constraints when known.
• Provide a logo file only when you have the right to use it and may send it to the selected image provider.
• Decide whether the run is guidance-only, prompt-only, image generation, or image generation plus an HTML presentation.
• Name an output directory you control before allowing the workflow to write images or HTML.

See Runtime adapters before assuming component-level parity.

Run the Skill

Start with a bounded brief and keep generation outside the first pass:

/ak:cip-design Create a CIP brief for Northstar, a B2B logistics brand. Cover business card, letterhead, reception signage, and vehicle branding. Use the supplied brand guide only. Do not call an image provider or write files yet

/ak:cip-design Create a CIP brief for Northstar, a B2B logistics brand. Cover business card, letterhead, reception signage, and vehicle branding. Use the supplied brand guide only. Do not call an image provider or write files yet

$ak:cip-design Create a CIP brief for Northstar, a B2B logistics brand. Cover business card, letterhead, reception signage, and vehicle branding. Use the supplied brand guide only. Do not call an image provider or write files yet

After approving the brief, make the mutation and provider boundary explicit:

/ak:cip-design Generate only the approved business-card and reception-signage mockups with ./brand/northstar-logo.png. Write PNG files to ./output/northstar-cip. Stop before creating a presentation

Use the same text with $ak:cip-design in Codex. The packaged helper's --prompt-only option avoids the provider call and image write. --logo selects image-editing input, --output selects the image directory, and --no-logo-prompt explicitly permits a provider-generated logo interpretation. Those are helper-script options, not flags on the Skill invocation.

Understand the stages

1. Confirm the application brief. The workflow records the brand, industry, style, deliverables, dimensions, logo source, output boundary, and approval state.
2. Search the bundled CIP data. Local tables supply candidate deliverables, style guidance, industry guidance, mockup contexts, and prompt ingredients.
3. Review the brief. You verify brand accuracy, exclusions, production constraints, and whether provider use is allowed.
4. Generate approved mockups. If authorized, the helper sends the prompt and optional logo image to Gemini and writes timestamped PNG files. A multi-item set defaults to business card, letterhead, office signage, vehicle, and polo shirt unless the request supplies a narrower list.
5. Render an optional presentation. The renderer reads PNG files from the selected directory and writes one responsive, dark HTML file with embedded base64 images.
6. Review the artifacts. You compare every result with the source logo, brand rules, real dimensions, legibility needs, and production requirements.

Keep approval and provider effects separate

The Skill does not authorize:

• Uploading a confidential or unlicensed logo, customer data, or unreleased identity material.
• Generating every item in a default set when only one deliverable was approved.
• Treating generated text, dimensions, colors, finishes, or logo placement as production truth without review.
• Sending files to a printer, manufacturer, social platform, ad platform, or other external destination.
• Committing, publishing, or deploying the output.

When a transparent or palette logo is loaded, the packaged generator converts it to RGB and places transparency on white before the provider call. Review that conversion if transparency or background treatment is material.

Verify the outputs and evidence

A complete run should provide:

• The approved CIP brief and the bundled data selections used to form it.
• The exact provider command or prompt-only evidence, including selected deliverables, model option, aspect ratio, logo path, and output directory.
• The paths of PNG files actually created, with failures kept visible.
• The HTML presentation path when rendering was approved.
• A review summary covering logo fidelity, spelling, contrast, safe placement, responsive presentation behavior, and unresolved production questions.

Do not accept an image merely because the prompt asked for an exact logo or a particular resolution. Inspect the rendered pixels and verify all visible text.

Troubleshoot or continue

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

Know the current limits

• Stable and beta contain byte-identical ak:cip-design Skill content in the inspected releases.
• The bundled tables and guides are reference material, not current platform, legal, fabrication, accessibility, or brand authority.
• Provider names and model wording in packaged source are historical release evidence. Current availability, quality, resolution, latency, and price are not guaranteed.
• The source overview and the packaged generator disagree about an additional flash2 default; the exposed parser accepts only flash and pro and defaults to flash. This page follows the executable parser and makes no quality claim about either option.
• The renderer describes known filename categories with built-in copy and uses generic copy for unknown names. Review every description before sharing it.