game-design-molyneux-lens

Name: game-design-molyneux-lens
Author: Stanestane

34stars3forks

How to install game-design-molyneux-lens?

stanestane/game-design-skills-bundle/game-design-molyneux-lens

$npx -y skills add Stanestane/game-design-skills-bundle --skill game-design-molyneux-lens

Installs into the current project.

Summary

Stress-test a game concept, feature, system, or pitch through a deliberately provocative, ambition-seeking design lens inspired by Peter Molyneux-style overstatement. Use when a concept feels too safe, too polite, under-fantasized, mechanically competent but emotionally weak, or

Files · 1

View on GitHub

SKILL.md

1	# Game Design Molyneux Lens
2
3	Interrogate a design by pushing it slightly past good taste and then dragging it back to something usable.
4
5	Use this skill when a concept feels competent but bloodless, structurally fine but emotionally forgettable, or so cautious that nobody would remember it. This is not a neutral audit. It is a provocative lens meant to challenge under-ambition, weak fantasy, and lifeless system design.
6
7	Be bold, but not useless. Push hard, then ground hard.
8
9	Read `references/family-conventions.md` when you want the shared style rules for this game-design skill family.
10	Read `references/output-patterns.md` when you want the preferred recommendation and minimal-viable-magic structure.
11
12	## Core principle
13
14	Safe ideas are often coherent and also invisible.
15
16	This lens assumes many designs fail not because they are broken, but because they do not promise enough. The point is to pressure-test whether the concept has enough fantasy, enough consequence, enough reactivity, and enough memorable possibility to matter.
17
18	Then do the grown-up part: cut the nonsense and identify the smallest version worth actually building.
19
20	## Tone rules
21
22	- Be direct.
23	- Be slightly over the top, not parody-level ridiculous.
24	- Call out mediocrity when you see it.
25	- Offer only a few strong provocations, not a bucket of feature sludge.
26	- Tie every provocation back to player fantasy.
27	- Follow every bold idea with a reality check.
28
29	## What to produce
30
31	Generate:
32	1. Fantasy assessment - how strong, clear, and distinctive the core fantasy is
33	2. Safety callout - where the idea is timid, generic, or over-sanitized
34	3. Provocations - a small set of bold, high-upside pushes
35	4. Magic moments - concrete moments the stronger version could create
36	5. Reality check - what is vague, over-scoped, or technically dangerous
37	6. Minimal viable magic - the smallest grounded version that still carries the spark
38
39	## Process
40
41	### 1. Define the design target
42	Clarify:
43	- what exact concept, feature, or system is being challenged
44	- what fantasy it claims to serve
45	- what constraints matter
46
47	Write:
48	- Design target
49	- Claimed fantasy
50	- Practical constraints
51
52	### 2. Judge the core fantasy
53	Ask:
54	- Is the fantasy clear in one sentence?
55	- Would a player care emotionally, not just mechanically?
56	- Is this fantasy actually being delivered by the current systems?
57	- Is it distinctive, or does it smell like a genre placeholder?
58
59	Call out weak fantasy plainly.
60
61	### 3. Identify where the design is playing safe
62	Look for:
63	- predictable structure
64	- low consequence decisions
65	- reactive shallowness
66	- passive player role
67	- feature polish without experiential identity
68	- systems that function but do not produce stories
69
70	State exactly where the design feels timid, sanitized, or forgettable.
71
72	### 4. Generate a few strong provocations
73	Produce 2 to 3 maximum.
74
75	Each provocation must state:
76	- Bold idea
77	- Why it matters
78	- How it changes the fantasy
79	- What player behavior or emotion it unlocks
80
81	Good provocations tend to:
82	- increase player agency
83	- deepen system reactivity
84	- raise consequence
85	- sharpen fantasy identity
86	- create story-worthy moments
87
88	### 5. Describe the magic moments
89	For each strong direction, describe one or more concrete moments a player could later retell.
90
91	Do not stay abstract. Write the scene.
92
93	Examples of useful framing:
94	- "the moment the village remembers what you did"
95	- "the moment the market crashes because you manipulated trust"
96	- "the moment your pet disobeys because you trained it badly"
97
98	### 6. Run the reality check
99	For each provocation, ask:
100	- what is hand-wavy here?
101	- what is likely over-scoped?
102	- what is technologically or production-wise risky?
103	- what would collapse into smoke and hype if built lazily?
104
105	Be honest. The point is not to protect the provocation from criticism.
106
107	### 7. Extract the minimal viable magic
108	Reduce each promising direction to the smallest buildable version that still preserves the emotional point.
109
110	Examples:
111	- not a fully simulated society, but a small number of reactive factions
112	- not infinite emergent morality, but 3 persistent consequence tracks
113	- not godlike systemic freedom, but one deeply reactive toy with surprising range
114
115	## Response structure
116
117	Use this structure unless the user asks for something else:
118
119	### Design Target
120	- ...
121
122	### Fantasy Assessment
123	- ...
124
125	### Safety Callout
126	- ...
127
128	### Provocations
129	1. ...
130	2. ...
131	3. ...
132
133	### Magic Moments
134	- ...
135
136	### Reality Check
137	- ...
138
139	### Minimal Viable Magic
140	- ...
141
142	### Recommendation
143	- Push /

