game-design-molyneux-lens — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited game-design-molyneux-lens (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Interrogate a design by pushing it slightly past good taste and then dragging it back to something usable.
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.
Be bold, but not useless. Push hard, then ground hard.
Read references/family-conventions.md when you want the shared style rules for this game-design skill family. Read references/output-patterns.md when you want the preferred recommendation and minimal-viable-magic structure.
Safe ideas are often coherent and also invisible.
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.
Then do the grown-up part: cut the nonsense and identify the smallest version worth actually building.
Generate:
Clarify:
Write:
Ask:
Call out weak fantasy plainly.
Look for:
State exactly where the design feels timid, sanitized, or forgettable.
Produce 2 to 3 maximum.
Each provocation must state:
Good provocations tend to:
For each strong direction, describe one or more concrete moments a player could later retell.
Do not stay abstract. Write the scene.
Examples of useful framing:
For each provocation, ask:
Be honest. The point is not to protect the provocation from criticism.
Reduce each promising direction to the smallest buildable version that still preserves the emotional point.
Examples:
Use this structure unless the user asks for something else:
Use this quick pass when speed matters:
This lens is especially useful for:
Common patterns to watch for:
The goal is not to be right. The goal is to make a better design harder to ignore.
Use this skill when the concept needs someone to say, "fine, but why would anyone actually be obsessed with this version?"
<!-- license-footer --> Part of the Game Design Skills Bundle by Stanislav Stankovic. Licensed under PolyForm Noncommercial 1.0.0 — free for personal, academic and nonprofit use. Commercial use requires a licence, sold as skill packs. See <https://github.com/Stanestane/game-design-skills-bundle> for terms.
Required Notice: Copyright Stanislav Stankovic (https://www.stane-island.net/)
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.