game-design-one-thing-to-remove

Name: game-design-one-thing-to-remove
Author: Stanestane

34stars3forks

How to install game-design-one-thing-to-remove?

stanestane/game-design-skills-bundle/game-design-one-thing-to-remove

$npx -y skills add Stanestane/game-design-skills-bundle --skill game-design-one-thing-to-remove

Installs into the current project.

Summary

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 lo

Files · 1

View on GitHub

SKILL.md

1	# Game Design One Thing To Remove
2
3	Improve the design by cutting one thing, not by adding three more.
4
5	Use this skill when a design would likely become better through subtraction. The goal is not to nitpick random dislikes. The goal is to identify the one removal with the highest leverage: the thing whose absence would most improve clarity, pacing, focus, emotional impact, usability, production efficiency, or strategic coherence.
6
7	Read `references/removal-lenses.md` when deciding what kind of thing is most worth cutting.
8	Read `references/evaluation-patterns.md` when you need the exact output pattern.
9
10	## What to produce
11
12	Produce:
13	1. Design read - what the design is trying to do
14	2. Removal candidate - the one thing to remove
15	3. Why this removal has highest leverage - why this cut matters more than others
16	4. What improves if removed - concrete downstream effects
17	5. Tradeoff - what value is lost too
18	6. Value-preserving alternative - how to keep the good part without the bad part, if needed
19	7. Verdict - remove now, prototype without it, or cut later if evidence confirms
20
21	## Process
22
23	### 1. Understand what the design is trying to achieve
24	Clarify:
25	- the intended player experience
26	- the core loop or promise
27	- which parts feel central versus decorative
28	- what business, retention, content, or production realities matter
29
30	### 2. Look for subtractive opportunities
31	Check whether the design contains:
32	- redundant mechanics
33	- duplicate progression layers
34	- false choices
35	- low-value friction
36	- weak reward currencies
37	- tutorial clutter
38	- content burdens that add little value
39	- fantasy dilution
40	- complexity that does not create meaningful depth
41
42	### 3. Identify the highest-leverage removal
43	Pick one thing only.
44	Do not list five cuts unless the user explicitly asks.
45	Choose the removal whose absence would improve the design most significantly.
46
47	Good candidates include:
48	- one mechanic
49	- one progression layer
50	- one UI step
51	- one rule or constraint
52	- one reward type
53	- one content dependency
54	- one feature that muddies the fantasy
55
56	### 4. Explain the mechanism of improvement
57	Do not say only that the design becomes “cleaner.”
58	Explain exactly what improves, such as:
59	- comprehension
60	- pacing
61	- motivation
62	- readability
63	- strategic clarity
64	- production sustainability
65	- onboarding burden
66	- player trust
67	- emotional focus
68
69	### 5. Acknowledge the loss honestly
70	A good cut may still remove something useful.
71	State what is lost and whether that loss matters.
72	If appropriate, suggest a lighter substitute that preserves the upside without keeping the full problematic element.
73
74	### 6. Make a practical recommendation
75	End with a decision such as:
76	- remove now
77	- prototype without it
78	- keep for now, but cut if testing confirms the issue
79
80	## Response structure
81
82	### Design Read
83	- ...
84
85	### One Thing I Would Remove
86	- ...
87
88	### Why This Is the Highest-Leverage Cut
89	- ...
90
91	### What Improves If Removed
92	- ...
93
94	### What You Lose
95	- ...
96
97	### How To Preserve the Good Part Without the Bad Part
98	- ...
99
100	### Verdict
101	- ...
102
103	## Fast mode
104	- What is the design trying to do?
105	- What single element is hurting it most?
106	- Why is that element more worth cutting than anything else?
107	- What gets better if it disappears?
108	- What should replace it, if anything?
109
110	## Style rules
111	- Be decisive.
112	- Pick one thing.
113	- Prefer mechanism over taste.
114	- Do not recommend removal just because something is complex; complexity is acceptable if it creates real value.
115	- Distinguish between elegant subtraction and destructive oversimplification.
116	- If nothing should be removed, say that clearly and explain why.
117
118	## Working principle
119
120	Many designs get worse because every problem is answered with addition.
121	Sometimes the best improvement is subtraction with intent.

