Menu
Use when creating or refining a brand - guides naming, voice and tone, brand story, visual direction, and brand principles
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | brand-identity |
| description | Use when creating or refining a brand - guides naming, voice and tone, brand story, visual direction, and brand principles |
Define the brand's name, voice, tone, story, and visual direction. Produces a brand guide that downstream skills reference for consistent messaging.
Announce at start: "I'm using the brand-identity skill to define the brand."
Step 1: Context gathering
docs/marketing/market-research.md, docs/marketing/customer-personas.mdStep 2: Five areas, one at a time
Present and validate each area before moving to the next:
Naming (skip if product already has a name)
Brand story
Voice & tone
Visual direction
Brand principles
Step 3: Write output
docs/marketing/brand-identity.mdStep 4: Handoff
globalcoder-marketing:positioning-strategyUse when executing an implementation plan with four or more independent tasks touching different files, via the experimental agent-teams flag — parallel implementer teammates plus continuous async reviewers. Higher token cost; requires CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1.
Use when starting creative work — adding features, building components, adding functionality, modifying existing behavior, or any time the user describes a new idea or capability they want to build.
Use when adding, modifying, or removing database tables, columns, indexes, views, functions, or RLS policies — any schema change targeting a shared or production database
Use when facing two or more independent investigations or research tasks in the current session — debugging multiple unrelated failures, exploring different solution approaches, or running parallel reads. Not for executing implementation plans (use subagent-driven-development, agent-team-development, or tmux-parallel-development for those).
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup