$npx -y skills add Stanestane/game-design-skills-bundle --skill game-design-player-persona-extractorExtract the ideal player persona and anti-persona for a game, feature, loop, or progression structure based on the design itself. Use when a team can describe mechanics but cannot clearly articulate who the design is truly for, which player motivations and tolerances it suits, wh
| 1 | # Game Design Player Persona Extractor |
| 2 | |
| 3 | Extract who a design is actually built for. |
| 4 | |
| 5 | Use this skill when a team can describe systems, loops, and mechanics, but not the kind of player who will love them, tolerate them, or bounce off them. The job is not to invent a fake marketing avatar. The job is to infer the player profile implied by the design. |
| 6 | |
| 7 | Focus on behavior, motivation, tolerance, learning style, and emotional appetite. Avoid demographic fluff unless the user explicitly asks for it. |
| 8 | |
| 9 | Read `references/family-conventions.md` when you want the shared style, prioritization, and diagnosis rules for this game-design skill family. |
| 10 | Read `references/output-patterns.md` when you want the preferred recommendation and minimal-fix structure. |
| 11 | Read `references/demographic-research-notes.md` when the user explicitly wants demographic support, market validation, or publisher-facing audience framing. |
| 12 | |
| 13 | ## Core principle |
| 14 | |
| 15 | A game becomes sharper when it serves a specific kind of player extremely well instead of vaguely trying to work for everyone. |
| 16 | |
| 17 | A useful persona does three things: |
| 18 | - identifies who the design delights |
| 19 | - identifies who the design frustrates or excludes |
| 20 | - implies concrete design choices |
| 21 | |
| 22 | If the resulting persona could fit almost any game, it is too weak to matter. |
| 23 | |
| 24 | ## What to produce |
| 25 | |
| 26 | Generate: |
| 27 | 1. **Ideal player persona** - the player this design best serves |
| 28 | 2. **Anti-persona** - the player most likely to reject or churn from it |
| 29 | 3. **Behavior profile** - how the player approaches play, learning, and decisions |
| 30 | 4. **Emotional profile** - what they want to feel and what breaks the deal |
| 31 | 5. **Design implications** - what the design must emphasize, protect, and avoid for this audience |
| 32 | 6. **Optional demographic layer** - only when explicitly requested, add likely demographic or market-fit hypotheses that support the behavior-first persona rather than replacing it |
| 33 | 7. **Optional market audience summary** - when requested for pitch, publishing, or strategy use, convert the persona into a concise audience-facing summary with demographic overlap, comparable-title signals, and confidence notes |
| 34 | |
| 35 | ## Process |
| 36 | |
| 37 | ### 1. Define the extraction target |
| 38 | Clarify: |
| 39 | - what exact game, feature, or loop is being analyzed |
| 40 | - whether the persona is for the whole product or only one experience slice |
| 41 | - what known constraints already shape audience fit |
| 42 | |
| 43 | Write: |
| 44 | - **Extraction target** |
| 45 | - **Scope** |
| 46 | - **Known constraints** |
| 47 | |
| 48 | ### 2. Read the design for behavioral signals |
| 49 | Look at features such as: |
| 50 | - difficulty level |
| 51 | - randomness level |
| 52 | - pacing and session length |
| 53 | - agency level |
| 54 | - punishment severity |
| 55 | - progression structure |
| 56 | - strategic depth |
| 57 | - repetition tolerance |
| 58 | - required patience, experimentation, or precision |
| 59 | |
| 60 | Ask: |
| 61 | - What kind of player will enjoy making these decisions repeatedly? |
| 62 | - What kind of frustration is this design asking the player to tolerate? |
| 63 | - Does it reward mastery, experimentation, social play, expression, optimization, calm routine, or high tension? |
| 64 | |
| 65 | ### 3. Infer the core motivation profile |
| 66 | Common motivation buckets include: |
| 67 | - mastery and skill growth |
| 68 | - experimentation and discovery |
| 69 | - optimization and efficiency |
| 70 | - competition and status |
| 71 | - expression and creativity |
| 72 | - narrative curiosity |
| 73 | - collection and completion |
| 74 | - comfort, ritual, and low-pressure progress |
| 75 | |
| 76 | State which motivations the design strongly serves and which it serves poorly. |
| 77 | |
| 78 | ### 4. Infer the tolerance profile |
| 79 | Judge what the implied player can comfortably tolerate in terms of: |
| 80 | - difficulty |
| 81 | - repetition |
| 82 | - randomness |
| 83 | - ambiguity |
| 84 | - failure frequency |
| 85 | - delayed rewards |
| 86 | - long sessions or short bursts |
| 87 | - social friction |
| 88 | - optimization pressure |
| 89 | |
| 90 | This often reveals the anti-persona more clearly than the positive persona does. |
| 91 | |
| 92 | ### 5. Describe the play style and learning style |
| 93 | Clarify how the ideal player tends to behave: |
| 94 | - cautious or impulsive |
| 95 | - planner or improviser |
| 96 | - systems learner or fantasy chaser |
| 97 | - repetition-based learner or novelty seeker |
| 98 | - optimizer or role-player |
| 99 | - solo-focused or socially motivated |
| 100 | |
| 101 | Write this as behavior, not vague adjectives. |
| 102 | |
| 103 | ### 6. Define emotional expectations |
| 104 | Ask: |
| 105 | - What does this player want to feel regularly? |
| 106 | - What kind of tension is enjoyable to them? |
| 107 | - What kind of frustration will they accept? |
| 108 | - What kind of frustration will feel like betrayal? |
| 109 | |
| 110 | ### 7. Define the anti-persona |
| 111 | State clearly who this is not for and why. |
| 112 | |
| 113 | Avoid generic anti-personas like "people who do |