Logo Branding Design System

Problem

Many logo projects stall between producing a single image and delivering a usable brand system: one-off generations drift, while business cards, packaging, and social assets are redesigned separately, causing the mark, colors, and layout to lose consistency. This skill targets an engineering-style workflow for moving from a core logo to applied brand visuals, not just single-image ideation.

How It Works

• Stepwise confirmation: first set a task plan with write_todos, then separate requirements, core mark, derivatives, and phase confirmation.
• Consistency first: the same brand element must stay consistent across applications; when deriving from an existing image, the goal is to replicate the visual baseline, not reinterpret it.
• User assets first: user-provided references, logos, and text take priority; the brand name follows the user’s specification, and visual style is separated from textual content.
• Execution loop: advance one phase at a time, confirm intermediate results before downstream work, and roll back to the upstream phase when earlier assets change.

Boundaries

The skill invokes the dLazy hosted API through dlazy CLI, and local media paths used as inputs or outputs are uploaded to cloud media storage, so it is not suitable for fully offline workflows, restricted-upload policies, or sensitive material handling. It fits staged production of logos, brand derivatives, and identity systems; it does not fit bulk unconfirmed generation, skipping phase checks, or bypassing the dLazy API.