What is a Brand Schema?

A Brand Schema is the canonical source of truth for your product's brand. It captures positioning, audience, voice, visuals, and constraints in a structured format that generates consistent outputs across all channels. Think of it as your brand's DNA expressed through 15 different outputs.

What outputs does Vox Animus generate?

Vox Animus generates 15 outputs: Vision & Purpose, Mission Statement, Target Audience, Brand Promise, Positioning, Rebrand Prompt, Voice Rules, Foundation Prompt, Visual Direction, Messaging Angles, Social Bio, Agent Prompt, Constraints, JSON-LD Schema, and LLMS.txt. These cover everything from app reskinning to AI search optimization.

What is a Rebrand Prompt?

A Rebrand Prompt is a comprehensive, copy-paste prompt you use in AI coding tools like Bolt, Cursor, Lovable, or v0 to reskin your existing application. It includes your positioning, target user description, brand energy, visual direction, voice rules, and constraints.

How is Vox Animus different from other brand tools?

Vox Animus doesn't generate your brand for you. It structures what you already know through 9 focused sprints, then enforces it through hard constraints like banned words and anti-references. It's specifically designed for indie developers using AI coding tools, not agencies or large teams.

What are JSON-LD and LLMS.txt outputs?

JSON-LD is structured data that helps AI search engines (ChatGPT, Claude, Perplexity, Google SGE) understand your product. LLMS.txt is a markdown file that tells AI crawlers what your site is about and how to index it. Both improve your discoverability in AI-powered search.

How long does it take to create a Brand Schema?

Most users complete all 9 sprints in 60-90 minutes. Each sprint takes 5-15 minutes. The system provides all 15 outputs instantly based on your inputs.

Developer Tools

Marker

Name: Brand Schema
Brand: Vox Animus

Bug reporting widget that captures everything developers need

Challenge

The BEFORE site leads with features: "automatically captures," "all in one click," "Everything you need." It solves a problem it has not named yet. Developers scan headlines. If you do not hook them with shared frustration, they leave.

Target User

Frontend developers drowning in vague bug reports. They spend more time asking "what did you do?" than fixing the actual bug. The product is for teams who have felt that specific frustration.

Key Insight

"It does not work" is the most useless bug report possible. Lead with that pain. Then offer context capture.

Marker is a fictional brand from the Vox Animus demo library. This case study demonstrates the Brand Schema methodology using realistic scenarios indie builders face.

Before & After

Same product. Same features. Different strategic foundation.

←Drag to compare→

← Before: Average Prompt

After: Foundation Prompt →

Open Before Site|Open After Site

Component Transformations

Before and after comparisons showing how Brand Schema enforcement changes every touchpoint.

Hero Headline

✗Before

✓After

→

Why This Matters

BEFORE: "Stop asking for console logs." Problem framing, but generic. AFTER: "It does not work tells developers nothing." Quotes the pain directly. Developers have received that exact message.

Primary CTA

✗Before

✓After

→

Why This Matters

BEFORE: Cyan-emerald gradient. "Get Started Free." Common SaaS pattern. AFTER: Solid orange. "Get Started." Shorter. Sharper. The color signals: bug, warning, attention.

Feature Description

✗Before

✓After

→

Why This Matters

BEFORE: "Everything you need to debug faster" with icon grid. Feature list. AFTER: "Captures everything automatically" with code snippets. Shows, does not tell.

Schema Artifacts

Enforceable design tokens and rules generated from brand strategy.

brand-schema.json

{
  "brandId": "marker",
  "voice": {
    "archetype": "Senior Developer Sage",
    "tone": [
      "a senior developer who has debugged this before. direct. tired of the same problems."
    ],
    "bannedWords": []
  },
  "colors": {
    "primary": "#f39c12",
    "semantic": {
      "deepslatenavy": "#0f172a",
      "warningorange": "#f39c12",
      "purewhite": "#ffffff"
    }
  },
  "typography": {
    "headline": "CLEAN",
    "body": "Sans-serif",
    "mono": "JetBrains Mono"
  },
  "constraints": {
    "neverUse": [
      "NEVER USE GRADIENT BUTTONS",
      "NEVER SAY \"POWERFUL\" OR \"REVOLUTIONARY\"",
      "NEVER USE \"ALL IN ONE CLICK\" OR \"EVERYTHING YOU NEED\"",
      "NEVER INCLUDE FAKE TESTIMONIALS"
    ],
    "alwaysShow": [
      "CLEAN for headlines",
      "SERIOUS, DEV-FOCUSED"
    ]
  }
}

#f39c12

Warning Orange

Orange signals bugs, alerts, attention. Deep slate navy (#0f172a) is serious dev-focused dark mode. Avoids template gradients.

Serif Headlines

Clean Sans + Mono

Clean sans-serif for headlines (Inter 600). Monospace for code blocks (JetBrains Mono). No decorative fonts.

Senior Developer Sage

Direct. Technical. Has debugged this before. Never says "revolutionary" or "powerful." Leads with the pain.

5 Never Rules

Never use gradient buttons. Never say "powerful" or "revolutionary." Never use "all in one click." Never fake social proof. Lead with pain, not features.