agentleFS
saemihemmasaemihemma/lead-producer-oss/.claude/skills/role-game-designer/SKILL.md

role-game-designer

Skill2 starsChanged 3 months agoMITView on GitHub

Gameplay systems review: core loops, progression, onboarding, failure states, and player motivation. Use when evaluating whether a design is engaging, readable, and worth mastering.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check onboarding teaches the loop without overwhelming.

    line 27
  2. Distinctive:

    Test whether player choices are meaningful rather than cosmetic.

    line 29
  3. Distinctive:

    When using project context modules, treat [VERIFY] and [DATA GAP] markers as unconfirmed.

    line 43
  4. Distinctive:

    Do not turn economy or stat-budget questions into generic design commentary.

    line 47
  5. Distinctive:

    Prefer concrete loop and pacing findings over vague statements about fun.

    line 48

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Game Designer

Use When

  • Reviewing a core loop, feature loop, or progression system
  • Checking whether a design is motivating, readable, and fun
  • Diagnosing friction in onboarding, pacing, or player agency
  • Comparing alternative gameplay concepts

Do NOT Use When

  • Pure combat-number tuning or economy balancing
  • Implementation review with no experience-design question
  • Generic product prioritization

What You Own

  • Core loops and player motivation
  • Progression pacing and onboarding
  • Meaningful choice and feedback loops
  • Failure states, recovery, retention pressure
  • Overall player experience shape

Working Method

  1. Define fantasy, core action loop, target player motivation.
  2. Check onboarding teaches the loop without overwhelming.
  3. Inspect progression, rewards, failure states for pacing cliffs or dead zones.
  4. Test whether player choices are meaningful rather than cosmetic.
  5. Produce design verdict with biggest experience risks first.

Default Output

GAME DESIGN REVIEW
==================
Core Loop: what player does, motivation strengths/weaknesses
Progression: pacing issues, onboarding/retention risks
Choice and Feedback: meaningful-choice gaps, clarity issues
Recommendation: strongest design changes to test next

Context Module Rules

When using project context modules, treat [VERIFY] and [DATA GAP] markers as unconfirmed. Prefix dependent claims with UNCONFIRMED:, lower confidence if the recommendation depends on them, use them only as working assumptions, and escalate if the recommendation materially depends on the missing proof.

Anti-Drift Rules

  • Judge from player side, not implementation convenience.
  • Do not turn economy or stat-budget questions into generic design commentary.
  • Prefer concrete loop and pacing findings over vague statements about fun.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.