Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计通过

category-design品类设计

Agent Skill

用于辅助界面设计、视觉规范、排版、配色、布局和交互体验优化。它适合让 Agent 根据产品场景整理页面结构、生成 UI 方案、检查视觉一致性或改进组件层级。使用时需要结合现有品牌、设计系统和用户任务,不应只堆装饰元素;涉及真实页面改动时,应通过截图或浏览器预览检查文本溢出、对齐和响应式表现。

总安装

1,988

周安装

82

GitHub Stars

85

下载量

649
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:category-design(品类设计)
来源仓库:https://github.com/guia-matthieu/clawfu-skills
仓库路径:skills/category-design
安装命令:
npx skills add https://github.com/guia-matthieu/clawfu-skills --skill category-design
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/guia-matthieu/clawfu-skills --skill category-design

简介

category-design 协助创建新品类或重构市场定位,通过重新定义需求边界来避开红海竞争,建立差异化叙事。

  • 适用于创业立项、产品转型或品牌重塑场景,帮助提炼非顾客、扩展使用情境与构建价值阶梯。
  • 输出包含品类定义、机会窗口与沟通框架,强调从用户真实痛点出发而非功能堆砌。
  • 使用时需提供现有竞争格局与用户反馈,避免凭空造概念;建议结合调研数据验证假设。
  • 本技能侧重战略构思,具体执行仍需配套产品设计与营销落地,不可单独作为上市依据。

SKILL.md

Category Design - Create and Dominate New Markets

Become the Category King by creating new markets instead of competing in existing ones

When to Use This Skill

  • Launching a company or product that doesn't fit cleanly into existing categories
  • Stuck in commodity competition where you're compared feature-to-feature with competitors
  • Redefining your market position when "better" isn't working as a strategy
  • Planning a major market announcement or product launch
  • Escaping price pressure by creating net new demand instead of fighting for existing pie
  • Building your company narrative for investors, employees, and customers
  • Feeling like you're losing to entrenched incumbents despite having a superior solution

Methodology Foundation

AspectDetails
SourcePlay Bigger: How Pirates, Dreamers, and Innovators Create and Dominate Markets (2016)
ExpertsAl Ramadan, Dave Peterson, Christopher Lochhead, Kevin Maney
Core Principle"Companies that design and dominate new categories capture 76% of the total market value. Being better isn't enough—you must be different."

What Claude Does vs What You Decide

Claude DoesYou Decide
Structures analysis frameworksStrategic priorities
Synthesizes market dataCompetitive positioning
Identifies opportunitiesResource allocation
Creates strategic optionsFinal strategy selection
Suggests implementation approachesExecution decisions

What This Skill Does

This skill helps you escape the trap of "better" and create something "different." Most companies fail because they try to out-compete entrenched incumbents on their terms. Category Design flips the script.

Instead of fighting for scraps in existing markets, you'll:

  1. Find problems others don't see - Identify costly problems hidden in plain sight
  2. Design the category - Create the rules that favor you
  3. Condition the market - Make your problem feel urgent and your solution inevitable
  4. Execute Lightning Strikes - Launch in ways that change how people think
  5. Become the Category King - Capture 76% of market value, not 24%

The result: You stop competing and start creating markets where you make the rules.

How to Use

Prompt Examples

Help me identify if my product/company is a true category creator or just a "better" competitor.
Here's what we do: [description]. Walk me through the category design diagnostic.
I'm competing in [existing category] against [competitors]. Help me find a new category
framing that makes our competition irrelevant. Use the Play Bigger methodology.
Write a POV (Point of View) document for my company using the category design format.
Our product: [description]. Our audience: [audience]. The problem we solve: [problem].
Plan a Lightning Strike for launching our new category. We have [budget] and [timeframe].
Include event strategy, PR, content, and sales enablement components.
Create a Category Blueprint for [my product/service] that shows how all the components
work together as a unified category solution.

Instructions

The Category Design Framework

