Update Brand Kit

Update Brand Kit

Purpose

Keep a brand kit correct and rich by talking to the user. A brand kit is the canonical context an ad/content-generation pipeline reads, so what's in it directly shapes every downstream generation. Reach for this whenever the user wants to set or refine brand positioning/voice/audience, add standing do/don't guidance, manage the product list, or attach product photos.

This skill is the portable domain model — the fields, the semantics, the rules. How you actually persist a change is the host's concern: a brand-kit API, a CLI, or a brand-kit document in a workspace. The field model, semantics, and caps below hold regardless of which backend stores the kit.

Inputs

• A natural-language request — free-form ("make the voice warmer and more technical", "we sell to ops teams not consumers", "add our Pro plan at $49"). You translate this into the field model below; do not ask the user to name fields.
• Optionally, a brand identifier or name — when the user owns more than one brand, you need to know which one. If they only have one, use it.
• Optionally, a folder of product photos to attach to a product.

The brand-kit field model

These are the context fields. Treat each edit as a partial update (see semantics): set only what's changing.

• description — what the brand does, in 1–2 sentences.
• audience — target audience / ICP.
• voice — tone of the copy.
• instructions — standing guidance applied to every generation (e.g. "always show the product in use", "never use red"). High-leverage — set this whenever the user describes a recurring do/don't, not a one-off.
• brand_type — one of: product, saas, service, agency, restaurant, fashion, beauty, fitness, finance, education, health.
• value_props — short selling points; the kit keeps the first 5.
• primary_color / accent_color — hex like #1a2b3c (validate the format).