Architecture
The Branding Assistant follows a layered architecture that separates concerns and enables reusability across different products and branding needs.Conceptual Architecture
Brand Normalization Layer
Converts project input into a Brand Anchor - a consistent text block injected into every prompt.Brand Anchor Example
“Sparki.tools is a terminal-first developer tool focused on effortless CI/CD. The brand is modern, confident, minimal, and craftsmanship-driven. Visuals should feel precise, dark-mode native, and subtly kinetic.”
Visual Vocabulary
Derived attributes that feed all downstream modules:- Motion level: subtle, intentional
- Complexity: low
- Emotional register: calm confidence
- Metaphors: sparks, pipelines, orchestration
Prompt Module System
Each Prompt Module is reusable across products and contains:| Component | Description |
|---|---|
| Purpose | What the module generates |
| Model Suitability | Which LLMs work best |
| Prompt Template | Parameterized prompt structure |
| Output Requirements | File formats and variants |
Available Modules
- Logo Module - Primary logo, icon, and wordmark
- Hero Banner Module - Website and README hero visuals
- Animation Module - Motion branding (mascot idle, system behavior)
- Social Module - High-impact announcement graphics
Model Routing Rules
| Asset Type | Model | Rationale |
|---|---|---|
| Logos | Grok Imagine | Sharp composition, static precision |
| Banners | Grok Imagine | UI + brand coherence |
| Animations | Sora | Temporal consistency, looping |
| Social Cards | Grok Imagine | High contrast, fast iteration |
Output Contract
Every generated asset includes:- Prompt used
- Brand anchor version
- Timestamp
- Intended use (logo, hero, etc.)