Game design roadblock reframing

Skill Stanestane/game-design-skills-bundle/game-design-roadblock-reframing

Reframe 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.From its SKILL.md

Install

npx -y skills add Stanestane/game-design-skills-bundle --skill game-design-roadblock-reframing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

SKILL.md

2.2 KB, 406 tokens by cl100k_base, as published. Nobody here has run it

Game Design Roadblock Reframing

Get unstuck by changing the angle of the problem.

Use this skill when one blocker has become mentally larger than the design space around it. The aim is not to deny the blocker. The aim is to remove it temporarily, inspect what becomes possible, and then derive realistic paths around, under, or over it.

Read references/family-conventions.md when you need the shared conventions for this GROW-derived skill family.

What to produce

Generate:

Roadblock definition - what is blocking progress
Unblocked reality - what the design would look like if that blocker vanished
Workaround paths - how to approach that unblocked state without magic
Recommendation - which path is most credible now

Process

1. Name the blocker clearly

Define:

what the roadblock is
why it matters
how it is constraining design thinking

2. Imagine it removed

Ask:

if this disappeared overnight, what would we want to do?
what would the feature or system look like then?
what value are we actually trying to protect or create?

3. Derive workaround paths

From the unblocked version, ask:

what partial version is achievable now
what adjacent solution gets us close enough
what substitute mechanism could create similar value
what sequencing change could bypass the blocker for now

4. Choose the strongest path

Select the workaround that best preserves value with acceptable cost and risk.

Response structure

Roadblock

Unblocked Reality

Workaround Paths

Recommendation

Fast mode

What is the blocker?
If it disappeared, what would we do?
What is the nearest realistic version of that outcome?

Working principle

Do not let one obstacle define the entire design space.

What ships with it: 1 file

1.3 KB alongside SKILL.md

references/

family-conventions.md1.3 KB

Gives 0 of the 12 instructions most design frontend skills give in 406 tokens

Counted across 1,169 of the 1,878 authors here whose files we hold, read 2026-08-07

Use CSS variables for color consistencyin 72 of 1169, across 23 files
Commit to one bold aesthetic direction before codingin 72 of 1169, across 27 files
Match implementation complexity to the aesthetic visionin 70 of 1169, across 20 files
Add atmospheric background effects and texturesin 57 of 1169, across 9 files
Use unexpected spatial compositions and layoutsin 56 of 1169, across 8 files
Implement real working codein 55 of 1169, across 7 files
Vary themes and aesthetics across different designsin 48 of 1169, across 7 files
Launch chromium in headless modein 47 of 1169, across 4 files
Close the browser when donein 47 of 1169, across 4 files
Run provided scripts with help flag firstin 47 of 1169, across 4 files
Wait for network idle statein 47 of 1169, across 4 files
Use descriptive selectors for elementsin 47 of 1169, across 4 files

Said here and by no other author read

Define the blocker
Imagine the blocker removed
Derive workaround paths
Choose the strongest path
Preserve value with acceptable cost
Do not let one obstacle define the entire design space

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.