정보
`brand-discovery` 스킬은 프로젝트의 타겟 고객, 경쟁 환경, 핵심 문제 영역을 명확히 하기 위한 기초적인 시장 조사를 수행합니다. 이 스킬은 프로젝트 시작 시점이나 크리에이티브 브리프에 필요한 핵심 입력 정보가 누락되었을 때 트리거됩니다. 이 스킬은 브랜드가 누구를 위한 것인지, 그들이 무엇을 필요로 하는지, 그리고 브랜드가 어디에서 독자적으로 위치를 잡을 수 있는지를 정의하는 데 도움을 줍니다.
빠른 설치
Claude Code
추천npx skills add rampstackco/claude-skills -a claude-code/plugin add https://github.com/rampstackco/claude-skillsgit clone https://github.com/rampstackco/claude-skills.git ~/.claude/skills/brand-discoveryClaude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요
문서
Brand Discovery
Upstream of every brief, identity, and content plan. Discovery answers four questions: who the brand is for, what they need, who else is competing for that need, and where the brand could plausibly stand that competitors do not.
When to use
- The very first phase of a new brand or website project
- Understanding an audience before any creative work begins
- Mapping competitors and category dynamics
- Surfacing the problem space the brand will operate in
- Generating positioning territories before brief or ideation
- When a creative brief was requested but the inputs are missing
When NOT to use
- The audience and category are already well-understood (jump to
creative-brieforbrand-ideation) - Validating a specific design or feature with users (use
usability-testing) - Mapping the customer journey of an existing audience (use
journey-mapping) - Generating brand names or visual directions (use
brand-ideation)
Required inputs
- The product, service, or organization being branded
- Whatever is already known about the audience and category (often very little)
- Access to existing materials (sales calls, support tickets, reviews, analytics)
- Any constraints (parent brand, regulatory, geographic)
- A timeline (a 1-week discovery looks different than a 6-week one)
The framework: 4 dimensions
Discovery covers four dimensions. Each has its own sources, methods, and outputs.
1. Audience
Who specifically does this serve?
Layers to surface:
- Demographic: Age range, geography, language, life stage, income (only if relevant; do not over-collect demographics)
- Psychographic: Values, motivations, beliefs, fears
- Behavioral: What they currently do to address the problem, what tools they use, where they spend time online and offline
- Jobs-to-be-done: The functional, emotional, and social jobs they hire a brand to perform
Sources:
- Existing customer interviews (5 to 8 ideal)
- Sales call recordings or transcripts
- Support ticket themes
- Review and forum analysis (Reddit, Trustpilot, App Store, niche communities)
- First-party analytics (search console queries, on-site search, top pages)
- Social listening (what they post about the category)
Output: 1 to 3 named audience segments, each with a one-page profile.
2. Competitors
Who else competes for the same audience and need?
Three layers of competitor:
- Direct: Solves the same problem the same way (e.g., another SaaS in the category)
- Indirect: Solves the same problem a different way (e.g., a spreadsheet replacing a SaaS tool)
- Status quo: Doing nothing, doing it manually, or living with the problem
The third is most often forgotten and most often the actual competitor.
Per competitor, document:
- Who they target (audience overlap with you)
- How they position (what they claim to be)
- What they actually deliver (often different from positioning)
- Pricing model and structure
- Strengths and weaknesses from the audience's perspective
- Recent moves (launches, pivots, hires, departures)
Sources:
- Their own website and marketing
- Reviews of their product or service
- Their content and SEO presence (use
seo-competitorfor the search angle) - Social proof and customer voices
Competitive scan benefits from quantitative grounding: not just "who are the competitors" but "how much traffic do they earn, where does it come from, who is the audience overlap." Similarweb is the standard for this kind of competitive landscape analysis; pair with Ahrefs for the SEO-specific overlap.
Output: Competitor matrix (3 to 8 competitors deep), plus a one-line "what makes them dangerous" for each.
3. Category and problem space
What is the broader context this brand operates in?
Map:
- The problem. What is the actual user problem? Not the surface symptom, the underlying job to be done.
- The category. How is the category structured? Is it new, mature, fragmenting, consolidating?
- The conventions. What does every brand in the category do the same way? (These are the conventions you can break.)
- The shifts. What is changing in the category? Technology, regulation, audience behavior, distribution.
- The moats. What protects incumbents? Brand, distribution, network effects, switching costs?
- The vocabulary. What language does the category use? What is jargon, what is meaningful, what is empty?
Sources:
- Industry reports and analyst coverage
- Trade publications and conferences
- Adjacent category observations
- Customer language vs. category language (the gap is informative)
Output: A category map and a list of conventions to consider breaking (or keeping deliberately).
4. Positioning territory
Given the audience, competitors, and category, where could this brand plausibly stand?
This is not yet "the positioning." Discovery surfaces possible territories. brand-ideation narrows them and commits.
Generate territories from:
- Underserved audience segments (audiences others ignore)
- Underserved jobs (jobs the category does not do well)
- Category convention violations (what would happen if you broke the rules everyone follows)
- Honest brand truths (what is genuinely true about this brand that competitors cannot also claim)
- Category shifts (where the puck is going)
Per territory, document:
- The statement (one sentence)
- Why it could work (proof point)
- Who would resonate (the audience for this territory)
- Who is competing in this territory (often, no one good)
- Risk (what makes it fragile)
Output: 3 to 5 distinct territories. Not yet committed. Inputs to brand-ideation.
Workflow
- Define the discovery scope. 1 week for a startup pre-launch. 4 to 6 weeks for a major rebrand. Set expectations.
- Audit existing inputs. Sales calls, support tickets, reviews, analytics, internal docs. Often more is known than people think.
- Audience research. 5 to 8 interviews if possible. Plus secondary research from review and forum analysis.
- Competitor mapping. 3 to 8 competitors deep, including indirect and status-quo competitors.
- Category mapping. Conventions, shifts, vocabulary, moats.
- Territory generation. 3 to 5 plausible positioning territories.
- Write the discovery report. Use the template in
references/discovery-report-template.md. - Hand off to next phase. Discovery feeds into
creative-brief,brand-ideation, orcontent-strategydepending on where the project goes next.
Failure patterns
- Skipping discovery to "save time." Every shortcut here costs 10x downstream when the brand fails to land.
- Audience research that confirms what you already believe. If your audience research validates every assumption, you did not actually research. Look for surprises.
- Demographic-heavy audience profiles. "Women aged 25 to 45" is not insight. Behavior, beliefs, and jobs-to-be-done are.
- Listing every competitor as if equal. Most competitors do not matter. Pick the 3 that are genuinely dangerous.
- Forgetting status-quo as competition. The biggest competitor is usually "doing nothing" or "doing it manually."
- Outputting territories without rejection criteria. A territory without a "what this rejects" is not a territory.
- Treating discovery as a one-time event. Categories shift. Audiences evolve. Re-run discovery at least every 3 years.
Output format
Default output is a discovery report at discovery-report.md plus appendices.
Structure:
- Executive summary (5 to 10 bullets)
- Audience (1 to 3 named segments with profiles)
- Competitors (matrix and per-competitor analysis)
- Category and problem space
- Positioning territories (3 to 5 candidates)
- Implications and recommendations
- Open questions that require further research
Appendices:
- Interview notes (sanitized)
- Competitor research data
- Source list
If required data is unavailable
This skill's output depends on data, measurements, or tool results it cannot generate on its own. When a required input, tool, or data source is unavailable or unverifiable, the sanctioned output is the deliverable with the gap stated: what was needed, what was actually obtained or verified, and which parts of the output are affected. Fabricating, estimating, or interpolating a required number to complete the deliverable is never sanctioned. A stated gap is a complete answer.
Reference files
references/discovery-report-template.md- Full discovery report template.references/interview-guide.md- Audience interview guide with question prompts.
GitHub 저장소
자주 묻는 질문
brand-discovery Skill이란 무엇인가요?
brand-discovery은(는) rampstackco이(가) 만든 Claude Skill입니다. Skill은 Claude가 필요할 때 불러오는 지침과 리소스를 묶어 추가 프롬프트 없이 brand-discovery 관련 작업을 수행할 수 있게 합니다.
brand-discovery은(는) 어떻게 설치하나요?
이 페이지의 설치 명령을 사용하세요. brand-discovery을(를) Claude Code 플러그인으로 추가하거나 저장소를 skills 디렉터리에 복제한 다음 Claude를 다시 시작해 Skill을 불러옵니다.
brand-discovery은(는) 어떤 카테고리에 속하나요?
brand-discovery은(는) 메타 카테고리에 속합니다.
brand-discovery은(는) 무료로 사용할 수 있나요?
네. brand-discovery은(는) AIMCP에 등록되어 있으며 무료로 설치할 수 있습니다.
연관 스킬
이 스킬은 콘텐츠 콜렉션(Content Collections)을 위한 프로덕션 검증된 설정을 제공합니다. 콘텐츠 콜렉션은 Markdown/MDX 파일을 Zod 검증이 포함된 타입 안전한 데이터 콜렉션으로 변환해주는 TypeScript 최우선 도구입니다. 블로그, 문서 사이트 또는 콘텐츠 중심의 Vite + React 애플리케이션을 구축할 때 타입 안전성과 자동 콘텐츠 검증을 보장하기 위해 사용하세요. Vite 플러그인 구성과 MDX 컴파일부터 배포 최적화 및 스키마 검증에 이르기까지 모든 것을 다룹니다.
이 스킬은 개발자들이 Polymarket 예측 시장 플랫폼을 활용한 애플리케이션을 구축할 수 있도록 지원하며, 거래 및 시장 데이터를 위한 API 통합 기능을 포함합니다. 또한 WebSocket을 통한 실시간 데이터 스트리밍을 제공하여 실시간 거래와 시장 활동을 모니터링할 수 있습니다. 이를 통해 거래 전략을 구현하거나 실시간 시장 업데이트를 처리하는 도구를 생성하는 데 활용할 수 있습니다.
이 스킬은 개발자들이 명령어, 파일, LSP 작업 등 25개 이상의 이벤트 유형에 연결되는 OpenCode 플러그인을 만들 수 있도록 돕습니다. JavaScript/TypeScript 모듈을 위한 플러그인 구조, 이벤트 API 명세, 구현 패턴을 제공합니다. OpenCode AI 어시스턴트의 라이프사이클을 사용자 정의 이벤트 기반 로직으로 가로채거나, 모니터링하거나, 확장해야 할 때 사용하세요.
SGLang은 RadixAttention 프리픽스 캐싱을 활용하여 JSON, 정규식, 에이전트 워크플로우를 위한 고속 구조화 생성에 특화된 고성능 LLM 서빙 프레임워크입니다. 특히 반복되는 프리픽스가 있는 작업에서 상당히 빠른 추론 속도를 제공하여 복잡한 구조화 출력 및 다중 턴 대화에 이상적입니다. 제약 디코딩이 필요하거나 광범위한 프리픽스 공유가 있는 애플리케이션을 구축할 때는 vLLM과 같은 대안보다 SGLang을 선택하십시오.
