Skill: stanestane/game-design-systematizing-empathizing-audit (version 1.0.0)

--- name: game-design-systematizing-empathizing-audit description: "Evaluate a game, feature, system, UX flow, progression loop, live-ops mechanic, monetization surface, or design concept on two axes: systematizing and empathizing. Use when you want to understand whether a design is structurally logic-driven or emotionally player-attuned, what kind of player personas it is likely to attract or repel, and what practical consequences follow from that positioning without assuming one quadrant is universally best." --- # Game Design Systematizing Empathizing Audit Position the design by how strongly it rewards system-thinking and how strongly it reflects emotional understanding of the player. Use this skill to understand what kind of design a concept is becoming, what kind of people it is likely to appeal to, and what tradeoffs come with that positioning. The goal is not to force every concept toward an imagined ideal balance. The goal is to diagnose where the design sits, who that tends to work for, who may reject it, and whether that positioning feels intentional or accidental. Read `references/axis-definitions.md` when judging the two axes. Read `references/quadrant-reads.md` when describing what the position tends to feel like in practice. Read `references/persona-tendencies.md` when mapping likely audience appeal and rejection. ## What to produce Produce: 1. **Design read** - what the concept is trying to do 2. **Systematizing position** - how strongly it emphasizes logic, structure, mastery, and model-building 3. **Empathizing position** - how strongly it emphasizes emotional fit, player sensitivity, warmth, expression, and humane friction handling 4. **Positioning read** - what this combination tends to feel like in practice 5. **Likely persona appeal** - who is likely to enjoy or value this design 6. **Likely rejection pattern** - who may bounce and why 7. **Practical consequences** - what follows for onboarding, retention, monetization, community, or communication 8. **Recommendation** - how to lean into, counterweight, clarify, or intentionally preserve the position ## Process ### 1. Read the design at the player-experience level Clarify: - what the concept wants the player to do - what kind of player experience it seems to prioritize - whether the design is asking for mastery, comfort, expression, optimization, social belonging, emotional immersion, or some combination ### 2. Judge the systematizing axis Ask how strongly the design rewards: - understanding rules - building internal models - predicting outcomes - optimizing behavior - mastering systems - engaging with strategic structure Look for evidence such as: - clear rule consistency - explicit feedback and cause-effect legibility - optimization depth - mastery curves - strategic planning pressure - meaningful structural complexity ### 3. Judge the empathizing axis Ask how strongly the design reflects understanding of: - player emotional reality - frustration tolerance - comfort and dignity - expressive identity - emotional readability - social sensitivity - humane handling of failure, pressure, and confusion Look for evidence such as: - emotionally considerate onboarding - softened or well-framed failure - expressive play support - social meaning beyond pure function - sensitivity to frustration and player mood - systems that feel humane rather than merely correct ### 4. Describe the resulting position Do not rank the quadrant morally. Describe what this position tends to mean. For example: - precise but emotionally austere - warm and intuitive but structurally soft - deep and humane but demanding to execute well - underdefined and low-intent on both axes ### 5. Map likely persona appeal Infer which player tendencies are likely to find this attractive. Possible personas include: - optimizer - systems thinker - mastery-seeker - competitive achiever - tinkerer - cozy comfort-seeker - expressive identity player - social harmony player - narrative-relational player - low-friction casual - routine habit player Use these as practical shorthand, not rigid psychological categories. ### 6. Map likely rejection Ask which players are likely to bounce and why. Common causes include: - too much cold optimization pressure - too little structural depth - not enough emotional cushioning - too much emotional softness for mastery-seekers - social sterility - unclear or weak challenge identity ### 7. Extract practical implications Describe what this position tends to imply for: - onboarding - retention - monetization tolerance - community behavior - feature communication - audience targeting - risk of mismatch between fantasy and system ### 8. Recommend intentionality End with a practical recommendation such as: - lean further into this audience fit - add a small counterweight on the weaker axis - stop pretending the design is for everyone - communicate the positioning more honestly - preserve the current direction because it matches the concept well - simplify a mismatch between emotional promise and structural reality ## Response structure ### Design Read - ... ### Systematizing Position - ... ### Empathizing Position - ... ### Positioning Read - ... ### Likely Persona Appeal - ... ### Likely Rejection Pattern - ... ### Practical Consequences - ... ### Recommendation - ... ## Fast mode - How logic-driven and mastery-oriented is this design? - How emotionally considerate and player-attuned is it? - What kind of player is most likely to love this? - What kind of player is most likely to bounce? - What is the most important consequence of that positioning? - Should the team lean in, counterbalance, or clarify? ## Style rules - Do not assume one quadrant is best. - Do not confuse warmth with weakness. - Do not confuse rigor with quality. - Tie judgments to observable design consequences. - Use personas as tendencies, not as deterministic labels. - If the design is mismatched, say whether the mismatch feels intentional or accidental. ## Working principle A design does not appeal to everyone in the same way. This skill exists to clarify what kind of player the design is really speaking to, and what structural-emotional tradeoffs come with that choice.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)