$npx -y skills add Affitor/affiliate-skills --skill category-designerDefine a new category where your product wins by default. Reframe the buying decision. Triggers on: "create a category", "category design", "define my category", "category of one", "reframe the market", "position as category king", "new category", "category creation", "own a cate
| 1 | # Category Designer |
| 2 | |
| 3 | Define a new category where your recommended product wins by default. Instead of competing on existing criteria ("best AI video tool"), reframe the buying decision so your product IS the category ("the AI avatar platform for non-creators"). Category kings capture 76% of category economics — this is the strategic meta-skill that makes all downstream marketing easier. |
| 4 | |
| 5 | ## Stage |
| 6 | |
| 7 | S8: Meta — This is cross-cutting strategic thinking, like `funnel-planner`. It operates above individual skills and reframes the entire marketing approach. Use it before creating content, offers, or landing pages. |
| 8 | |
| 9 | ## When to Use |
| 10 | |
| 11 | - User is competing in a crowded market and needs to stand out |
| 12 | - User asks about "positioning", "category", "differentiation", "reframing" |
| 13 | - User says "category of one", "own a category", "change the game" |
| 14 | - After `monopoly-niche-finder` to formalize the niche into a named category |
| 15 | - After `purple-cow-audit` to amplify what makes a product remarkable |
| 16 | - Before creating content/offers to ensure consistent category messaging |
| 17 | |
| 18 | ## Input Schema |
| 19 | |
| 20 | ```yaml |
| 21 | product: object # REQUIRED — the product to position |
| 22 | name: string |
| 23 | description: string |
| 24 | key_features: string[] |
| 25 | pricing: string |
| 26 | current_category: string # What category it's currently in |
| 27 | # e.g., "AI video tools", "email marketing platforms" |
| 28 | |
| 29 | competitors: string[] # OPTIONAL — main competitors |
| 30 | # Default: auto-researched |
| 31 | |
| 32 | your_audience: string # OPTIONAL — your specific audience |
| 33 | # Default: inferred from product |
| 34 | |
| 35 | monopoly_niche: string # OPTIONAL — from monopoly-niche-finder |
| 36 | # Default: none |
| 37 | ``` |
| 38 | |
| 39 | **Chaining from S1 monopoly-niche-finder**: Use `monopoly_niche.intersection` as the starting point for category design. |
| 40 | |
| 41 | **Chaining from S1 purple-cow-audit**: Use `remarkable_angles` to identify category-defining features. |
| 42 | |
| 43 | ## Workflow |
| 44 | |
| 45 | ### Step 1: Analyze Current Category |
| 46 | |
| 47 | 1. `web_search`: `"best [current_category]"` — see how the market is currently framed |
| 48 | 2. Identify the default buying criteria (price, features, ease of use, etc.) |
| 49 | 3. Map where the product wins AND loses on current criteria |
| 50 | 4. Identify: what does this product do that competitors DON'T even try? |
| 51 | |
| 52 | ### Step 2: Find the Category Seed |
| 53 | |
| 54 | The category seed is the intersection of: |
| 55 | - What the product does uniquely well |
| 56 | - What a specific audience cares about most |
| 57 | - What competitors ignore or can't do |
| 58 | |
| 59 | Formula: `[Unique capability] + [Specific audience] + [Outcome they care about]` |
| 60 | |
| 61 | Example: "AI avatar platform" + "for non-creators" + "who need professional video content" |
| 62 | = **"AI Video Content Platform for Non-Creators"** |
| 63 | |
| 64 | ### Step 3: Design the Category |
| 65 | |
| 66 | Define: |
| 67 | |
| 68 | 1. **Category name** — 3-6 words, self-explanatory, memorable |
| 69 | 2. **Category POV** — "The old way was [X]. The new way is [Y]. [Product] is the [category name]." |
| 70 | 3. **Buying criteria** — new criteria where your product automatically wins |
| 71 | 4. **Lightning strike** — the "aha moment" that makes the category real (a stat, story, or demonstration) |
| 72 | 5. **Category ecosystem** — what other products/services exist in YOUR category (you define the landscape) |
| 73 | |
| 74 | ### Step 4: Create Category Assets |
| 75 | |
| 76 | Produce: |
| 77 | 1. **Category narrative** — 2-3 paragraph story of why this category exists now |
| 78 | 2. **Comparison reframe** — how to redirect "Product X vs Product Y" to "Old category vs New category" |
| 79 | 3. **Content angles** — 5-10 content pieces that educate the market about the category |
| 80 | 4. **Objection handling** — "Isn't this just [old category]?" → "No, because..." |
| 81 | |
| 82 | ### Step 5: Self-Validation |
| 83 | |
| 84 | - [ ] Category name is self-explanatory to someone hearing it for the first time |
| 85 | - [ ] Product genuinely wins on the new buying criteria (not forced) |
| 86 | - [ ] Category is big enough to matter but specific enough to own |
| 87 | - [ ] Narrative is compelling and truthful (not spin) |
| 88 | - [ ] Content angles are substantial enough for 6+ months of content |
| 89 | |
| 90 | ## Output Schema |
| 91 | |
| 92 | ```yaml |
| 93 | output_schema_version: "1.0.0" |
| 94 | category: |
| 95 | name: string # The new category name |
| 96 | pov: string # Point of view statement |
| 97 | product_name: string |