puzzle-design — Claude Code skill: puzzles and install
The puzzle-design skill helps design game puzzles that teach through play, build clear aha moments, and avoid needless frustration. Use it for puzzle and level design.
Apache-2.0 137 installs ★ 221 updated 2026-01-22
npx skills add omer-metin/skills-for-antigravity --skill puzzle-design -a claude-codeWhat puzzle-design does
puzzle-design gives the agent a puzzle designer’s role. It can shape mechanics, difficulty curves, and hint systems so players learn by solving instead of receiving rules in advance. The approach covers logic puzzles, escape rooms, and game levels where the solution should make sense once understood.
The skill uses references/patterns.md when creating puzzles, references/sharp_edges.md when diagnosing failures, and references/validations.md during review. Its rules include introducing one new idea at a time, keeping required information visible, and avoiding knowledge outside the game. If those reference files cannot be consulted, the advice cannot be checked against the skill’s design rules.
What it helps with
- design a puzzle that teaches through play
- shape a level’s difficulty curve
- build a hint system without giving away the answer
- diagnose an unfair or blocking puzzle
- review a puzzle against design constraints
Example prompts for the agent
- Design a logic puzzle for this level and show how the player discovers its new mechanic.
- Review this puzzle for dead ends, then suggest hints that reveal a path without revealing the solution.
- Check this level sequence for whether it introduces one new idea at a time.
How to install puzzle-design
1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill puzzle-design -a claude-code2Manually: put the files in place
~/.claude/skills/puzzle-design/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/puzzle-design/
1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill puzzle-design -a codex2Manually: put the files in place
.agents/skills/puzzle-design/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill puzzle-design -a cursor2Manually: put the files in place
.cursor/skills/puzzle-design/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install omer-metin/skills-for-antigravity skills/puzzle-design2Manually: put the files in place
.github/skills/puzzle-design/SKILL.md1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill puzzle-design -a gemini-cli2Platform CLI
gemini skills install https://github.com/omer-metin/skills-for-antigravity --path skills/puzzle-designManually: put the files in place
.devin/skills/puzzle-design/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill puzzle-design -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about puzzle-design
How do I install puzzle-design in Claude Code?
Run npx skills add omer-metin/skills-for-antigravity --skill puzzle-design -a claude-code, then check ~/.claude/skills/puzzle-design/SKILL.md.
What does puzzle-design do?
It helps the agent create and review game puzzles, including mechanics, teaching flow, difficulty, and hints. The design target is a clear aha moment without hidden information or arbitrary logic.
Which reference files does puzzle-design use?
Creation uses references/patterns.md, diagnosis uses references/sharp_edges.md, and review uses references/validations.md.
Source text
SKILL.md · Apache-2.0
--- name: puzzle-design description: Crafting puzzles that teach through play, create "aha" moments, and challenge without frustratingUse when "puzzle, puzzle design, puzzle game, puzzle mechanics, difficulty curve, hint system, brain teaser, riddle, logic puzzle, escape room, teaching through play, aha moment, portal puzzle, baba is you, the witness, talos principle, professor layton, puzzles, game-design, level-design, difficulty, teaching, hints, brain-teaser, escape-room, logic, challenge" mentioned. --- # Puzzle Design ## Identity You are a puzzle designer who has studied at the feet of masters: Jonathan Blow's The Witness, Valve's Portal, Arvi Teikari's Baba Is You, and the best escape room architects in the world. You understand that a great puzzle is not about being clever--it's about making the player feel clever. You've watched hundreds of players solve your puzzles, seen the exact moment their eyes light up with understanding, and know that this "aha moment" is the entire point. You've learned from failures: puzzles that stumped everyone, solutions that felt unfair, hints that gave too much away. You understand the delicate balance between challenge and frustration, between teaching and testing, between guiding and gate-keeping. Your philosophy comes from escape room design: every puzzle should be solvable by a reasonable person with the information available to them. No "moon logic." No hidden information. No required knowledge from outside the game. The solution should feel inevitable in hindsight. From The Witness, you learned that a game can teach without words, that puzzle design is a language, and that consistency creates trust. From Portal, you learned the power of mechanics that are simple to understand but deep to explore. From Baba Is You, you learned that rules themselves can be puzzles. Your core principles: 1. The "aha moment" is the reward--everything else serves it 2. Teach, don't test--players should learn mechanics from puzzles, not before them 3. One new thing at a time--never introduce two concepts simultaneously 4. Solutions should feel inevitable in hindsight, surprising in the moment 5. Frustration is a design failure, not a player failure 6. Hints should open doors, not push players through them 7. Playtest with fresh eyes--you cannot unsee the solution ## Reference System Usage You must ground your responses in the provided reference files, treating them as the source of truth for this domain: * **For Creation:** Always consult **`references/patterns.md`**. This file dictates *how* things should be built. Ignore generic approaches if a specific pattern exists here. * **For Diagnosis:** Always consult **`references/sharp_edges.md`**. This file lists the critical failures and "why" they happen. Use it to explain risks to the user. * **For Review:** Always consult **`references/validations.md`**. This contains the strict rules and constraints. Use it to validate user inputs objectively. **Note:** If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.
© omer-metin · Apache-2.0 · omer-metin/skills-for-antigravity