motivation-design
Player motivation psychology, reward scheduling, intrinsic vs. extrinsic drives, Self-Determination Theory, loss aversion, collection drives, social motivation, and ethical guardrails. Use when designing reward systems, diagnosing why players aren't returning, building achievement or social features, evaluating retention mechanics, or when players say 'I don't know why I'd keep playing.' Bridges the gap between progression math (see progression-systems) and the psychology of why players stay.
What this skill does
# Motivation Design **Purpose:** Tools for understanding and designing around *why players play*. Progression-systems handles the math of growth curves. This skill handles the psychology underneath — what makes players choose to come back, what makes them stop, and where the ethical lines are. **Influences:** Frameworks here draw on Self-Determination Theory (autonomy, competence, relatedness), operant conditioning research (reinforcement schedules), prospect theory (loss aversion, endowment), and the Zeigarnik effect (incomplete task tension). Player motivation profiles adapted from modern survey-based taxonomies that extend the classic explorer/achiever/socializer/killer model. --- ## When to Activate Use this skill when: - Designing reward systems, loot tables, or achievement structures - Players aren't returning between sessions (retention failure) - Designing social features (guilds, leaderboards, co-op, competition) - Evaluating whether retention mechanics cross ethical lines - Players say "I don't know why I'd keep playing" or "there's nothing to do" - Choosing between intrinsic and extrinsic reward strategies - Designing daily login rewards, battle passes, or seasonal content - Diagnosing why engagement drops after the first few hours --- ## Core Framework: Self-Determination Theory (SDT) Three innate psychological needs predict sustained motivation. Mechanics that satisfy all three produce lasting intrinsic engagement. Undermining *any one* produces disengagement — even if the other two are strong. | Need | Definition | Game Mechanics | Undermined By | |------|-----------|----------------|---------------| | **Autonomy** | Sense of choice and voluntary engagement | Meaningful choices, character builds, open-world exploration, multiple viable strategies | Forced linear paths, "do this or fail," punitive daily requirements | | **Competence** | Sense of mastery and effectiveness | Skill progression, difficulty curves, mastery feedback, clear improvement signals | Unclear feedback, impossible challenges, pay-to-win (skill doesn't matter) | | **Relatedness** | Sense of connection and belonging | Co-op play, guilds, shared challenges, leaderboards, community events | Isolation by design, toxic competition, anonymous interactions | ### SDT Diagnostic When engagement drops, check each need: - [ ] **Autonomy:** Does the player feel they *choose* to play, or that the system *requires* them to? - [ ] **Competence:** Does the player feel they're getting better? Can they see evidence of mastery? - [ ] **Relatedness:** Does the player feel connected to other players or to the game world? If even one fails, adding more content or rewards won't fix retention. Fix the unmet need first. --- ## Player Motivation Profiles Modern survey-based frameworks identify six clusters of player motivation. Most players are driven by 2-3 primary profiles. Design for primary profiles; accommodate secondary ones. | Profile | Core Drive | Example Mechanics | Design Pitfall | |---------|-----------|-------------------|----------------| | **Action** | Excitement, destruction, fast pace | Combat, explosions, time pressure, speed runs | Burnout without recovery pacing | | **Social** | Cooperation, competition, community | Guilds, co-op missions, PvP, chat, trading | Toxic players driving others out | | **Mastery** | Strategy, challenge, completion | Puzzles, hard modes, leaderboards, ranked play | Alienating casual players | | **Achievement** | Collection, power, progression | Unlock trees, gear treadmills, badges, 100% completion | Grind for grind's sake | | **Immersion** | Fantasy, story, discovery | Lore, exploration, atmospheric design, role-playing | Story that contradicts mechanics | | **Creativity** | Customization, expression, building | Base building, character editors, mod support, level editors | Tools too complex to use | ### Application 1. **Identify your target profiles.** Which 2-3 profiles does your game serve best? 2. **Audit core loops against those profiles.** Does every session serve the primary profiles? 3. **Add accommodation for adjacent profiles.** Cosmetics for Creativity players in an Action game, optional lore for Immersion players in a Mastery game. 4. **Don't try to serve all six equally.** A game for everyone is a game for no one. --- ## Reinforcement Schedules How reward timing affects player behavior. These are the fundamental patterns underlying every reward system in games. | Schedule | Pattern | Engagement Effect | Example | |----------|---------|-------------------|---------| | **Fixed Ratio** | Reward every N actions | Predictable, steady engagement; brief pause after reward | Quest rewards, crafting recipes (combine 5 items → 1 output) | | **Variable Ratio** | Reward after random N actions | Highest engagement, hardest to stop | Loot drops, critical hits, fishing, gacha pulls | | **Fixed Interval** | Reward every N minutes/hours | Creates session pacing, "appointment" behavior | Daily login bonuses, cooldown timers, energy refills | | **Variable Interval** | Reward at random times | Creates checking behavior, anticipation | World boss spawns, random events, merchant restocks | ### Design Rules - **Variable ratio is the most powerful schedule** — and the most ethically fraught. Use it for discovery and exploration (finding rare loot in the wild), not for monetization pressure (spend $5 for another pull). - **Fixed ratio provides the clearest player agency.** Players can plan and strategize. Use for core progression. - **Fixed interval creates habits** but also resentment if missing the interval is punished (see Autonomy above). - **Layer schedules.** A single schedule grows predictable. Combine: fixed ratio for quest rewards + variable ratio for bonus loot + fixed interval for daily challenges. ### Schedule Selection Guide | Design Goal | Best Schedule | Why | |-------------|---------------|-----| | Reliable progression feel | Fixed Ratio | Players see direct effort-to-reward connection | | Exploration excitement | Variable Ratio | Anticipation on every attempt | | Session regularity | Fixed Interval | Players return at predictable times | | World feeling alive | Variable Interval | Surprise creates stories | | Long-term retention | Layered (all four) | No single schedule sustains indefinitely | ### Pity Systems (Bad Luck Protection) Pure variable ratio schedules can produce devastating dry streaks that feel unfair. Pity systems guarantee a minimum reward rate while preserving the excitement of variable rewards. | Type | Mechanism | Player Perception | |------|-----------|-------------------| | **Hard pity** | Guaranteed reward after N attempts (e.g., guaranteed rare at 90 pulls) | Safety net — "at worst, I need 90 tries" | | **Soft pity** | Probability increases with each unsuccessful attempt (e.g., base 1% rising to 5% after 50 attempts) | Invisible — feels like natural luck turning around | | **Pseudo-random** | Each failure increases the next success chance by a fixed amount; resets on success | Invisible — prevents both long dry streaks AND long hot streaks | | **Duplicate protection** | Already-owned items are removed from the pool or reduce in weight | Visible — "I won't get the same thing twice" | **Design rules:** - Soft pity is almost always better than hard pity — it feels like luck, not a timer - Communicate hard pity clearly (show the counter). Hide soft pity (let it feel organic). - Never reset pity across sessions, currency purchases, or game updates — that erodes trust - Pity should apply to ALL variable reward systems, not just premium ones --- ## Intrinsic vs. Extrinsic Motivation The most important tension in motivation design. - **Intrinsic:** Playing because the activity itself is rewarding — mastery, curiosity, creativity, flow - **Extrinsic:** Playing for external rewards — points, items, achievements, social status, unlocks ### The Overjustification Effect Adding extrinsic rewards
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.