┌─────────────────────────────────────────────────────────────┐
│         THE THREE PILLARS OF CATEGORY CREATION              │
├─────────────────────────────────────────────────────────────┤
│                                                             │
│    PRODUCT DESIGN     COMPANY DESIGN     CATEGORY DESIGN    │
│    ──────────────     ──────────────     ──────────────     │
│    Solves the         Creates culture    Battle for         │
│    category           and org that       public opinion     │
│    problem            supports both      about the problem  │
│                                                             │
│         ↓                   ↓                   ↓           │
│                                                             │
│                  ALL THREE MUST ALIGN                       │
│                                                             │
└─────────────────────────────────────────────────────────────┘

The Five Golden Rules

Before starting, internalize these principles:

RuleWhat It Means
1. Fight the status quo, not competitionMake what competitors do irrelevant, not inferior
2. Know who it's for (and who it's not)Narrow focus creates stronger category claim
3. See problems others can'tThe best problems are hidden in plain sight
4. Solve with a vision for the futurePaint a compelling picture of what's possible
5. Frame it. Name it. Claim it.Own the language and definition

Step 1: Find the Problem

The problem is the foundation. Without the right problem, there is no category.

Requirements for a category-worthy problem:

RequirementTest
Unsolved or poorly solvedCurrent solutions have significant gaps
CostlyNot solving it costs time, money, reputation, or opportunity
WidespreadEnough people have it to create a market
Creates an "aha" momentWhen framed correctly, people immediately recognize it
Non-obviousIf it were obvious, incumbents would have solved it

Category Potential Formula:

CP = Pr × P

CP = Category Potential
Pr = Number of people/companies with the problem
P  = What they're willing to pay to solve it

Example:

  • 500,000 companies have the problem
  • They'd pay $5,000/year to solve it
  • CP = $2.5B annual category potential

Problem Discovery Questions:

  1. What do our best customers complain about that we thought was "just how it is"?
  2. What takes our customers 10x longer than it should?
  3. What are our customers apologizing to THEIR customers about?
  4. What would our customers' CEO care about that their current vendors can't solve?
  5. If we could wave a magic wand, what reality would we create?

Step 2: Name the Category

The name unifies all your solution components into a single concept.

Good Category Names:

  • Content Streaming (Netflix)
  • Experience Management (Qualtrics)
  • Ridesharing (Uber)
  • Connectivity Cloud (Cloudflare)

Naming Principles:

PrincipleExplanation
Single-mindedOne name, not a Lego set of features
SearchablePeople will eventually Google this
OwnableYou can claim it and defend it
ExpandableRoom to grow without renaming
IntuitiveNew people get it quickly

Naming Exercise: Complete this sentence: "We invented _____________ so that [customer] can [outcome]."


Step 3: Create the Category Blueprint

The Blueprint shows how your category works—not just your product, but the entire category ecosystem.

Blueprint Components:

┌─────────────────────────────────────────────────────────────┐
│                    [CATEGORY NAME]                          │
├─────────────────────────────────────────────────────────────┤
│                                                             │
│  ┌─────────────┐    ┌─────────────┐    ┌─────────────┐     │
│  │  COMPONENT  │ ↔  │  COMPONENT  │ ↔  │  COMPONENT  │     │
│  │     ONE     │    │     TWO     │    │    THREE    │     │
│  └─────────────┘    └─────────────┘    └─────────────┘     │
│         ↕                 ↕                  ↕              │
│  ┌───────────────────────────────────────────────────┐     │
│  │              DATA / INTELLIGENCE LAYER            │     │
│  └───────────────────────────────────────────────────┘     │
│         ↕                 ↕                  ↕              │
│  ┌─────────────┐    ┌─────────────┐    ┌─────────────┐     │
│  │   OUTCOME   │    │   OUTCOME   │    │   OUTCOME   │     │
│  │     ONE     │    │     TWO     │    │    THREE    │     │
│  └─────────────┘    └─────────────┘    └─────────────┘     │
│                                                             │
└─────────────────────────────────────────────────────────────┘

Why the Blueprint Matters:

  • Defines what a "complete" solution looks like
  • Forces competitors to match your definition
  • Educates customers on what to demand from vendors
  • Creates the "RFP" for your category

Step 4: Write Your POV (Point of View)

The POV is the single most important deliverable. It arms your company with a unique perspective that conditions the market.

POV Structure:

## [Category Name] POV

### 1. Context
What's happening in the world that sets the stage for this problem?
[2-3 sentences about trends, shifts, changes]

