team-brand-team
Skill2 starsChanged 3 months agoMITView on GitHub
Brand system team: tone, positioning, visual rules, and cross-surface identity standards. Use when defining or tightening brand consistency across product, docs, and community.
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-brand-strategistSkill
- 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-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
3 rules. About 0 are common, 2 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 35
Write/update canonical brand artifact (default brand/BRAND_SYSTEM.md).
- Distinctive: line 52
When brand aspiration conflicts with implementation reality, find the smallest brand adaptation that maintains identity.
- Distinctive: line 56
Do not expand into product strategy under brand review label.
≈ “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 Team
Purpose
Own identity standards, not raw implementation. Turn vague taste questions into a usable system other teams can apply consistently.
Composition
- role-brand-strategist: brand voice, positioning, visual rules
- role-ui-ux-designer: ensures brand works in real interfaces
- role-technical-writer: verbal guidance portable into docs and copy
- role-community-developer: brand survives community-facing surfaces
- Synthesis: trade-offs, keeps team lean
- role-frontend-engineer (optional): when implementation realism matters
Use When
- Defining a brand system
- Aligning voice and visual identity across product, docs, community
- Applying brand standards for launch, redesign, or new surface
- Resolving UI/docs/messaging inconsistency
Do NOT Use When
- Raw frontend implementation (use
team-frontend-team) - Feature prioritization (use
team-product-team) - Pure docs with no brand question (use
team-documentation)
Workflow
- Define or load brand truth from one canonical file.
- Align voice, visuals, cross-surface rules.
- Stress-test against actual UI, docs, community usage.
- Write/update canonical brand artifact (default
brand/BRAND_SYSTEM.md). - Produce small implementation handoff.
Default Output
BRAND TEAM BRIEF
================
Canonical File: brand/BRAND_SYSTEM.md
Brand Truth: positioning, voice, visual principles
Consistency Risks: current mismatches, surfaces likely to drift
Application Rules: product UI, docs, community/ecosystem
Handoff: frontend actions, documentation actions, open constraintsConflict Resolution
- Brand Strategist owns voice, positioning, and visual rules. UI/UX Designer owns interface feasibility.
- Technical Writer owns verbal specificity. Community Developer owns community-surface applicability.
- When brand aspiration conflicts with implementation reality, find the smallest brand adaptation that maintains identity.
Anti-Drift Rules
- Brand is rules, not decoration. If output is vague adjectives without application guidance, it failed.
- Do not expand into product strategy under brand review label.
- One canonical brand file, not multiple competing sources of truth.
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.

