defining-brand-strategy
Skill1 starsChanged 3 months agoMITView on GitHub
Use when a new, repositioned, or inconsistent brand needs explicit audience, positioning, differentiation, personality, and decision criteria before naming, identity, or messaging work begins.
In this repository65 other files it gives its agents.
- analyzing-change-blast-radiusSkill
- analyzing-developer-career-opportunitiesSkill
- art-directing-web-interfacesSkill
- assessing-developer-proficiencySkill
- auditing-dependency-riskSkill
- auditing-pixel-perfect-frontendSkill
- bootstrapping-modern-web-appsSkill
- brag-slimSkill
- building-brand-guidelinesSkill
- building-conversion-product-pagesSkill
- building-developer-career-roadmapsSkill
- building-hybrid-game-assetsSkill
- building-premium-nextjs-interfacesSkill
- building-project-showcasesSkill
- building-regression-testsSkill
- building-reliable-node-api-boundariesSkill
- choosing-application-architectureSkill
- craft-premium-motionSkill
- creating-character-sprite-pipelinesSkill
- designing-action-combatSkill
- designing-developer-portfolio-evidenceSkill
- designing-relational-data-modelsSkill
- designing-software-boundariesSkill
- designing-test-strategiesSkill
- designing-ui-systemsSkill
- designing-visual-identitiesSkill
- documenting-architecture-decisionsSkill
- editing-for-clarity-and-toneSkill
- engineering-gsap-animationsSkill
- evaluating-developer-proficiencySkill
- evolving-postgres-schemas-safelySkill
- humanizing-generated-proseSkill
- implementing-reference-faithful-uiSkill
- investigating-codebase-semanticallySkill
- managing-implementation-slicesSkill
- mapping-existing-codebase-structureSkill
- naming-brands-and-productsSkill
- optimizing-frontend-motion-performanceSkill
- orchestrating-cinematic-web-motionSkill
- planning-codebase-changes-with-evidenceSkill
- planning-engineering-workSkill
- planning-launch-distributionSkill
- planning-safe-refactorsSkill
- planning-written-communicationSkill
- preparing-project-launchSkill
- profiling-postgres-query-performanceSkill
- reconstructing-images-as-threejsSkill
- reviewing-api-securitySkill
- reviewing-apple-platform-interfacesSkill
- reviewing-pull-requestsSkill
- reviewing-web-securitySkill
- selecting-working-methodsSkill
- shipping-github-vercel-changesSkill
- teaching-developer-conceptsSkill
- testing-integration-boundariesSkill
- testing-playable-gamesSkill
- testing-web-applications-end-to-endSkill
- threat-modeling-applicationsSkill
- tracing-code-execution-pathsSkill
- translating-figma-to-nextjsSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 17
Write the positioning. Clarify who the brand is for, the frame of reference, the meaningful difference, and the reason to believe it.
- Distinctive: line 19
Create brand principles and guardrails.
- Distinctive: line 39
Before handing off to downstream brand work, test the strategy against three decisions: one naming choice, one visual direction, and one …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Defining Brand Strategy
Core principle
Brand strategy is a decision system, not a moodboard. Convert evidence about the audience, category, offer, and business into constraints that make later naming, visual, and verbal choices easier to judge.
Strategy workflow
- Establish the assignment. State what is changing, why now, which business or product outcome matters, and what is outside scope.
- Separate evidence from assumption. Capture customer language, category expectations, stakeholder beliefs, product facts, and unanswered questions without flattening them into one narrative.
- Define the audience by situation and need. Prefer the problem, motivation, alternative, and buying or adoption context over broad demographic personas.
- Map the competitive frame. Identify the category users think they are choosing within, the conventions competitors repeat, and the spaces where meaningful distinction is possible.
- Define the value proposition and proof. State the useful promise, why it matters to the audience, and what evidence makes the promise credible.
- Write the positioning. Clarify who the brand is for, the frame of reference, the meaningful difference, and the reason to believe it.
- Define personality as behavioral attributes. For each attribute, state what it looks like in decisions and what would violate it. Avoid adjective piles such as “bold, modern, human” without operational meaning.
- Create brand principles and guardrails. Record what the brand should consistently express, what it must avoid, and which tensions it intentionally balances.
- Turn the strategy into evaluation criteria for naming, visual identity, and messaging. Later concepts should be judged against the strategy rather than stakeholder taste alone.
Strategy quality checks
A useful strategy should:
- distinguish facts, assumptions, and hypotheses;
- describe a real audience tension or job, not a fictional archetype;
- make the brand meaningfully different without claiming uniqueness that cannot be proved;
- connect differentiation to product or organizational reality;
- give creative teams enough constraint to reject plausible but off-strategy work;
- remain short enough to be used in decisions.
Avoid
- starting with logos, colors, archetypes, or taglines before the positioning problem is understood;
- treating a competitor moodboard as strategy;
- inventing purpose language unsupported by the organization;
- equating “premium”, “innovative”, or “authentic” with differentiation;
- forcing consensus by making the strategy so broad that every creative direction fits.
Verification
Before handing off to downstream brand work, test the strategy against three decisions: one naming choice, one visual direction, and one messaging choice. If the strategy cannot explain why one option fits better than another, its constraints are still too weak.
References
- Design Council, Double Diamond design process: https://www.designcouncil.org.uk/our-resources/the-double-diamond/
- Design Council, history and role of the Double Diamond: https://www.designcouncil.org.uk/resources/the-double-diamond/history-of-the-double-diamond/
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.

