brandbook

Convert approved creative direction into machine-readable design tokens and approval-ready styleboards.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/vTRKA/supervibe --skill brandbook-vtrka
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brandbook
Source: https://github.com/vTRKA/supervibe/tree/main/skills/brandbook
Command: npx skills add https://github.com/vTRKA/supervibe --skill brandbook-vtrka

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Rebrands and new products stall when design direction exists but a machine-readable, approval-ready design system does not, causing teams to prototype without durable tokens and evidence.

Core Features & Use Cases

  • Design-system lifecycle ownership: Turns approved creative direction into durable design tokens, component specs, motion/voice/accessibility policy, and prototype unlock metadata.
  • Evidence-first approvals: Enforces section-scoped candidate approvals, styleboard evidence, and producer receipts so prototype work can’t proceed without gated artifacts.
  • Anti-AI-Slop guardrails: Requires an antiSlopReport.schema with gate taxonomy ids and fails closed when evidence is missing or gates are unresolved.

Quick Start

Use the brandbook skill to convert an approved rebrand direction into a candidate design-system token set and an approval-ready styleboard.

Frequently Asked Questions about brandbook

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert approved creative direction into machine-readable design tokens?

To convert approved creative direction into machine-readable design tokens, you need a design system lifecycle process that generates durable tokens, component specs, and styleboard evidence while enforcing section-scoped approvals before any prototypes unlock.

What is design token drift remediation and when do I need it?

Design token drift remediation is the process of correcting misaligned or outdated design tokens across a product. You need it when prototypes and components deviate from the approved creative direction, requiring evidence-based styleboard validation to realign the system.

How do I enforce an approval workflow that blocks prototypes until design sections are approved?

To enforce an approval workflow that blocks prototypes, apply section-scoped candidate approvals and producer-based promotion gates. This ensures prototype directories remain locked until all required design system sections, tokens, and policies are explicitly approved.

Can I generate an accessibility policy alongside my design tokens?

Yes, you can generate an accessibility policy alongside your design tokens. A complete design system lifecycle converts approved creative direction into durable tokens, component specs, motion, voice, and accessibility policy to ensure compliance.

Why does my design system generation fail closed when styleboard evidence is missing?

Design system generation fails closed when styleboard evidence is missing due to enforced anti-AI-slop guardrails. An antiSlopReport schema requires explicit gate taxonomy IDs and evidence-before-score reporting, intentionally halting promotion if artifacts are unresolved.

What's the best way to manage a rebrand design system without unapproved artifacts leaking into prototypes?

The best way to manage a rebrand design system without unapproved artifacts leaking is to use evidence-first approvals with producer receipts. This gates prototype promotion into artifact directories, ensuring only explicitly approved sections are materialized.