game-design-one-thing-to-remove
De la autor
Identify the single highest-leverage thing to remove from a game design, feature, system, UX flow, pitch, roadmap item, or prototype in order to improve it significantly. Use when a design feels bloated, muddy, overengineered, overly tutorialized, friction-heavy, or diluted by low-value mechanics, and you want a subtractive critique with rationale, tradeoffs, and a cleaner alternative.
Instalare
npx skills add Stanestane/game-design-skills-bundle --skill game-design-one-thing-to-remove -a claude-code
Se instalează în .claude/skills/game-design-one-thing-to-remove/ · 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-designericrisco/rsc-harnessUse when designing or repairing what makes a game fun — verbs and mechanics, moment-to-moment/session/meta loops, progression, economy faucets and sinks, difficulty curves, dominant strategies, juice, prototyping and scope. NOT engine code (that is `godot`), NOT story (that is `game-storytelling`), NOT level layout (that is `level-design`).Design★ 272
- game-design-feature-prioritizationStanestane/game-design-skills-bundlePrioritize game design feature options by comparing expected impact, implementation cost, strategic fit, and roadmap context. Use when choosing between competing feature ideas, deciding what to do now versus later, ranking solution paths after ideation, or identifying which option is best immediately and which is better long-term.Design★ 86
- game-design-transformative-reuseStanestane/game-design-skills-bundleSolve game design problems by adapting, extending, recombining, or retuning what already exists instead of inventing from scratch. Use when building on live systems, reusing content pipelines, stretching feature value, reducing production cost, or finding a lower-risk way to achieve a new purpose with existing mechanics, UX, progression structures, or content.Design★ 86
- game-design-design-pillars-extractorStanestane/game-design-skills-bundleExtract 3 to 5 actionable design pillars from a game, feature, loop, or system based on what the design actually rewards and prioritizes. Use when a team can describe mechanics but cannot clearly articulate the principles those mechanics serve, when pillars are vague, generic, or contradictory, or when you need a sharper set of tradeoff-driven pillars that can guide decisions and cut features.Design★ 86
- game-design-roadblock-reframingStanestane/game-design-skills-bundleReframe a game design problem by isolating the main blocker, imagining it removed, and using that perspective to discover workaround paths. Use when a team is stuck on one obstacle, when discussion keeps collapsing into 'we can't because', or when a feature, system, or plan feels trapped by a single technical, UX, content, or production roadblock.Design★ 86
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