Captures brand identity from user-provided assets and stores it for document skills to reference. Use this skill whenever the user says: "set up my brand", "configure brand identity", "use my company colors", "brand my documents", "my brand guidelines", "import my brand", "set up company style", "use my logo", "brand setup", "my presentations should match my company style", or when the user provides brand assets (logo, PPTX template, brand guidelines PDF, color preferences). Also trigger when document skills notice no brand-profile.md exists and the user wants branded output. Do NOT use for applying brand voice to individual content tasks after setup is complete (brand configuration is read by other skills automatically), calibrating email tone specifically (use email-style — it handles email-specific voice refinement), designing visual brand assets like logos or color palettes (brand skill captures guidelines, not design output), or auditing existing content for brand compliance without a setup/update intent.
From tandemnpx claudepluginhub binatrixai/tandem-marketplace --plugin tandemThis skill is limited to using the following tools:
evals/evals.jsonreferences/brand-voice.mdreferences/persona-template.mdVerifies tests pass on completed feature branch, presents options to merge locally, create GitHub PR, keep as-is or discard; executes choice and cleans up worktree.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Executes pre-written implementation plans: critically reviews, follows bite-sized steps exactly, runs verifications, tracks progress with checkpoints, uses git worktrees, stops on blockers.
Extract brand identity from user-provided assets and save to ~/Tandem/memory/brand-profile.md.
Once configured, document skills (presentation, report-writer, budget-wizard) automatically
reference the brand profile when creating output.
See METHODOLOGY.md language mirror rule. Reply in the user's language.
Read ~/Tandem/memory/brand-profile.md if it exists. If brand is already configured:
AskUserQuestion:
- "Update my existing brand"
- "Start fresh"
- "Show me what's configured"
If "Show me" — display current brand profile and ask what to change.
Create ~/Tandem/brand/ directory if it doesn't exist.
AskUserQuestion:
- "I have a presentation template (PPTX)"
- "I have brand guidelines (PDF)"
- "I have a logo file"
- "I'll describe my brand manually"
Allow multiple selections. For each:
PPTX template:
Ask user to place their PPTX template in ~/Tandem/brand/.
Read the file using the pptx skill. Extract:
PDF guidelines:
Ask user to place guidelines PDF in ~/Tandem/brand/.
Read the file using the pdf skill. Extract:
Logo file:
Ask user to place logo (PNG, SVG, or JPG) in ~/Tandem/brand/.
Note the file path for reference in brand-profile.md.
AskUserQuestion:
- "Logo uploaded — continue"
- "I don't have a logo file"
Manual description: Walk through brand elements one at a time:
What are your primary brand colors?
AskUserQuestion:
- "Blue and white"
- "Red and black"
- "Green and grey"
- "Let me describe them"
If "Let me describe" — accept free text with hex codes if they know them.
What fonts does your brand use?
AskUserQuestion:
- "Arial / Helvetica"
- "Times New Roman / Serif"
- "I don't have specific fonts"
- "Let me specify"
What's your brand's tone?
AskUserQuestion:
- "Professional and formal"
- "Casual and friendly"
- "Technical and precise"
- "Creative and bold"
Create ~/Tandem/memory/brand-profile.md:
# Brand Profile
_Generated: [date]_
_Source: [PPTX template / PDF guidelines / manual input]_
## Colors
- **Primary**: [color name] [#hex]
- **Secondary**: [color name] [#hex]
- **Accent**: [color name] [#hex]
- **Background**: [light/dark preference]
- **Text**: [color for body text]
## Typography
- **Headings**: [font family], [weight]
- **Body text**: [font family], [weight]
- **Size guidelines**: [if specified]
## Logo
- **File**: ~/Tandem/brand/[filename]
- **Placement**: [top-left / center / as specified]
- **Min size**: [if specified]
## Tone & Style
- **Voice**: [professional / casual / technical / creative]
- **Writing style**: [description]
## Document Rules
- **Presentations**: [specific rules for slides — backgrounds, layouts, etc.]
- **Reports**: [specific rules for written documents]
- **General**: [any other formatting rules]
## Do's and Don'ts
- ✅ [Do: specific guideline]
- ❌ [Don't: specific guideline]
Show the generated brand profile:
Here's your brand identity profile:
[show key points — colors, fonts, tone]
AskUserQuestion:
- "Looks good — save it"
- "Change something"
- "Start over"
After saving, offer to create a test artifact:
AskUserQuestion:
- "Create a sample 3-slide presentation with my brand"
- "Create a sample 1-page report with my brand"
- "Skip testing — I'll try it later"
If test requested, invoke the presentation or report-writer skill. After viewing the test output:
AskUserQuestion:
- "Looks great — brand is set up"
- "Adjust the colors"
- "Adjust the fonts"
- "Adjust the tone"
If ~/Tandem/dashboard.html exists, add a system activity entry:
{ "text": "Brand identity configured", "timestamp": "[now]", "type": "system" }
Document skills should check for ~/Tandem/memory/brand-profile.md before creating output.
If it exists, apply the specified colors, fonts, and style rules.
If it doesn't exist, use defaults and offer: "Want to set up your brand? Run /setup-brand."
Skills that reference brand-profile.md:
After brand setup completes:
AskUserQuestion:
- "Create a branded presentation"
- "Create a branded report"
- "Done for now"
When a document skill runs and brand-profile.md doesn't exist:
AskUserQuestion:
- "Set up my brand first (/setup-brand)"
- "Use defaults for now"