Game Design Player Segment Perception Audit

Check not only who the feature is for, but who will see it, misunderstand it, resent it, or feel left out by it.

Use this skill to audit a feature through the eyes of different player segments. The goal is not to please every segment equally. The goal is to understand who the feature is actually serving, what other groups will perceive, and where update visibility, access, and expectation can create disappointment or wasted communication.

Read references/segment-layers.md when mapping the main audience groups. Read references/perception-failures.md when diagnosing common update-perception mistakes. Read references/recommendation-patterns.md when deciding how to adjust targeting, access, or messaging.

What to produce

Produce:

1. Feature read - what the feature is and who it seems intended for
2. Target segment read - which cohort is supposed to care most and why
3. Cross-segment perception - how other player groups are likely to interpret it
4. Access and visibility mismatch - who will hear about it versus who can actually use it
5. Risk diagnosis - what disappointment, alienation, or wasted hype may result
6. Recommendation - how to retarget, reframe, gate, soften, or broaden the feature rollout