Skip to main content
Your brand kit is the context that makes everything else on-brand. These tools read and edit it, and read and grow a semantic knowledge base that holds everything you have taught ContentHero about your brand.

​
The brand kit

A brand kit’s content is a set of sections, each one Markdown document. Every kit starts with eight across three tabs: About, Audience, Offer and Content Strategy (overview); Voice & Tone, Writing Style and Speaking Style (voice); Design Guidelines (visual). The user can rename them and add their own. Each section has a stable key, and a starter section has a role that says what it means and is the same in every kit, whatever it is named (voice_and_tone, audience, …). Start with the summary: it is small, and each section’s outline (its own headings) and length tell you which sections the task needs, so the next read pulls only those. Edits need brand:write. Section writes are by key and all or nothing, naming only the sections you change. A body replaces the whole section in Markdown, so read it, change what needs changing, and send the whole body back. Pass each section’s version as expectedVersion: if anyone changed it since you read it, nothing is written and the error returns its current body, so you re-read and reapply rather than overwrite. revertTo restores an earlier version as a new one. Archiving is a soft delete; there is no hard delete.

​
The knowledge base

Everything you have uploaded about your brand: notes, decisions, lessons, documents, articles, video transcripts. It is stored with embeddings, so it is semantically searchable, and it grows as you work. This is the deepest grounding ContentHero has.

​
Three reads

  • search_brand_knowledge (the workhorse): semantic retrieval. Give it a natural-language query, get the most relevant passages ranked by similarity. Reach for this first whenever you need what the brand has said or decided about a topic.
  • list_brand_knowledge: the complete index (titles and metadata, no bodies). Browse what exists or find an item’s id.
  • get_brand_knowledge: one item’s stored body by id.
Browse to see what exists, search to find what is relevant, get to open one item.

​
Grow it (where the value compounds)

The knowledge base is most valuable when it grows as you work. When the user learns something, decides something, or shares a resource, offer to remember it with add_brand_knowledge (needs brand:write). Confirm before adding, give it a clear title, and tell the user it is now searchable. Remove an item with remove_brand_knowledge on user request only.
When grounding any on-brand decision, a knowledge search is often the single highest-leverage read. Do not skip it because the kit’s sections looked sufficient; the knowledge base holds what the sections do not.

​
The hard line

Never silently change the brand document or knowledge base. Reads and summaries are free. Any write (a section edit, a new section, a knowledge add or remove) is confirmed with the user first.