Skip to main content
The cats don’t start from zero each session. A project accumulates knowledge in five layers, and every layer compounds: the team you have after ten cycles is meaningfully better than the one you started with — because it knows your business, your rules, and your winners.

​
The brief

The durable identity of your project, written by Mad Kitty during /setup: core promise, positioning, features, use cases, constraints. Every cat reads it before doing anything. If your positioning changes, tell Mad Kitty to update the brief — it’s a living document, not a one-time form.

​
Memories

Rules and learnings the cats save and recall across all sessions. Two ways they’re created:
  • During setup — Mad Kitty captures compliance and CTA rules for your business model (e.g. what claims are off-limits, how trials must be described).
  • As you work — ask any cat to remember something: “remember: never show competitor logos”, “remember: our audience responds to urgency, not discounts”. The correction sticks for every future session, in every chat.
Memories are the difference between an assistant and a teammate. Use them aggressively — anything you’ve said twice should be a memory.

​
Formats

A format is a winning ad turned into a reusable recipe. When a creative performs, run /save_format in its chat — Creo Kitty distills what made it work (structure, pacing, hook style) into a template it can apply to future concepts. Over time you build a library of proven formats unique to your brand.

​
Reference assets

Raw material you upload for the cats to use and learn from:
  • Winning reference ads (3–10, yours or competitors’) — teach the team what “good” looks like in your market. Collected during setup, extendable any time.
  • Logo and brand assets — used directly in production by Creo Kitty.
Upload them in chat or via the project’s brand assets area. Details in Creo Kitty → Your assets.

​
Custom skills

For power users: packaged instructions that extend what a cat knows how to do — brand-voice guides, production playbooks, house style rules. These are developer-flavored; see Custom Skills in the Developers section.
Rule of thumb: the brief says who you are, memories say what to always/never do, formats say what works, reference assets show instead of tell, and custom skills package all of the above for repeatable jobs.