People who liked this also viewed

6 picks

Type

game-design-one-thing-to-remove

34stars3forks

View on GitHub

How to install game-design-one-thing-to-remove?

stanestane/game-design-skills-bundle/game-design-one-thing-to-remove

$npx -y skills add Stanestane/game-design-skills-bundle --skill game-design-one-thing-to-remove

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Game Design One Thing To Remove
2
3	Improve the design by cutting one thing, not by adding three more.
4
5	Use this skill when a design would likely become better through subtraction. The goal is not to nitpick random dislikes. The goal is to identify the one removal with the highest leverage: the thing whose absence would most improve clarity, pacing, focus, emotional impact, usability, production efficiency, or strategic coherence.
6
7	Read `references/removal-lenses.md` when deciding what kind of thing is most worth cutting.
8	Read `references/evaluation-patterns.md` when you need the exact output pattern.
9
10	## What to produce
11
12	Produce:
13	1. Design read - what the design is trying to do
14	2. Removal candidate - the one thing to remove
15	3. Why this removal has highest leverage - why this cut matters more than others
16	4. What improves if removed - concrete downstream effects
17	5. Tradeoff - what value is lost too
18	6. Value-preserving alternative - how to keep the good part without the bad part, if needed
19	7. Verdict - remove now, prototype without it, or cut later if evidence confirms
20
21	## Process
22
23	### 1. Understand what the design is trying to achieve
24	Clarify:
25	- the intended player experience
26	- the core loop or promise
27	- which parts feel central versus decorative
28	- what business, retention, content, or production realities matter
29
30	### 2. Look for subtractive opportunities
31	Check whether the design contains:
32	- redundant mechanics
33	- duplicate progression layers
34	- false choices
35	- low-value friction
36	- weak reward currencies
37	- tutorial clutter
38	- content burdens that add little value
39	- fantasy dilution
40	- complexity that does not create meaningful depth
41
42	### 3. Identify the highest-leverage removal
43	Pick one thing only.
44	Do not list five cuts unless the user explicitly asks.
45	Choose the removal whose absence would improve the design most significantly.
46
47	Good candidates include:
48	- one mechanic
49	- one progression layer
50	- one UI step
51	- one rule or constraint
52	- one reward type
53	- one content dependency
54	- one feature that muddies the fantasy
55
56	### 4. Explain the mechanism of improvement
57	Do not say only that the design becomes “cleaner.”
58	Explain exactly what improves, such as:
59	- comprehension
60	- pacing
61	- motivation
62	- readability
63	- strategic clarity
64	- production sustainability
65	- onboarding burden
66	- player trust
67	- emotional focus
68
69	### 5. Acknowledge the loss honestly
70	A good cut may still remove something useful.
71	State what is lost and whether that loss matters.
72	If appropriate, suggest a lighter substitute that preserves the upside without keeping the full problematic element.
73
74	### 6. Make a practical recommendation
75	End with a decision such as:
76	- remove now
77	- prototype without it
78	- keep for now, but cut if testing confirms the issue
79
80	## Response structure
81
82	### Design Read
83	- ...
84
85	### One Thing I Would Remove
86	- ...
87
88	### Why This Is the Highest-Leverage Cut
89	- ...
90
91	### What Improves If Removed
92	- ...
93
94	### What You Lose
95	- ...
96
97	### How To Preserve the Good Part Without the Bad Part
98	- ...
99
100	### Verdict
101	- ...
102
103	## Fast mode
104	- What is the design trying to do?
105	- What single element is hurting it most?
106	- Why is that element more worth cutting than anything else?
107	- What gets better if it disappears?
108	- What should replace it, if anything?
109
110	## Style rules
111	- Be decisive.
112	- Pick one thing.
113	- Prefer mechanism over taste.
114	- Do not recommend removal just because something is complex; complexity is acceptable if it creates real value.
115	- Distinguish between elegant subtraction and destructive oversimplification.
116	- If nothing should be removed, say that clearly and explain why.
117
118	## Working principle
119
120	Many designs get worse because every problem is answered with addition.
121	Sometimes the best improvement is subtraction with intent.

People who liked this also viewed

6 picks

Type