game-design-craft-critique
De la autor
Critically analyze an existing, shipped, third-party or competitor game for craft lessons, using a layered method (adapted from Raph Koster's "How I Analyze a Game") that separates a game's systems from its surface experience, guesses the intent behind each layer, and checks whether those intents actually line up. Use this whenever the user wants to study a released game, competitor title, or reference game in depth -- not just describe it, but understand why it's built the way it is and what to steal from it. Trigger on requests like "analyze [game]", "break down how [game] works", "what can we learn from [game]", "why does [game] feel so good/bad", or "study this competitor game." This is a game-study tool aimed at OTHER people's games, distinct from the feature-pitch and own-design audits elsewhere in this bundle -- though it also works as a systems-vs-experience alignment gut check on your own game once both layers exist enough to compare.
Instalare
npx skills add Stanestane/game-design-skills-bundle --skill game-design-craft-critique -a claude-code
Se instalează în .claude/skills/game-design-craft-critique/ · Fiecare comandă descarcă skill-ul direct de pe GitHub cu utilitarul open source skills.
Fără descărcare: licența acestui skill (Personalizată sau neclară) nu ne permite să-i redistribuim fișierele. Comenzile de instalare le iau direct de pe GitHub.
Vrei ca agentul să-ți propună skill-uri în timp ce scrii? Vezi cum folosești skill-urile din IDE.
Verificări de siguranță pe SKILL.md
Niciun avertisment.
De ce 75
aiqbench calculează scorul de încredere din semnale publice. Nu este un audit de securitate, așa că citește un skill înainte să-l instalezi.
Skill-uri similare
Cele mai apropiate de acesta prin ce fac și când sunt folosite.
- game-design-reviewYuki001/game-dev-skillsReview, critique, compare, improve, or stress-test an existing game concept, GDD, mechanic, puzzle, economy, level, theme, emotional arc, interface, narrative, social feature, prototype, pitch, or playtest result. Use when the user asks what is weak, risky, unclear, unbalanced, contradictory, insufficiently engaging, or worth validating next in a game design. Produce evidence-based findings, explicit tradeoffs, and the smallest useful prototype or playtest experiment.Design★ 100
- game-design-fairness-frustration-auditStanestane/game-design-skills-bundleAudit a game, feature, failure loop, combat encounter, reward system, progression wall, or high-variance mechanic for perceived fairness and frustration. Use when diagnosing whether players feel cheated, whether difficulty feels deserved, whether randomness, feedback, and challenge interact badly, or why a design remains technically functional yet still produces anger, blame, or refusal to retry.Design★ 86
- game-design-perceived-randomness-auditStanestane/game-design-skills-bundleAudit a game feature, combat system, loot table, reward loop, procedural system, chance mechanic, or uncertainty-driven design by how players are likely to perceive its randomness. Use when you need to evaluate whether a system will feel fair, streaky, rigged, sabotaging, manipulable, or skill-undermining; when players may misread independent events as patterned; or when randomness may sit too close to player action and create frustration. Analyze expectation gaps, gambler's-fallacy-style reactions, hidden pattern-seeking, input-versus-output randomness, perceived fairness, exploit risk, and ways to reshape presentation or mechanics.Design★ 86
- game-design-systematizing-empathizing-auditStanestane/game-design-skills-bundleEvaluate 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.Design★ 86
- game-design-attribution-auditStanestane/game-design-skills-bundleAudit a game, feature, combat scenario, progression step, failure state, onboarding beat, or reward outcome through the lens of attribution theory: how players explain success and failure. Use when evaluating whether players will blame themselves, the system, luck, or hidden rules; diagnosing perceived unfairness, learned helplessness, rage, or churn after losses; or identifying where clarity, control, and feedback are too weak for healthy learning.Design★ 86
- research-craftnik1t7n/research-craft-skillUse when planning, reviewing, or improving research work: choosing research problems, designing ML/AI experiments, reading papers, building experiment loops, analyzing outputs, writing research notes, or turning vague curiosity into a disciplined research plan. Emphasizes avoiding absorbed problems, upgrading information inputs beyond shared reading lists, and reasoning backward from outcomes the researcher genuinely wants to exist.Știință★ 50
Note și recenzii
—
nicio recenzie
Ai încercat acest skill? Notează-l ca să-i ajuți pe alții. Autentifică-te
Discuție
Intră în discuție. Autentifică-te