Skip to content
Back to search

game-design-skills-bundle

A public OpenClaw and ClawHub-ready bundle of game design skills for emotional direction, feature workflows, audits, FTUE, pitch decks, prototyping, and red-team design review.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/stanestane--game-design-skills-bundle/badge.svg)](/listings/stanestane--game-design-skills-bundle)

HTML

<a href="/listings/stanestane--game-design-skills-bundle"><img src="/api/listings/stanestane--game-design-skills-bundle/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 944 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Game Design Skills Bundle
  2. A curated bundle of reusable game design skills for OpenClaw / ClawHub-style agent workflows.
  3. This repository collects a set of practical design skills covering:
  4. - emotional direction
  5. - design decision workflows
  6. - player motivation and need audits
  7. - prototyping under uncertainty
  8. - creative unblockers
  9. - FTUE analysis
  10. - pitch deck review
  11. These skills are designed to be used either:
  12. - as installed skill folders in an OpenClaw workspace, or
  13. - as packaged `.skill` files from the `package-skills/` folder.
  14. They also now include `emotional-canvas-moodboard`, a follow-on moodboard skill that turns emotional direction into curated visual boards with candidate-pool gathering, hard rejection, palette-reference support, and clean or annotated JPG/HTML outputs.
  15. They now also include beginner-oriented planning skills for turning rough game concepts into sane first steps, team plans, and budget ranges, plus a project-adjacent collaboration skill for analyzing recurring conflict patterns on software teams.
  16. This repo now also includes a newer extractor/audit pack focused on fantasy, persona, pillars, core loop, failure loop, attribution, flow, fairness/frustration, a deliberately provocative Molyneux-style lens, a fast-vs-slow cognition audit inspired by Thinking, Fast and Slow, plus peak-end and Zeigarnik-effect audits for memory-shape and unfinished-business tension.
  17. ## Repository structure
  18. - `game-design-*/` - individual game-design skill folders
  19. - `package-skills/` - packaged distributable `.skill` files
  20. - `game-design-skill-catalog.md` - compact local catalog/index
  21. ## Skills
  22. ## New extractor / audit additions
  23. ### game-design-attribution-audit
  24. **What it does:**
  25. Audits how players explain success and failure through attribution theory: locus, stability, and controllability.
  26. **Use it when:**
  27. - players seem to blame the game instead of their own decisions
  28. - a failure feels unfair, opaque, or unteachable
  29. - you want to diagnose learned helplessness, rage, or churn after repeated losses
  30. **Best for:**
  31. Perceived causality, fairness diagnosis, and failure-teachability analysis.
  32. ---
  33. ### game-design-flow-audit
  34. **What it does:**
  35. Audits how challenge and player skill align over time to identify boredom, anxiety, and exact flow-break moments.
  36. **Use it when:**
  37. - pacing feels flat, spiky, or mysteriously exhausting
  38. - difficulty may be too high, too low, or badly timed
  39. - you need a time-based engagement read rather than a static balance opinion
  40. **Best for:**
  41. Challenge-skill alignment, pacing diagnosis, and temporal engagement analysis.
  42. ---
  43. ### game-design-fairness-frustration-audit
  44. **What it does:**
  45. Combines attribution, flow, and randomness-perception lenses to audit whether a design feels fair, understandable, and worth retrying.
  46. **Use it when:**
  47. - players say something feels unfair, rigged, hostile, or just maddening
  48. - the system is technically functional but emotionally untrusted
  49. - you need to know why frustration points toward quitting instead of mastery
  50. **Best for:**
  51. Trust diagnosis, fairness perception, and retry-worthiness analysis.
  52. ---
  53. ### game-design-failure-loop-audit
  54. **What it does:**
  55. Audits what happens after failure: what players lose, what they learn, how fast they re-enter, and whether the loop creates momentum or resignation.
  56. **Use it when:**
  57. - retry structure feels punishing or exhausting
  58. - the team is tuning death, setback, reset, or recovery systems
  59. - the player dreads the retry more than the challenge itself
  60. **Best for:**
  61. Punishment tuning, retry friction analysis, and post-failure motivation diagnosis.
  62. ---
  63. ### game-design-fantasy-extractor
  64. **What it does:**
  65. Extracts the core player fantasy from what the design actually lets the player do, feel, and become.
  66. **Use it when:**
  67. - the team can explain mechanics but not the emotional promise
  68. - a pitch names features instead of a player fantasy
  69. - the concept feels emotionally vague or thematically fake
  70. **Best for:**
  71. Fantasy clarification, pitch sharpening, and mechanic-to-emotion alignment.
  72. ---
  73. ### game-design-player-persona-extractor
  74. **What it does:**
  75. Extracts the ideal player persona and anti-persona from the design itself, behavior-first. It can also optionally add demographic overlap, market-validation, comparable-title, and pitch-facing audience-summary layers when explicitly requested.
  76. **Use it when:**
  77. - the team knows the mechanics but not who the design is really for
  78. - audience fit is vague or contradictory
  79. - you need a behavior-first persona before adding market-facing framing
  80. **Best for:**
  81. Audience-fit diagnosis, player targeting, and pitch-support persona framing.
  82. ---
  83. ### game-design-design-pillars-extractor
  84. **What it does:**
  85. Extracts 3 to 5 actionable design pillars from what the game actually rewards, prioritizes, and sacrifices.
  86. **Use it when:**
  87. - the team has vague slogans instead of real design pillars
  88. - mechanics exist but the governing principles are muddy
  89. - you need tradeoff-driven pillars that can guide cuts and decisions
  90. **Best for:**
  91. Design-principle extraction, focus recovery, and feature-triage alignment.
  92. ---
  93. ### game-design-core-loop-extractor
  94. **What it does:**
  95. Extracts the actual repeatable core loop from player actions, game response, reward, and renewed motivation.
  96. **Use it when:**
  97. - a pitch sounds like disconnected feature soup
  98. - the design doc lists systems but not the repeatable engine
  99. - you need to separate the core loop from meta layers and progression wallpaper
  100. **Best for:**
  101. Loop clarity, feature-sprawl diagnosis, and motivational structure analysis.
  102. ---
  103. ### game-design-molyneux-lens
  104. **What it does:**
  105. Stress-tests a concept through a deliberately provocative, ambition-seeking lens that pushes fantasy and reactivity, then grounds the result back into something usable.
  106. **Use it when:**
  107. - a concept feels too safe or mechanically competent but emotionally weak
  108. - the team needs sharper provocation, stronger fantasy, or more memorable possibility
  109. - you want a boldness check before settling into compromise
  110. **Best for:**
  111. Ambition pressure-testing, fantasy escalation, and memorable-moment provocation.
  112. ---
  113. ### game-design-thinking-fast-and-slow-audit
  114. **What it does:**
  115. Audits a design through the lens of fast versus slow thinking: instinctive/reactive cognition versus deliberate/analytical cognition, including where the design mishandles transitions between them.
  116. **Use it when:**
  117. - a proposal may be asking for the wrong kind of thinking for its fantasy or pacing
  118. - a hybrid design feels cognitively awkward, exhausting, or fake-deep
  119. - you want to diagnose overload, under-stimulation, or bad handoffs between reactive and reflective play
  120. **Best for:**
  121. Cognitive-demand analysis, fast/slow mode-fit diagnosis, and handoff-risk audits.
  122. ---
  123. ### game-design-peak-end-audit
  124. **What it does:**
  125. Audits a design through the peak-end rule by identifying which moments dominate memory, how strong the emotional peaks are, and whether the ending helps or poisons the remembered experience.
  126. **Use it when:**
  127. - a feature feels decent on average but is remembered badly
  128. - you want to know whether the strongest moment and the final note are doing the right work
  129. - a reward sequence, session ending, or event wrap-up needs a stronger aftertaste
  130. **Best for:**
  131. Memory-shape diagnosis, ending-quality analysis, and peak-moment tuning.
  132. ---
  133. ### game-design-zeigarnik-effect-audit
  134. **What it does:**
  135. Audits a design through the Zeigarnik effect by examining how unresolved tasks, incomplete progress, and open loops create return tension, curiosity, or unhealthy pressure.
  136. **Use it when:**
  137. - a system relies on unfinished business to drive return behavior
  138. - you want to know whether open loops create momentum or just chores and guilt
  139. - quest logs, event tracks, collections, or progression dashboards may be cluttering the player's mind
  140. **Best for:**
  141. Open-loop tension analysis, return-motivation diagnosis, and unfinished-task hygiene.
  142. ---
  143. ### 0. game-dev-first-steps
  144. **What it does:**
  145. Helps beginners or early-stage indie teams turn a rough game idea into a practical starting plan, prototype strategy, or pitchable vertical-slice path.
  146. **Use it when:**
  147. - someone asks how to start making a game
  148. - the concept sounds exciting but the order of work is fuzzy
  149. - a solo dev, duo, or small team needs help scoping the first milestone
  150. - the team needs advice on what to build now versus what to postpone
  151. **Best for:**
  152. Beginner-friendly concept scoping and early development sequencing.
  153. **Example prompt:**
  154. > I have an idea for a mobile game where you defend a train from bandits. I'm a solo developer. What should I figure out first, what should I prototype first, and what should I postpone if I want a pitchable vertical slice?
  155. **Short blurb:**
  156. A beginner-friendly skill that turns rough game ideas into practical first steps, sane milestone planning, and realistic build order advice.
  157. ---
  158. ### 0.5 game-dev-team-gap
  159. **What it does:**
  160. Helps a beginner or early-stage team figure out which roles and skill areas are missing, weakly covered, or dangerously overloaded for a specific game concept and target milestone.
  161. **Use it when:**
  162. - someone asks who is missing from the team
  163. - a concept seems larger than the current team can safely handle
  164. - a solo dev, duo, or small team needs to understand its weakest coverage
  165. - no team has been described yet and the user wants the minimum viable team for the project
  166. **Best for:**
  167. Beginner-friendly role-gap diagnosis and minimum-team planning.
  168. **Example prompt:**
  169. > We want to make a small co-op survival game for PC and mobile-friendly art style. We have one programmer and one 2D artist. What roles are we missing, which gaps are dangerous, and what is the smallest realistic team for a pitchable vertical slice?
  170. **Short blurb:**
  171. A practical skill for identifying missing roles, weak coverage, and the smallest workable team for a game concept.
  172. ---
  173. ### 0.75 game-dev-budget-estimator
  174. **What it does:**
  175. Helps a beginner or early-stage team estimate likely budget ranges for a game concept based on scope, team coverage, milestone, work model, and geography.
  176. **Use it when:**
  177. - someone asks how much a game like this might cost
  178. - the concept, team, and milestone are known but the budget picture is fuzzy
  179. - the team wants to understand what is already covered internally versus what still costs real money
  180. - no team has been described yet and the user wants scenario-based budget ranges
  181. **Best for:**
  182. Beginner-friendly budget framing, cost-driver diagnosis, and rough milestone-based game cost estimation.
  183. **Example prompt:**
  184. > We want to make a pitchable mobile F2P action game. We have one programmer in Serbia and one freelance 2D artist in Poland working part-time. What budget range should we expect for a vertical slice, what costs are already covered, and what hidden costs are we probably missing?
  185. **Short blurb:**
  186. A practical skill for turning a game concept, team, and scope into a rough budget range with transparent assumptions and cost drivers.
  187. ---
  188. ### 0.8 game-dev-time-estimator
  189. **What it does:**
  190. Helps a beginner or early-stage team estimate likely development time ranges for a game concept based on scope, team coverage, milestone, availability, and production constraints.
  191. **Use it when:**
  192. - someone asks how long a game like this might take
  193. - the concept, team, and milestone are known but the schedule picture is fuzzy
  194. - the team wants to know whether a target date is realistic
  195. - no team has been described yet and the user wants scenario-based timeline ranges
  196. **Best for:**
  197. Beginner-friendly schedule framing, time-driver diagnosis, and rough milestone-based development-time estimation.
  198. **Example prompt:**
  199. > We want to make a PC co-op survival prototype. We have one programmer full-time and one 3D artist part-time. How long would a prototype or vertical slice likely take, what will bottleneck us, and is 5 months realistic?
  200. **Short blurb:**
  201. A practical skill for turning a game concept, team, and scope into a rough development timeline with transparent assumptions and schedule risks.
  202. ---
  203. ### 0.9 game-design-fogg-behavior-audit
  204. **What it does:**
  205. Audits a game feature, flow, onboarding step, retention mechanic, or monetization prompt using the Fogg Behavior Model: Motivation, Ability, Prompt.
  206. **Use it when:**
  207. - a feature seems valuable on paper but players are not using it
  208. - you want to diagnose whether a behavior is failing because of low motivation, low ability, or a bad prompt
  209. - you need a focused audit of onboarding, event participation, reward claims, retention mechanics, or monetization nudges
  210. - you want a practical feature-adoption critique instead of a broad design essay
  211. **Best for:**
  212. Behavior-focused feature audits, adoption diagnosis, and prompt/friction analysis.
  213. **Example prompt:**
  214. > Audit this daily event flow with the Fogg Behavior Model. The goal is to get players to enter the event once per day, but adoption is weak. Tell me whether motivation, ability, or prompt is the main bottleneck.
  215. **Short blurb:**
  216. A practical audit skill for diagnosing whether a feature actually drives the intended player behavior.
  217. ---
  218. ### 0.95 game-design-perceived-randomness-audit
  219. **What it does:**
  220. Audits a game feature, combat system, loot table, reward loop, procedural system, or chance mechanic by how players are likely to perceive its randomness rather than only by the raw math.
  221. **Use it when:**
  222. - players may think the system feels rigged, streaky, or malicious
  223. - a design relies on loot drops, hit chance, crits, proc systems, or procedural offers
  224. - you want to check whether randomness supports skill or sabotages action
  225. - you need to diagnose gambler's-fallacy-style expectations, expectation mismatch, or competence damage
  226. **Best for:**
  227. Perceived fairness audits, randomness placement diagnosis, and frustration-risk analysis around chance systems.
  228. **Example prompt:**
  229. > Audit this chest and combat reward system from the perspective of perceived randomness. Players can miss attacks, crit unpredictably, and open random post-fight chests. Tell me where players may feel the game is rigged, whether the randomness is placed well, and what should change first.
  230. **Short blurb:**
  231. A practical audit skill for evaluating how players are likely to interpret, mistrust, or emotionally react to randomness in a game system.
  232. ---
  233. ### 1. game-design-emotional-canvas
  234. **What it does:**
  235. Defines the emotional core, atmosphere, tone, and vibe of a game, feature, event, world area, or content theme.
  236. **Use it when:**
  237. - a concept feels emotionally vague
  238. - you want a moodboard-ready emotional direction
  239. - you need to clarify what players should feel
  240. - art, audio, narrative, and design need emotional alignment
  241. **Best for:**
  242. High-level emotional identity work.
  243. ---
  244. ### 2. game-design-grow-design
  245. **What it does:**
  246. Applies the GROW model (Goal, Reality, Options, Will) to game design decision-making.
  247. **Use it when:**
  248. - a team is stuck in circular feature discussions
  249. - a design problem needs more structure
  250. - you need clearer tradeoffs and next steps
  251. - a feature pitch is muddy and process-heavy thinking would help
  252. **Best for:**
  253. Structured feature and roadmap conversations.
  254. ---
  255. ### 3. game-design-player-motivation-audit
  256. **What it does:**
  257. Audits what kinds of motivation a game or feature creates using an SDT-inspired motivation spectrum.
  258. **Use it when:**
  259. - a system feels sticky but suspiciously hollow
  260. - you want to understand whether behavior is driven by rewards, pressure, identity, or intrinsic fun
  261. - you are reviewing live-ops, progression, battle passes, or social systems
  262. **Best for:**
  263. Diagnosing the motivational quality of engagement.
  264. ---
  265. ### 3.5 game-design-granular-player-motivation-audit
  266. **What it does:**
  267. Audits a game, feature, or system through a granular player motivation taxonomy spanning progress, cognition, immersion, creation, leadership, belonging, competition, and rewards.
  268. **Use it when:**
  269. - Bartle or broad motivation theory feels too coarse
  270. - you want to know which detailed motivation segments a design strongly serves, neglects, or quietly repels
  271. - you need to distinguish between competitive status, strategic leadership, creative authorship, narrative absorption, social belonging, and reward-chasing
  272. **Best for:**
  273. Segment-level motivation analysis, fine-grained audience-fit diagnosis, and motivation audits with more archetype detail than a simple four-type model.
  274. ---
  275. ### 3.6 game-design-big-five-personality-audit
  276. **What it does:**
  277. Audits a game, feature, or system through the Big Five / OCEAN personality traits: Openness, Conscientiousness, Extraversion, Agreeableness, and Neuroticism.
  278. **Use it when:**
  279. - you want a personality-fit lens rather than a motivation or archetype lens
  280. - you need to understand how much novelty, structure, social intensity, cooperation, or emotional pressure a design assumes
  281. - you want to know what kinds of players feel naturally comfortable versus overloaded, stressed, or alienated by the experience
  282. **Best for:**
  283. Personality-style fit diagnosis, emotional-cost analysis, and exposing hidden assumptions about ambiguity, obligation, social loudness, conflict, and punishment tolerance.
  284. ---
  285. ### 4. game-design-player-need-satisfaction-audit
  286. **What it does:**
  287. Audits whether a design satisfies or frustrates autonomy, competence, and relatedness.
  288. **Use it when:**
  289. - a feature retains players but may feel quietly depleting
  290. - you want to understand whether the experience is psychologically nourishing
  291. - onboarding, progression, or social systems feel flat or coercive
  292. **Best for:**
  293. Psychological need diagnosis and quality-of-experience audits.
  294. ---
  295. ### game-design-multiplayer-feature-audit
  296. **What it does:**
  297. Audits a game, feature, live-ops layer, social system, or multiplayer concept for the quality and fit of its social design.
  298. **Use it when:**
  299. - you want to evaluate collaboration, competition, or collaborate-to-compete structures
  300. - you need to judge whether a feature should be synchronous, asynchronous, realtime, or hybrid
  301. - you are reviewing guilds, clubs, leaderboards, judged showcases, community structures, or status systems
  302. - you want to add social play to a mostly single-player game without damaging its core fantasy
  303. **Best for:**
  304. Social-system fit, multiplayer structure, community formation, and vanity/status audits.
  305. ---
  306. ### 5. game-design-unknown-unknowns-prototyping
  307. **What it does:**
  308. Maps uncertainty and helps decide what to prototype, in what order, and why.
  309. **Use it when:**
  310. - a concept seems promising but underdefined
  311. - the team does not know what the real design question is yet
  312. - a prototype risks becoming production theater instead of a learning tool
  313. **Best for:**
  314. Preproduction and uncertainty-driven prototyping.
  315. ---
  316. ## Beginner planning / first-step strategy
  317. ### 6. game-dev-first-steps
  318. **What it does:**
  319. Turns a rough game idea into a practical starting plan by asking about team size, skill mix, platform, scope, and first milestone, then recommending what to build first, what to postpone, and how to avoid early overscope.
  320. **Use it when:**
  321. - someone asks "how do I start making this?"
  322. - a beginner needs help deciding what to build first
  323. - a solo dev, duo, or small team needs a sane first milestone
  324. - a concept should be reduced into a prototype or pitchable vertical slice plan
  325. **Best for:**
  326. Beginner-friendly scoping, build-order advice, and early production strategy.
  327. ---
  328. ## GROW-derived workflow family
  329. These skills split the broader GROW-style decision process into smaller, sharper workflows.
  330. ### 6. game-design-goal-framing
  331. **What it does:**
  332. Turns a vague feature idea into a clear design goal with purpose, fit, success criteria, and constraints.
  333. **Use it when:**
  334. - a feature sounds fine but nobody can explain what it is really for
  335. - success criteria are unclear
  336. - the team is jumping into implementation too early
  337. **Best for:**
  338. Clarifying purpose before ideation or production.
  339. ---
  340. ### 7. game-design-option-generation
  341. **What it does:**
  342. Generates multiple credible solution paths before the team commits to one.
  343. **Use it when:**
  344. - one answer is dominating too early
  345. - you want several plausible approaches with tradeoffs
  346. - the solution space feels artificially narrow
  347. **Best for:**
  348. Expanding design options before prioritization.
  349. ---
  350. ### 8. game-design-five-options
  351. **What it does:**
  352. Forces explicit comparison across at least five candidate directions.
  353. **Use it when:**
  354. - there are already several ideas on the table
  355. - the team needs structured comparison
  356. - you want to avoid premature convergence
  357. **Best for:**
  358. Tactical option comparison.
  359. ---
  360. ### 9. game-design-roadblock-reframing
  361. **What it does:**
  362. Reframes a blocked design problem by isolating the obstacle, imagining it removed, and deriving workaround paths.
  363. **Use it when:**
  364. - the team keeps saying “we can’t because…”
  365. - one blocker is dominating all thinking
  366. - a feature feels trapped by a specific limitation
  367. **Best for:**
  368. Getting unstuck from design deadlock.
  369. ---
  370. ### 10. game-design-ideal-outcome-backcasting
  371. **What it does:**
  372. Starts from the ideal player-facing result and works backward to the conditions and steps needed to reach it.
  373. **Use it when:**
  374. - the end-state is easier to imagine than the path forward
  375. - the team knows the destination vibe but not the design sequence
  376. - you want to align a feature around a stronger final vision
  377. **Best for:**
  378. Vision-led design planning.
  379. ---
  380. ### 11. game-design-transformative-reuse
  381. **What it does:**
  382. Finds ways to adapt, recombine, extend, or retune existing systems instead of inventing from scratch.
  383. **Use it when:**
  384. - you want leverage over novelty
  385. - live systems already exist and should be reused intelligently
  386. - the team needs lower-risk innovation
  387. **Best for:**
  388. Production-aware feature design and reuse strategy.
  389. ---
  390. ### 12. game-design-feature-prioritization
  391. **What it does:**
  392. Compares options by impact, cost, fit, timing, and risk to decide what should happen now versus later.
  393. **Use it when:**
  394. - several candidate features compete for attention
  395. - ideation is done and prioritization is needed
  396. - roadmap discussions need a more explicit decision frame
  397. **Best for:**
  398. Choosing the strongest next move.
  399. ---
  400. ## Creative disruption
  401. ### 13. game-design-creative-unblocker
  402. **What it does:**
  403. Uses oblique prompts, sideways reframing, and playful provocations to break creative block.
  404. **Use it when:**
  405. - a feature feels stale
  406. - discussions are looping
  407. - every option feels equally dead
  408. - the team needs strange but useful creative motion
  409. **Best for:**
  410. Creative detours and design unblock sessions.
  411. ---
  412. ## FTUE / onboarding
  413. ### 14. game-design-ftue-hero-journey-audit
  414. **What it does:**
  415. Audits FTUE and onboarding flows through the Hero’s Journey lens.
  416. **Use it when:**
  417. - the opening experience feels too tutorial-like and not emotionally engaging
  418. - you want to audit call-to-adventure, mentor guidance, and threshold crossing
  419. - you want a more narrative-emotional reading of onboarding quality
  420. **Best for:**
  421. FTUE, onboarding, and first-session retention review.
  422. ---
  423. ## Session structure / retention
  424. ### 15. game-design-goal-density-and-immediacy-audit
  425. **What it does:**
  426. Audits a game, feature, or metagame layer for goal density, goal immediacy, short/mid/long-term goal spread, safe session closure, and return triggers.
  427. **Use it when:**
  428. - players return and do not know what to do next
  429. - a game feels aimless, overwhelming, or brittle across session lengths
  430. - you want to evaluate how well the design fits fragmented player time
  431. - you need a structured breakdown of short-term, mid-term, and long-term goals
  432. **Best for:**
  433. Session structure, return-player experience, and retention-oriented goal design.
  434. ---
  435. ### game-design-friction-journey-audit
  436. **What it does:**
  437. Audits a game, feature flow, economy path, onboarding journey, progression chain, or live-ops loop for friction quality and friction accumulation.
  438. **Use it when:**
  439. - players stall, disengage, or churn and the reason is not yet clear
  440. - you need to distinguish meaningful challenge from harmful obstruction
  441. - waiting, confusion, resource pressure, or dependency chains may be stacking badly
  442. - a system feels sticky in the wrong way
  443. **Best for:**
  444. Journey mapping, friction diagnosis, and challenge-versus-frustration analysis.
  445. ---
  446. ### game-design-player-values-mapper
  447. **What it does:**
  448. Infers a player's underlying values and motivational priorities from behavior, then translates those into design implications.
  449. **Use it when:**
  450. - you need behavior-first personalization or segmentation
  451. - players behave differently from what the design assumed they would value
  452. - you want better targeting for events, missions, offers, or adaptive guidance
  453. - you need a practical values profile instead of a demographic label
  454. **Best for:**
  455. Behavior-first player profiling, value-alignment diagnosis, and personalization framing.
  456. ---
  457. ### game-design-player-perspective-reframe
  458. **What it does:**
  459. Reframes a player's current situation to reveal new meaning, goals, roles, or playstyles without changing the underlying mechanics.
  460. **Use it when:**
  461. - players are not literally blocked, but their interpretation of the current state has gone stale
  462. - you want to design re-engagement prompts, adaptive guidance, or alternate challenge framing
  463. - a system has meaningful options available, but players no longer recognize them as interesting or purposeful
  464. - you need to judge whether reframing is appropriate or whether the real issue is structural
  465. **Best for:**
  466. Stagnation recovery, adaptive guidance, and alternate-goal reframing when the core system is still fundamentally sound.
  467. ---
  468. ### game-design-social-satisfaction-matrix
  469. **What it does:**
  470. Evaluates a game's social features and multiplayer elements by their potential to create social satisfaction versus social dissatisfaction.
  471. **Use it when:**
  472. - you need to classify social features as basic, critical, booster, or secondary
  473. - you are auditing chat, voice, gifting, guilds, lobbies, reporting, hubs, friend systems, or profile surfaces
  474. - you want to reduce social risk while increasing social stickiness
  475. - the team is treating all social features as equally important or equally dangerous
  476. **Best for:**
  477. Social feature prioritization, social UX risk/opportunity mapping, and multiplayer stickiness analysis.
  478. ---
  479. ### game-design-prosocial-session-chapters
  480. **What it does:**
  481. Designs or audits prosocial experiences in session-based multiplayer games using a three-phase model built around Setup, Little Loops, and Long Tail.
  482. **Use it when:**
  483. - you are evaluating co-op games, team shooters, MOBAs, mission-based multiplayer, or other repeat-session formats
  484. - you want to prime trust before play, reinforce repeatable helping behaviors during play, and preserve positive momentum after play
  485. - a multiplayer game feels socially flat, hostile, forgettable, or unable to turn one good match into another
  486. - you need a time-structured prosocial lens rather than a static feature checklist
  487. **Best for:**
  488. Session-based prosocial design, trust-building arc analysis, and repeat-session social experience tuning.
  489. ---
  490. ## Publishing / pitch support
  491. ### 16. game-design-pitch-deck-audit
  492. **What it does:**
  493. Audits a game pitch deck for structure, clarity, persuasiveness, readability, business-case completeness, and publisher-fit.
  494. **Use it when:**
  495. - preparing a deck for publishers or funders
  496. - checking whether the deck answers who / what / why / when / budget / opportunity
  497. - polishing a deck before sending it asynchronously
  498. **Best for:**
  499. Pitch-deck review and publishing-readiness feedback.
  500. ---
  501. ### 16.5 game-design-one-page-design-doc
  502. **What it does:**
  503. Creates a concise one-page game design document and exports it as both markdown and PDF.
  504. **Use it when:**
  505. - the team needs a compact one-pager instead of a bloated GDD
  506. - rough game notes need to be compressed into a pitchable, readable concept sheet
  507. - you want one document that captures identity, pillars, summary, features, interface, style, sound, audience, and milestone framing
  508. **Best for:**
  509. One-page design communication, compact concept documentation, and pitch-friendly internal summaries.
  510. ---
  511. ### 17. design-red-team-audit
  512. **What it does:**
  513. Performs an adversarial design pre-mortem that assumes a feature, system, pitch, or roadmap idea fails, then identifies the most credible mechanisms of failure.
  514. **Use it when:**
  515. - a concept sounds persuasive on paper and you want to pressure-test it
  516. - you want a hostile-but-constructive critique before production
  517. - you need to expose weak assumptions, rollout risks, MVP traps, or misleading metrics
  518. **Best for:**
  519. Pre-mortems, risk exposure, and hard design challenge sessions.
  520. ---
  521. ### 18. game-design-prototyping-companion
  522. **What it does:**
  523. Tracks prototype branches, dead ends, parked ideas, and next experiments, and can support simple branch-map visualization workflows.
  524. **Use it when:**
  525. - a prototype creates multiple follow-up paths
  526. - you want to preserve design learning across branches
  527. - the team needs a structured record of what was tried, learned, chosen, or parked
  528. **Best for:**
  529. Prototype logging, branch tracking, and experiment continuity.
  530. ---
  531. ### 19. game-design-brainstorm-methods
  532. **What it does:**
  533. Applies named brainstorming methods such as SCAMPER, How Might We, Crazy 8s, Six Thinking Hats, Brainwriting 6-3-5, Worst Possible Idea, Lotus Blossom, forced connections, and morphological matrix to game design problems.
  534. **Use it when:**
  535. - the team wants method-driven ideation instead of generic brainstorming
  536. - you need the right brainstorming framework for the problem
  537. - you want ideation that ends in a shortlist or next move
  538. **Best for:**
  539. Structured ideation and facilitated brainstorming.
  540. ---
  541. ### 20. game-design-one-thing-to-remove
  542. **What it does:**
  543. Identifies the single highest-leverage thing to remove from a design in order to improve clarity, focus, pacing, emotional fit, or production sustainability.
  544. **Use it when:**
  545. - a feature feels bloated or overengineered
  546. - a system has too much friction or redundant complexity
  547. - you want a subtractive critique rather than another additive brainstorm
  548. **Best for:**
  549. Subtractive design audits and elegance-through-removal decisions.
  550. ---
  551. ### 21. game-design-novelty-spectrum-audit
  552. **What it does:**
  553. Evaluates a concept on the spectrum between too familiar and too novel using player expectations, mental models, and innovation pattern diagnosis.
  554. **Use it when:**
  555. - you want to know whether a concept is too derivative or too risky
  556. - you need to assess familiarity anchors versus real novelty
  557. - you want to classify innovation as incremental, recombinational, simplifying, or more radical
  558. **Best for:**
  559. Novelty positioning, concept differentiation, and expectation-risk analysis.
  560. ---
  561. ### 22. game-design-systematizing-empathizing-audit
  562. **What it does:**
  563. Positions a design on two axes — systematizing and empathizing — then infers likely player/persona appeal, likely rejection patterns, and the practical consequences of that positioning.
  564. **Use it when:**
  565. - you want to understand whether a design is logic-driven, emotionally player-attuned, or both
  566. - you want to know what kind of player this design is really for
  567. - you need a structural-emotional positioning read without assuming one quadrant is ideal
  568. **Best for:**
  569. Audience-fit diagnostics, structural-emotional positioning, and persona-oriented feature evaluation.
  570. ---
  571. ### 23. game-design-kpi-coverage-audit
  572. **What it does:**
  573. Audits whether a feature is being judged fairly by the KPI framework around it, especially when connective tissue, UX, QoL, enabling work, or sustainability value are being undervalued because they are hard to measure directly.
  574. **Use it when:**
  575. - a feature has obvious design value but weak direct KPI attribution
  576. - the roadmap favors flashy self-contained systems over support work
  577. - the team may be neglecting foundational improvements because they are hard to justify cleanly
  578. **Best for:**
  579. KPI blind-spot diagnosis, roadmap fairness, and support-feature justification.
  580. ---
  581. ### 24. game-design-prototype-intent-audit
  582. **What it does:**
  583. Audits whether a prototype is meant to sell the idea or reveal unknowns, and whether its scope actually matches that purpose.
  584. **Use it when:**
  585. - a prototype plan feels vague or contradictory
  586. - the team may be building a demo while claiming it is for learning
  587. - precious prototype time is being spent on the wrong questions
  588. **Best for:**
  589. Prototype strategy, prototype-scoping, and demo-vs-learning clarity.
  590. ---
  591. ### 25. game-design-player-segment-perception-audit
  592. **What it does:**
  593. Audits how different player segments are likely to perceive a feature, update, or content drop, especially when the feature is aimed at one cohort but visible to many others.
  594. **Use it when:**
  595. - a feature is targeted at elder or niche players but broadly marketed
  596. - you want to know how new, mid, and elder players will read the same update differently
  597. - you need to catch disappointment caused by visibility-access mismatch
  598. **Best for:**
  599. Segment targeting, feature rollout messaging, and cross-cohort perception analysis.
  600. ---
  601. ## Example prompt pack for the 4 game-dev skills
  602. Use the same concept across all four skills to get a beginner-friendly planning stack from first steps -> team gaps -> budget -> timeline.
  603. ### 1. game-dev-first-steps
  604. > I want to make a small PC creature-battler with light base-building and asynchronous trading. We are two people: one programmer and one 2D artist. What should we build first, what should we postpone, and what should our smallest believable prototype be?
  605. ### 2. game-dev-team-gap
  606. > We want to make a small PC creature-battler with light base-building and asynchronous trading. We are two people: one programmer and one 2D artist. What roles or skills are we missing for a prototype and later for a vertical slice?
  607. ### 3. game-dev-budget-estimator
  608. > We want to make a small PC creature-battler with light base-building and asynchronous trading. We are two people: one programmer and one 2D artist, both part-time in Eastern Europe. What rough budget should we expect for a prototype and for a vertical slice, and what costs are probably not covered by our team?
  609. ### 4. game-dev-time-estimator
  610. > We want to make a small PC creature-battler with light base-building and asynchronous trading. We are two people: one programmer and one 2D artist, both part-time. How long would a prototype and a vertical slice likely take, what would bottleneck us, and is 6 months realistic for the vertical slice?
  611. ### Fast comparison pack
  612. Use these when you want to test skill boundaries quickly.
  613. - **First steps:** What should we build first?
  614. - **Team gap:** Who are we missing?
  615. - **Budget:** What will this likely cost?
  616. - **Time:** How long will this likely take?
  617. ## How to use
  618. ### In OpenClaw
  619. Place the skill folders in your workspace `skills/` directory.
  620. ### As packaged files
  621. Use the `.skill` archives from `package-skills/` for sharing or installation.
  622. ## Notes
  623. - Some skills are **audit skills** (diagnose what is true, weak, missing, or risky).
  624. - Some skills are **workflow skills** (help move from ambiguity to action).
  625. - Some intentionally overlap a bit; that is by design. Different framing lenses are useful in different conversations.
  626. ## Best starting points
  627. If you are not sure where to begin:
  628. - vague concept -> `game-design-goal-framing`
  629. - no good options yet -> `game-design-option-generation`
  630. - emotionally flat idea -> `game-design-emotional-canvas`
  631. - suspicious engagement loop -> `game-design-player-motivation-audit`
  632. - need to audit social systems, multiplayer structure, or community/status fit -> `game-design-multiplayer-feature-audit`
  633. - weak onboarding -> `game-design-ftue-hero-journey-audit`
  634. - unclear session structure -> `game-design-goal-density-and-immediacy-audit`
  635. - need to map where challenge becomes harmful friction -> `game-design-friction-journey-audit`
  636. - need a behavior-first values profile for personalization or targeting -> `game-design-player-values-mapper`
  637. - player is not truly blocked, but their reading of the current state has gone stale -> `game-design-player-perspective-reframe`
  638. - need to classify social features by satisfaction upside versus dissatisfaction risk -> `game-design-social-satisfaction-matrix`
  639. - need to design prosociality across the arc of repeated multiplayer sessions -> `game-design-prosocial-session-chapters`
  640. - stale discussion -> `game-design-creative-unblocker`
  641. - unclear prototype needs -> `game-design-unknown-unknowns-prototyping`
  642. - upcoming publisher conversation -> `game-design-pitch-deck-audit`
  643. - need to audit whether the design asks for the right kind of cognition -> `game-design-thinking-fast-and-slow-audit`
  644. - need to audit which moments and endings dominate memory -> `game-design-peak-end-audit`
  645. - need to audit whether unfinished business creates momentum or guilt -> `game-design-zeigarnik-effect-audit`
  646. - need structured brainstorming methods -> `game-design-brainstorm-methods`
  647. - suspect the best improvement is subtraction -> `game-design-one-thing-to-remove`
  648. - not sure if the concept is too familiar or too novel -> `game-design-novelty-spectrum-audit`
  649. - want to understand who the design emotionally/structurally appeals to -> `game-design-systematizing-empathizing-audit`
  650. - suspect the KPI framing is undervaluing connective tissue or QoL work -> `game-design-kpi-coverage-audit`
  651. - unclear whether a prototype is for selling or learning -> `game-design-prototype-intent-audit`
  652. - worried different player cohorts will read the same feature differently -> `game-design-player-segment-perception-audit`
  653. ## Licence
  654. These skills are published under the
  655. [PolyForm Noncommercial License 1.0.0](./LICENSE).
  656. Free to use, modify, fork and share for:
  657. - personal projects, hobby games and self-directed learning
  658. - students, teachers and educational institutions
  659. - charities, public research organisations and government bodies
  660. A commercial licence is required for:
  661. - use inside a company developing, publishing or operating a game
  662. - consulting, contracting or agency work delivered to clients
  663. - paid training, workshops or courses
  664. - redistributing or reselling these skills, including repackaging them for an
  665. agent-skill marketplace
  666. Commercial licences are sold as skill packs. See
  667. [COMMERCIAL-LICENSE.md](./COMMERCIAL-LICENSE.md).
  668. This is a source-available licence, not an OSI-approved open source one. The
  669. Open Source Definition does not allow a restriction on field of use, so
  670. noncommercial licences fall outside it. If you assumed MIT-style terms because
  671. the repository is public, they do not apply here.
  672. If you copy a skill folder out of this repository on its own, the licence line
  673. at the bottom of its `SKILL.md` and the Required Notice in `LICENSE` need to
  674. travel with it.
  675. The frameworks these skills draw on belong to their authors and are credited in
  676. [CREDITS.md](./CREDITS.md). The licence covers the skill instructions and
  677. wording here, not the theory underneath.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.