Skip to main content

​
Project Definition

The Branding Assistant requires a structured project definition as input. This document defines the contract and provides examples.

​
Input Contract

The system requires a normalized project object containing brand identity information.

​
Required Fields

FieldTypeDescription
namestringProduct or project name
descriptionstringShort tagline or description
missionstringCore purpose statement
tonestring[]Brand voice attributes
visual_identityobjectVisual style definition
taglinestringMarketing tagline

​
Optional Fields

FieldTypeDescription
mascot_personalitystring[]Mascot behavior rules
typographyobjectFont preferences
forbidden_stylesstring[]Styles to avoid
competitive_positioningstringMarket differentiation

​
Example: Sparki.tools

name: Sparki.tools
description: Zero-fuss Kontinuous Integration
mission: CI that adapts to the developer
tone:
  - friendly
  - confident
  - terminal-first

visual_identity:
  mascot: kinetic spark
  colors:
    background: dark
    accents: glowing

tagline: Zero-fuss CI for humans

mascot_personality:
  - abstract, not cartoon
  - controlled energy
  - friendly but professional

forbidden_styles:
  - cartoon faces
  - corporate clipart
  - overly playful

​
Design Principle

The project definition should be model-agnostic and reusable across all branding tasks.

​
Reuse Guarantee

To apply this system to another application:
  1. Swap the project definition
  2. Regenerate brand anchor
  3. Reuse all prompt modules unchanged
  4. Route to same or different models
Result: Same flows, same formats, different identity.

​
Validation

The system validates project definitions before processing:
  • All required fields present
  • Tone array contains at least one value
  • Visual identity includes mascot or abstract concept
  • No conflicting style directives