### 2. The Problem
What problem hasn't been solved—or hasn't been solved well?
[Describe in visceral, specific terms]

### 3. The Villain
What's the shorthand name for this problem?
"The [X] Gap" / "The [X] Crisis" / "[X] Chaos"

### 4. Why Current Approaches Fail
Why haven't existing solutions worked?
[2-3 specific reasons with evidence]

### 5. The Costs
What are the specific, quantifiable costs of not solving this?
- Cost 1: [$ or % impact]
- Cost 2: [$ or % impact]
- Cost 3: [$ or % impact]

### 6. Our Vision for the Future
What does the world look like when this problem is solved?
[Paint a compelling picture]

### 7. The Category
We call this [CATEGORY NAME].
[One sentence definition]

### 8. How It Works (Blueprint)
[Walk through the components and how they connect]

### 9. Outcomes
When companies/people adopt [CATEGORY NAME], they get:
- Outcome 1
- Outcome 2
- Outcome 3

### 10. Call to Action
Here's what you can do right now:
[Specific next step]

Step 5: Mobilize the Company

Everyone must align behind the category. This is CEO-driven.

Mobilization Checklist:

  • POV presented to entire company
  • Every team understands how their work supports the category
  • Sales has new talk tracks aligned to POV
  • Marketing has new messaging and content
  • Product roadmap reflects category vision
  • Recruiting looks for category believers
  • "Zeds" (skeptics) given chance to buy in or exit

Gravity Warning: "Gravity" is the day-to-day grind that pulls you back to old ways—current customer demands, existing sales motions, quarterly targets. You must actively fight gravity to create a new category.


Step 6: Execute Lightning Strikes

Lightning Strikes are coordinated moments of maximum impact that establish your category leadership.

Lightning Strike Components:

ComponentPurpose
EventCenterpiece (your event or hijacked conference)
PRMajor media coverage timed to event
WebsiteComplete refresh with new messaging
ContentBlueprint, POV, thought leadership
Sales EnablementNew decks, battlecards, talk tracks
ProductFeature or milestone announcement
Analyst RelationsBriefings to create coverage

Timing:

  • 2 Lightning Strikes per year maximum
  • 80% of marketing budget to strikes
  • 3-6 months to prepare properly

Success Metric:

"A lightning strike is an efficient way to start altering brain patterns and establish the idea that your company is the category leader."

Examples

Example 1: B2B SaaS Repositioning

Before (Competing): "We're a project management tool that's faster and more intuitive than Monday.com and Asana."

After (Category Design):

Problem Identified: Remote teams waste 30% of their time on "work about work"—status updates, finding information, and coordinating across time zones.

Category Name: Async Work Intelligence

POV Excerpt:

"We live in a world where work happens across time zones, yet our tools were built for everyone being in the same office at the same time. The result? 'Work about work' has exploded. Remote workers spend 30% of their day just figuring out what's happening. We call this the Sync Tax. Traditional project management tools try to organize the chaos. But they don't solve it—they systematize it. What if instead of better ways to coordinate, we could eliminate the need to coordinate at all? We call this Async Work Intelligence—a new category of software that eliminates the Sync Tax by making work self-aware. Projects know their own status. People know what matters without asking. And the 30% comes back to actual work."

Blueprint:

  • AI Status Layer (automatic progress detection)
  • Async Communication Hub (time-zone-aware messaging)
  • Decision Intelligence (who needs to know what, when)
  • Work Graph (relationship between tasks, people, time)

Example 2: Consumer Product Launch

Before (Competing): "We make premium athletic wear that's more sustainable than Lululemon."

After (Category Design):

Problem Identified: Athletes want to perform AND live their values, but "sustainable" athletic wear means compromising performance.

Category Name: Performance Activism

POV Excerpt:

"A new generation of athletes has emerged. They train hard AND care deeply. They want to perform at their best AND leave the world better. But every brand forces a choice: performance OR values. 'Sustainable' athletic wear uses recycled materials that absorb sweat, stretch weird, and fall apart in months. Performance wear uses plastics that will outlive your grandchildren. We rejected this choice. We call it Performance Activism—apparel that performs at the elite level while actively healing the planet. Not 'less bad.' Actually regenerative. Every piece sequesters carbon. Every purchase restores ecosystems. And it out-performs any synthetic."

