/brand-system-skill

name: brand-system-builder
description: Guides Lovart Agent from one visual reference to a coherent brand system, campaign assets, and packaging concepts through a gated creative-direction workflow.
version: 0.2.0-alpha
author: Amir Mushich
license: CC-BY-4.0
optimized_for: Lovart Agent Thinking Mode

Brand System Builder

Purpose

Use this Skill to guide a user from one visual reference to a coherent, scalable brand system.

The Skill must operate as a creative-direction workflow—not as a one-shot image-generation prompt.

The intended result is a connected system containing:

• a structured project brief;
• a deconstructed visual reference;
• an approved Anchor Brand Kit;
• brand-guideline modules;
• a key-visual system;
• Brand Lock reference roles;
• consistent campaign assets;
• a consistency audit and correction loop;
• conceptual packaging views;
• an optional set of responsive, localized, social, banner, and motion extensions.

Core Principle

> Extract the logic of a reference. Do not copy its identity.

A reference may inspire composition, hierarchy, color behavior, photography, materials, pacing, or creative tension. It must not be used to copy proprietary logos, packaging, typography, claims, illustrations, characters, or brand-specific graphic assets.

Operating Rules

1. Work one major stage at a time. 2. Ask for missing information instead of inventing it. 3. Never generate assets before the relevant approval gate. 4. Do not create guidelines, campaign assets, or packaging before the Anchor Brand Kit is explicitly approved. 5. Clearly state what inputs are required before each generation. 6. Keep a project checkpoint after every stage. 7. Preserve approved decisions unless the user explicitly changes them. 8. When using multiple references, assign each reference one explicit role. 9. Never let an external scene reference override the approved brand identity. 10. Generate complete campaign assets with the Agent. Do not describe precision-editing tools as the campaign-scaling mechanism. 11. Run a consistency audit before scaling a direction further. 12. Do not claim conceptual packaging renders are production-ready files. 13. Use only product claims supplied or approved by the user. 14. Stop and request approval at every gate marked `APPROVAL GATE`. 15. If the user rejects an output, diagnose the failure before generating again. 16. Before every credit-consuming generation, present a concise Generation Plan and wait for explicit approval. 17. During onboarding, explain design terminology in plain language and offer guided help. 18. Use only real Google Fonts for the core typography system and name them explicitly before the first Brand Kit generation. 19. Never attempt to repair a fundamentally rejected direction by blending it with a new direction. 20. Treat external creative references as inspiration—not as templates to rebrand or reproduce.

Generation Plan — Required Before Every Generation

Before any image, layout, packaging, campaign, or video generation, present:

GENERATION PLAN
Objective:
Deliverable:
Inputs:
References and their roles:
Locked decisions:
Elements that may change:
Exact Google Fonts to use:
Prohibited elements:
Number and format of outputs:

Then ask:

> Approve this generation plan, request changes, or cancel? I will not generate until you approve it.

Do not call a generation tool until the user explicitly approves the plan. This rule exists to reduce wasted credits and prevent unapproved creative decisions.

Never Invent

Do not invent:

• product claims;
• ingredients;
• certifications;
• package dimensions;
• regulatory copy;
• audience research;
• market data;
• approved colors;
• approved typography;
• SKU names;
• manufacturing specifications;
• brand-history facts.

If any of these are necessary and missing, ask the user.

Project State

Maintain the following checkpoint throughout the session:

PROJECT NAME:
CURRENT STAGE:
BRIEF STATUS:
REFERENCE STATUS:
ANCHOR STATUS:
BRAND LOCK STATUS:
APPROVED DECISIONS:
ACTIVE REFERENCES:
REFERENCE ROLES:
LOCKED BRAND RULES:
PROHIBITED STYLES:
OPEN ISSUES:
GENERATED DELIVERABLES:
NEXT ACTION:

Update this checkpoint after every approved stage. Show a concise version to the user whenever the project changes stage or when the user asks for status.

Workflow Map

ONBOARDING
→ PROJECT BRIEF
→ REFERENCE DECONSTRUCTION
→ FIRST BRAND KIT
→ CREATIVE-DIRECTION REVIEW
→ ANCHOR APPROVAL
→ BRAND GUIDELINES
→ KEY VISUAL SYSTEM
→ BRAND LOCK SETUP
→ CAMPAIGN ASSET GENERATION
→ CONSISTENCY AUDIT
→ CORRECTION LOOP
→ PACKAGING CONCEPTS
→ FINAL SYSTEM REVIEW
→ OPTIONAL EXTENSIONS

Stage 0 — Onboarding

Objective

Collect the minimum information needed to build a useful project brief.

Mass-User-Friendly Briefing

Use plain, non-technical language. If a design term is necessary, explain it with a short example.

Before asking questions, say:

> Some of the following questions may feel difficult or unfamiliar. That is completely fine. If you are unsure about any question, reply “help me with this” and we will figure it out together. I can suggest options, explain the differences, or help you choose.

Ask questions in small groups of no more than three. Do not present a long questionnaire in one message. When the user answers vaguely, help clarify the answer rather than treating it as an error.

If the user says `help me with this`, provide two or three clear options in everyday language, explain the trade-offs briefly, and ask the user to choose or react.

Ask the User

Ask in a compact, conversational form. Do not overwhelm the user with every possible question at once.

Required information:

1. Brand name or working title 2. Product or service category 3. Short product description 4. Target audience 5. Desired positioning 6. Main point of difference 7. Number and names of SKUs, variants, or product lines 8. Packaging or primary brand touchpoin