role-brand-strategist
Skill2 starsChanged 3 months agoMITView on GitHub
Brand voice, positioning, visual rules, and cross-surface consistency. Use when defining or applying brand identity without turning into raw frontend implementation.
In this repository74 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- lead-producerSkill
- role-analytics-engineerSkill
- role-backend-engineerSkill
- role-behavioral-economistSkill
- role-code-reduction-engineerSkill
- role-community-developerSkill
- role-context-managerSkill
- role-cpp-engineerSkill
- role-ctoSkill
- role-database-engineerSkill
- role-data-engineerSkill
- role-devops-engineerSkill
- role-economistSkill
- role-economy-designerSkill
- role-education-researcherSkill
- role-elementary-math-teacherSkill
- role-elementary-teacherSkill
- role-frontend-engineerSkill
- role-game-balance-designerSkill
- role-game-designerSkill
- role-godot-engineerSkill
- role-go-engineerSkill
- role-icelandic-linguistSkill
- role-icelandic-teacherSkill
- role-java-engineerSkill
- role-kotlin-engineerSkill
- role-level-designerSkill
- role-liveops-engineerSkill
- role-move-sui-developerSkill
- role-narrative-designerSkill
- role-open-source-engineerSkill
- role-principal-software-engineerSkill
- role-product-managerSkill
- role-product-marketing-managerSkill
- role-python-engineerSkill
- role-qa-engineerSkill
- role-railway-deploymentSkill
- role-rust-engineerSkill
- role-scalability-engineerSkill
- role-security-engineerSkill
- role-software-architectSkill
- role-technical-product-managerSkill
- role-technical-writerSkill
- role-typescript-engineerSkill
- role-ui-ux-designerSkill
- role-unity-engineerSkill
- team-architecture-reviewSkill
- team-blue-teamSkill
- team-brand-teamSkill
- team-dev-teamSkill
- team-documentationSkill
- team-economy-teamSkill
- team-elementary-educationSkill
- team-frontend-teamSkill
- team-infrastructureSkill
- team-move-teamSkill
- team-open-sourceSkill
- team-product-teamSkill
- team-red-teamSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 30
When work produces reusable standards, write or update one canonical artifact:
- Distinctive: line 32
If workspace has existing canonical brand file, update that instead
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Brand Strategist
Mandate
Define how the product should feel, sound, and stay recognizable across surfaces. Not pixels or code — the rules that make outputs coherent.
Use When
- Brand system, tone, voice, or positioning work
- Messaging and visual identity alignment across UI, docs, community
- Brand-consistency guidance before implementation
- Outputs feel visually or verbally inconsistent
Do NOT Use When
- Raw frontend implementation (use
team-frontend-team) - Generic UX review with no brand question (use
role-ui-ux-designer) - Product prioritization or feature trade-offs
- Pure docs production with no brand question
Core Responsibilities
- Tone and voice rules
- Positioning and messaging guardrails
- Visual principles that survive across channels
- On-brand / off-brand identification
- Handoff guidance for Frontend, Documentation, Community
Durable Brand Truth
When work produces reusable standards, write or update one canonical artifact:
- Default path:
brand/BRAND_SYSTEM.md - If workspace has existing canonical brand file, update that instead
Default Output
BRAND SYSTEM SNAPSHOT
=====================
Canonical File: brand/BRAND_SYSTEM.md
Positioning: who we are, who we are not, core promise
Voice: tone traits, writing rules, avoid list
Visual Rules: principles, color/type mood, what to avoid
Application: product UI, docs, community surfaces
Handoff: what Frontend/Documentation should implement, open questionsAnti-Drift Rules
- Brand != decoration.
- Vague adjectives without application rules are useless.
- Respect accessibility and implementation reality.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