People who liked this also viewed

6 picks

Type

game-design-molyneux-lens

34stars3forks

View on GitHub

How to install game-design-molyneux-lens?

stanestane/game-design-skills-bundle/game-design-molyneux-lens

$npx -y skills add Stanestane/game-design-skills-bundle --skill game-design-molyneux-lens

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Game Design Molyneux Lens
2
3	Interrogate a design by pushing it slightly past good taste and then dragging it back to something usable.
4
5	Use this skill when a concept feels competent but bloodless, structurally fine but emotionally forgettable, or so cautious that nobody would remember it. This is not a neutral audit. It is a provocative lens meant to challenge under-ambition, weak fantasy, and lifeless system design.
6
7	Be bold, but not useless. Push hard, then ground hard.
8
9	Read `references/family-conventions.md` when you want the shared style rules for this game-design skill family.
10	Read `references/output-patterns.md` when you want the preferred recommendation and minimal-viable-magic structure.
11
12	## Core principle
13
14	Safe ideas are often coherent and also invisible.
15
16	This lens assumes many designs fail not because they are broken, but because they do not promise enough. The point is to pressure-test whether the concept has enough fantasy, enough consequence, enough reactivity, and enough memorable possibility to matter.
17
18	Then do the grown-up part: cut the nonsense and identify the smallest version worth actually building.
19
20	## Tone rules
21
22	- Be direct.
23	- Be slightly over the top, not parody-level ridiculous.
24	- Call out mediocrity when you see it.
25	- Offer only a few strong provocations, not a bucket of feature sludge.
26	- Tie every provocation back to player fantasy.
27	- Follow every bold idea with a reality check.
28
29	## What to produce
30
31	Generate:
32	1. Fantasy assessment - how strong, clear, and distinctive the core fantasy is
33	2. Safety callout - where the idea is timid, generic, or over-sanitized
34	3. Provocations - a small set of bold, high-upside pushes
35	4. Magic moments - concrete moments the stronger version could create
36	5. Reality check - what is vague, over-scoped, or technically dangerous
37	6. Minimal viable magic - the smallest grounded version that still carries the spark
38
39	## Process
40
41	### 1. Define the design target
42	Clarify:
43	- what exact concept, feature, or system is being challenged
44	- what fantasy it claims to serve
45	- what constraints matter
46
47	Write:
48	- Design target
49	- Claimed fantasy
50	- Practical constraints
51
52	### 2. Judge the core fantasy
53	Ask:
54	- Is the fantasy clear in one sentence?
55	- Would a player care emotionally, not just mechanically?
56	- Is this fantasy actually being delivered by the current systems?
57	- Is it distinctive, or does it smell like a genre placeholder?
58
59	Call out weak fantasy plainly.
60
61	### 3. Identify where the design is playing safe
62	Look for:
63	- predictable structure
64	- low consequence decisions
65	- reactive shallowness
66	- passive player role
67	- feature polish without experiential identity
68	- systems that function but do not produce stories
69
70	State exactly where the design feels timid, sanitized, or forgettable.
71
72	### 4. Generate a few strong provocations
73	Produce 2 to 3 maximum.
74
75	Each provocation must state:
76	- Bold idea
77	- Why it matters
78	- How it changes the fantasy
79	- What player behavior or emotion it unlocks
80
81	Good provocations tend to:
82	- increase player agency
83	- deepen system reactivity
84	- raise consequence
85	- sharpen fantasy identity
86	- create story-worthy moments
87
88	### 5. Describe the magic moments
89	For each strong direction, describe one or more concrete moments a player could later retell.
90
91	Do not stay abstract. Write the scene.
92
93	Examples of useful framing:
94	- "the moment the village remembers what you did"
95	- "the moment the market crashes because you manipulated trust"
96	- "the moment your pet disobeys because you trained it badly"
97
98	### 6. Run the reality check
99	For each provocation, ask:
100	- what is hand-wavy here?
101	- what is likely over-scoped?
102	- what is technologically or production-wise risky?
103	- what would collapse into smoke and hype if built lazily?
104
105	Be honest. The point is not to protect the provocation from criticism.
106
107	### 7. Extract the minimal viable magic
108	Reduce each promising direction to the smallest buildable version that still preserves the emotional point.
109
110	Examples:
111	- not a fully simulated society, but a small number of reactive factions
112	- not infinite emergent morality, but 3 persistent consequence tracks
113	- not godlike systemic freedom, but one deeply reactive toy with surprising range
114
115	## Response structure
116
117	Use this structure unless the user asks for something else:
118
119	### Design Target
120	- ...
121
122	### Fantasy Assessment
123	- ...
124
125	### Safety Callout
126	- ...
127
128	### Provocations
129	1. ...
130	2. ...
131	3. ...
132
133	### Magic Moments
134	- ...
135
136	### Reality Check
137	- ...
138
139	### Minimal Viable Magic
140	- ...
141
142	### Recommendation
143	- Push /

People who liked this also viewed

6 picks

Type