Brand kits and context

A brand kit holds identity information such as colors, typography, logos, and positioning. Context documents add the guidance a workflow needs: brand voice, audience information, SEO rules, writing examples, and more.

1. Find or create the kit

simplified brandkit:list
simplified brandkit:create --title "Acme Studio"

Reuse an existing kit when it represents the same brand. Copy the brand kit UUID from the response and use it as BRAND_UUID in the next steps.

simplified brandkit:get --brand "BRAND_UUID"

2. Add structured brand identity

Create a file named brand.json:

{
  "brand": {
    "name": "Acme Studio",
    "description": "Thoughtful everyday essentials.",
    "website": "https://example.com"
  },
  "style": {
    "colors": {
      "primary": [{"hex": "#1F3D35", "name": "Forest", "role": "Primary brand color"}],
      "neutral": [{"hex": "#FBF9F4", "name": "Paper", "role": "Light background"}]
    },
    "typography": {
      "headline": {"family": "Inter", "weights": [600, 700]},
      "body": {"family": "Inter", "weights": [400, 500]}
    }
  }
}

Replace these sample values with the brand’s real identity, then apply them:

simplified brandkit:build --brand "BRAND_UUID" --json brand.json

Each color token needs a hex value. Inspect the response and any warnings, then read the kit again to verify what was saved. --data accepts an inline JSON body when a file would be unnecessary.

3. Attach a voice document

Create voice.md with guidance that can be applied to actual copy:

# Acme Studio voice
Write with warmth and clarity. Use concrete details about materials and use.
Prefer short sentences. Avoid exaggerated claims and artificial urgency.
Example: "A durable everyday mug, made for slow mornings."

simplified brandkit:context-create --brand "BRAND_UUID" \
  --doc-type brand_voice --name "Brand voice" --content-file voice.md

Keep the returned context link UUID for updates. To attach an existing workspace document instead, use --document-id "DOCUMENT_UUID" rather than creating new content with --doc-type.

4. Read the guidance you need

simplified brandkit:context-list --brand "BRAND_UUID"
simplified brandkit:context-get-by-type --brand "BRAND_UUID" --type brand_voice
simplified brandkit:brandbook --brand "BRAND_UUID" --elements "brief,voices,colors,fonts"

The brandbook command returns a view suited to integrations and AI workflows. Choose only the sections you need. Other element names include logos, description, social_links, knowledge, brand_icps, usps, products, competitors, and content_pillars; see the command’s help for the full set.

Retrieving brand context does not automatically apply it to later generation commands. Your script or assistant must use that guidance when writing prompts, preparing copy, and reviewing outputs.

5. Maintain the documents

simplified brandkit:context-get --brand "BRAND_UUID" --link "CONTEXT_LINK_UUID"
simplified brandkit:context-update --brand "BRAND_UUID" \
  --link "CONTEXT_LINK_UUID" --content-file voice.md

Use brandkit:context-delete --brand "BRAND_UUID" --link "CONTEXT_LINK_UUID" to remove a document link you no longer need. The link identifier is not the brand kit’s ID.

Import structured modules

If you already have structured brand modules, use:

simplified brandkit:import --brand "BRAND_UUID" --json modules.json

modules.json must follow the brand module import schema for the modules being provided, such as brand voice, ideal-customer profiles, or USPs. It is a different input contract from the identity/style document used by brandkit:build; do not reuse one file for both commands without checking its structure.