player-experience-modeling
Model target players, motivations, emotions, pleasures, needs, flow, novelty, judgment, and interest curves. Use when defining who a game is for, shaping retention, diagnosing boredom or confusion, designing progression, or aligning gameplay with a desired emotional arc.
- License 许可
- MIT
- 最近更新
- 2026-06-26
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- player-experience-modeling
- license
- MIT
- metadata
- { "tags": "game-design,player-research,motivation,flow,interest-curve", "version": "0.1.0", "category": "Game Development", "displayName": "Player Experience Modeling" }
- description
- Model target players, motivations, emotions, pleasures, needs, flow, novelty, judgment, and interest curves. Use when defining who a game is for, shaping retention, diagnosing boredom or confusion, designing progression, or aligning gameplay with a desired emotional arc.
- compatibility
- Codex, Claude Code, and other Agent Skills-compatible clients.
02 资源文件 2
- 参考文档references/core/guide.md2.3 KB
- 参考文档workflows/experience-brief.md725 B
03 SKILL.md 正文
Player Experience Modeling
Use this skill to define the experience the game is trying to create before implementing systems. It gives an AI game-building agent a target for taste, pacing, onboarding, and progression decisions.
Source Traceability
Primary source: The Art of Game Design: A Book of Lenses, Third Edition by Jesse Schell, especially chapters 2, 9-11, and 16 on experience, players, pleasure, flow, motivation, novelty, judgment, and interest curves. The workflow is transformed and paraphrased.
Supporting source: Self-Determination Theory for autonomy, competence, and relatedness as durable motivation lenses.
Workflow
- Define the target player by behavior and context, not demographic shorthand.
- Identify the desired emotional and motivational promise.
- Map pleasures, needs, novelty, mastery, and social drivers.
- Shape the interest curve across first minute, first session, midpoint, climax, and return session.
- Translate experience goals into implementation constraints and telemetry.
Required Output
Player Model: target player, context, skills, anxieties, and motivations.Experience Promise: what the game should make the player feel and do.Motivation Map: autonomy, competence, relatedness, novelty, mastery, expression, and reward drivers.Interest Curve: beats, intensity, variety, and recovery.Build Implications: onboarding, feedback, difficulty, pacing, progression, and content priorities.
Local References
Before producing an experience model, read:
references/core/guide.mdworkflows/experience-brief.md
04 同仓库更多 Skills
android-emulator-qa
Use when validating Android feature flows in an emulator with adb-driven launch, input, UI-tree inspection, screenshots, and logcat capture.
supabase-postgres-best-practices
Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.
sentry
Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.
render-workflows
Sets up, develops, tests, and deploys Render Workflows. Covers first-time scaffolding (via CLI or manual), SDK installation (Python or TypeScript), task patterns (retries, subtasks, fan-out), local development, Dashboard deployment, and troubleshooting. Use when a user wants to set up Render Workflows for the first time, scaffold a workflow service, add or modify workflow tasks, test workflows locally, or deploy workflows to Render.
render-web-services
Configures Render web services—port binding, TLS, health checks, custom domains, auto-deploy, PR previews, persistent disks, and deploy lifecycle. Use when the user needs to set up a web service, fix health check failures, add a custom domain, configure zero-downtime deploys, or troubleshoot port binding issues.
render-static-sites
Deploys and configures static sites on Render's global CDN—build commands, publish paths, SPA routing, redirects, custom headers, and PR previews. Use when the user needs to deploy a static site, set up a React/Vue/Hugo/Gatsby frontend, configure SPA fallback routing, add redirect rules, customize response headers, or choose between a static site and a web service for their frontend. Trigger terms: static site, CDN, SPA, single-page app, React deploy, Vue deploy, Hugo, Gatsby, Docusaurus, Jekyll, staticPublishPath.