Checklists & Templates

Category Potential Assessment

## Category Potential Assessment: [Idea/Product]

### The Problem
**Problem Statement**:
[One sentence]

**Who Has It**:
- Segment 1: [# of people/companies]
- Segment 2: [# of people/companies]
- Total Addressable: [total]

**Costs of Not Solving**:
- Direct cost: $___/year
- Indirect cost: $___/year
- Opportunity cost: $___/year

**Willingness to Pay**:
- Low estimate: $___/year
- Mid estimate: $___/year
- High estimate: $___/year

### Category Potential Calculation
CP = [# with problem] × [$ willing to pay]
CP = ___ × $___
**CP = $___/year**

### Problem Quality Check
- [ ] Unsolved or poorly solved currently?
- [ ] Creates visceral reaction when described?
- [ ] CEO-level concern (not just department)?
- [ ] Getting worse over time (not better)?
- [ ] Non-obvious to incumbents?

POV Document Template

# [Category Name]: Point of View

## The World Is Changing
[2-3 sentences on macro trends creating the problem]

## The Problem
[Problem described in visceral, human terms]

### The [Villain Name]
[One-line definition of the shorthand villain]

**The Costs**:
| Impact | Annual Cost |
|--------|-------------|
| [Impact 1] | $X or X% |
| [Impact 2] | $X or X% |
| [Impact 3] | $X or X% |

## Why Current Solutions Fail
### [Current Approach 1]
[Why it doesn't work]

### [Current Approach 2]
[Why it doesn't work]

## A New Way: [Category Name]
[One paragraph vision of the future]

### How It Works
[Blueprint description with components]

## The Outcomes
When [customers] adopt [Category Name]:
1. [Outcome 1 - specific and measurable]
2. [Outcome 2 - specific and measurable]
3. [Outcome 3 - specific and measurable]

## Take the First Step
[Clear call to action]

Lightning Strike Planning Template

## Lightning Strike Plan: [Event/Launch Name]

### Timing
- Strike Date: [date]
- Prep Begins: [date - usually 3-6 months prior]

### Centerpiece Event
- What: [conference, webinar, launch event]
- Where: [location/platform]
- Expected Attendance: [number]

### Pre-Strike Checklist
**30 Days Before**:
- [ ] POV finalized and approved
- [ ] Website updates ready to deploy
- [ ] PR embargo packages sent
- [ ] Sales enablement complete
- [ ] Product milestone confirmed

**7 Days Before**:
- [ ] All teams briefed
- [ ] Content queued
- [ ] Analyst briefings scheduled
- [ ] Customer quotes secured
- [ ] Social campaign ready

### Day-Of Execution
- [ ] Website goes live: [time]
- [ ] Press release drops: [time]
- [ ] Social campaign launches: [time]
- [ ] Email blast: [time]
- [ ] Event begins: [time]

### Post-Strike (72 Hours)
- [ ] Follow-up emails
- [ ] Retargeting activated
- [ ] Sales follow-up begins
- [ ] Media coverage tracking
- [ ] Social engagement response

### Success Metrics
- Media mentions: [target]
- Website traffic: [target]
- Leads generated: [target]
- Social engagement: [target]
- Category name mentions: [target]

Skill Boundaries

What This Skill Does Well

  • Structuring strategic analysis
  • Identifying market opportunities
  • Creating strategic frameworks
  • Synthesizing competitive data

What This Skill Cannot Do

  • Replace market research
  • Guarantee strategic success
  • Know proprietary competitor info
  • Make executive decisions

References

  • Book: Play Bigger by Al Ramadan, Dave Peterson, Christopher Lochhead, Kevin Maney
  • Website: PlayBigger.com
  • Research: Harvard Business Review on Category Kings
  • Source: sources/books/play-bigger-category-design.md

Related Skills

  • positioning-dunford - How positioning fits within category design
  • sales-pitch-dunford - The sales narrative for category leaders
  • storybrand-framework - Storytelling for category POVs
  • grand-slam-offers - Offer design for category-creating products
  • made-to-stick - Making your category message memorable

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Claude

33.12%
按下载量换算215

Codex

32.69%
按下载量换算212

Cursor

21.23%
按下载量换算138

Gemini CLI

9.21%
按下载量换算60

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills