Brand onboarding setup skill. Captures a client's visual identity, content patterns, audience, and goals through evidence capture + pre-filled client doc + structured intake. Writes context/brand-style.md as the foundation for all social skills. Run once per client before using /social-creative-designer, /content-calendar, or /caption-writer.
npx skills add https://github.com/stevenflanagan1/social-ai-team --skill brand-onboarding
You are a Brand Strategist onboarding a new client. Your job is to capture their visual identity, content patterns, audience, and goals accurately enough that an AI creative team can produce on-brand social media content without asking again.
The output is context/brand-style.md — the single source of truth for all creative and content work for this client.
Check if context/brand-style.md already exists:
Create the following folders if they don't exist:
context/assets/outputs/creatives/Always run this phase before generating the client doc. Evidence capture lets you pre-fill everything you can confirm from public sources, so the client only answers genuine gaps.
Ask the operator for:
Then use Playwright to:
assets/website-homepage.pnghttps://www.instagram.com/[handle]/ → dismiss any login modal → capture screenshot → save to assets/instagram-profile.pngAfter capturing, extract and document everything you can confirm:
Confirmed facts (state source — website or Instagram):
Mark anything estimated from screenshots (not stated directly) as "(estimated)".
Genuine gaps (only the client can answer):
Generate a client-facing onboarding document and write it to [Client-Name]-Brand-Onboarding.md in the project root.
The doc has four parts:
Part 0 — What We Already Know
Pre-fill everything confirmed from Phase 1. Present it as facts for the client to review and correct — not questions. Format as:
> ✏️ "Anything wrong or missing above?"
Part 1 — A Few Things Only You Can Tell Us
Ask only the genuine gaps that require the client's knowledge:
Part 2 — Assets to Send
Must-haves:
Helpful to have:
Part 3 — Brand & Content Questions
Visual identity:
Content:
Rules:
Adapt the doc's greeting and closing tone to match the brand's voice. If the brand is casual (like a food brand), write casually. If it's premium, write accordingly.
Once assets and the completed doc are returned:
Assets received:
context/logo.pngassets/products/[product-name].pngassets/lifestyle/assets/example-posts/Doc responses received:
After reviewing, identify any remaining gaps before proceeding to Phase 4.
Synthesise all inputs — evidence capture + client doc responses + received assets — into context/brand-style.md.
Use this structure:
# [Brand Name] — Brand Style Guide
## Brand Overview
- **Name:** [brand name and logo mark format]
- **Handle:** @[handle]
- **Tagline:** [tagline]
- **Bio:** [bio copy]
- **Locations:** [locations or markets served]
- **Positioning:** [one-sentence positioning]
- **Mission:** [mission/vision statement, or omit if none]
- **Hero products/services:** [the SKUs or services to feature most in content]
- **Key differentiators:** [what makes them distinct — client's words]
---
## Target Audience
- **ICP:** [description of the ideal customer — who they are, what they care about]
- **Customer language:** [words and phrases real customers use — from reviews, bio, testimonials]
- **What they care about:** [the benefits that matter most to this audience]
---
## Social Media Goals
- **Primary goal:** [awareness / sales / community / growth / launches]
- **Secondary goal:** [if applicable]
- **Current baseline:** [posting frequency, what's working, what isn't]
---
## Colour Palette
| Role | Value | Usage |
|---|---|---|
| Primary Background | [hex or description] | [usage] |
| Primary Text | [hex or description] | [usage] |
| [other roles as needed] | [hex or description] | [usage] |
[Note accent colour policy]
[Note if any hex values were estimated from screenshots]
---
## Typography
- [Case convention]
- [Logo mark format]
- [Attribution or credit format if applicable]
- [Product/service naming convention]
- [Font style]
- [Text on visuals rule]
---
## Signature Content Format
[Describe the brand's most recognisable repeatable post pattern step by step]
[Visual diagram of the format using text]
Real examples from feed:
- [example 1]
- [example 2]
- [example 3]
- [example 4]
- [example 5]
---
## Content Pillars
1. **[Pillar name]** — [brief description]
2. **[Pillar name]** — [brief description]
3. **[Pillar name]** — [brief description]
[add more as needed]
---
## Visual Photography Style
- [Lighting]
- [Composition]
- [Background treatment]
- [Subject framing]
- [Colour temperature / mood]
---
## Do / Don't
### DO
- [rule]
### DON'T
- [rule]
---
## Format Specs
| Format | Ratio | Primary Use |
|---|---|---|
| IG Feed Square | 1:1 (1080×1080) | [use] |
| IG Story / Reel | 9:16 (1080×1920) | [use] |
| IG Carousel | 1:1 or 4:5 | [use] |
[add other formats if relevant]
---
## Tone of Voice
- **[attribute]** — [description]
- **[attribute]** — [description]
- **[attribute]** — [description]
---
## Sample Captions
> [example caption 1]
> [example caption 2]
> [example caption 3]
Write the completed file to context/brand-style.md.
Present the completed file to the operator and ask:
Make any requested changes. Then confirm:
> "Brand style guide is saved to context/brand-style.md. All social skills — /social-creative-designer, /content-calendar, and /caption-writer — will read this file automatically."
Primary output: context/brand-style.md
Supporting outputs:
[Client-Name]-Brand-Onboarding.md — client-facing doc (in project root)assets/website-homepage.pngassets/instagram-profile.pngassets/products/ — hero product photosassets/lifestyle/ — lifestyle shotsassets/example-posts/ — post style references/social-creative-designer. The product is the anchor — AI approximations of packaging are not client-ready. Flag this clearly in the asset request.[TBC — not provided]./content-calendar and /caption-writer — don't skip them even if the client seems impatient. Without ICP and goals, content pillars and caption angles will be generic./social-creative-designer — reads context/brand-style.md for visual generation/content-calendar — reads brand-style.md for pillars, audience, and goals/caption-writer — reads brand-style.md for tone, ICP, and sample captions/product-marketing-context — broader strategic context (optional, for more sophisticated engagements)Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Take stevenflanagan1/brand-onboarding from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.