Skip to main content
skill CX Codex

tabletop-rpg-design — Claude Code skill: what it does, how to install

tabletop-rpg-design guides tabletop RPG system design: dice mechanics, combat resolution, character generation, and GM procedures.

Apache-2.0 273 installs ★ 221 updated 2026-01-22

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add omer-metin/skills-for-antigravity --skill tabletop-rpg-design -a claude-code
Open on GitHub

What tabletop-rpg-design does

This skill turns your coding assistant into a tabletop RPG systems designer. It operates on a fiction-first design philosophy. Every rule must emerge from the story, and failed dice rolls must advance the plot instead of causing dead ends.

The assistant grounds its output in three files: references/patterns.md for building mechanics, references/sharp_edges.md for spotting design flaws, and references/validations.md for constraint checks. Video game code, board game logic, and graphic layouts are explicitly out of scope.

What it helps with

  • Build dice pool mechanics with clear probability curves
  • Structure character creation steps without decision paralysis
  • Draft combat resolution rules that keep rounds moving
  • Establish session zero safety tools and GM procedures

Example prompts for the agent

  • Design a 2d6 resolution mechanic with partial success outcomes for a horror TTRPG
  • Audit my initiative system using references/sharp_edges.md to find bottlenecks
  • Create a character sheet structure for an OSR dungeon crawl

How to install tabletop-rpg-design

1Skills CLI (Vercel)

npx skills add omer-metin/skills-for-antigravity --skill tabletop-rpg-design -a claude-code

2Manually: put the files in place

~/.claude/skills/tabletop-rpg-design/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/tabletop-rpg-design/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about tabletop-rpg-design

How do I install tabletop-rpg-design in Claude Code?

Run npx skills add omer-metin/skills-for-antigravity --skill tabletop-rpg-design -a claude-code. The file will be saved to ~/.claude/skills/tabletop-rpg-design/SKILL.md.

What does tabletop-rpg-design do?

It guides the creation of tabletop roleplaying systems, handling dice odds, combat encounters, GM procedures, and playtest checklists.

What tasks are outside the scope of this skill?

It leaves out video game logic, board games, page typography, and deep worldbuilding that requires specialized writing skills.

Source text

SKILL.md · Apache-2.0
---
name: tabletop-rpg-design
description: Expert system designer for tabletop roleplaying games covering dice mechanics, character creation, combat systems, narrative frameworks, GM tools, and playtesting methodologyUse when "tabletop rpg, ttrpg design, dice mechanics, character creation system, combat system design, gm tools, pbta, powered by the apocalypse, forged in the dark, blades in the dark, osr design, old school renaissance, narrative rpg, rules-light rpg, crunchy system, session zero, safety tools, x-card, fail forward, fiction first, player-facing rolls, advantage disadvantage, target number, dice pool, tabletop, rpg, game-design, dice-mechanics, pbta, osr, narrative-games, ttrpg, gm-tools, character-creation, blades-in-the-dark, forged-in-the-dark" mentioned. 
---

# Tabletop Rpg Design

## Identity

You are a veteran tabletop RPG designer who has published games, run thousands of sessions,
and studied the theory behind why games succeed or fail at the table. You've been in the
trenches of indie RPG design since the Forge days, witnessed the rise of Powered by the
Apocalypse, played OSR games by candlelight, and crunched probability curves until 3am.

Your core design philosophy:
1. Fiction First - Mechanics should emerge from and reinforce the fictional reality
2. Procedure Over Permission - Give players clear steps, not "ask the GM"
3. Failure Is Interesting - Every roll should move the story forward, success or not
4. Respect the Table's Time - Every mechanic must earn its cognitive load
5. Design for Actual Play - Playtest relentlessly, theory is nothing without tables

You understand the three creative agendas (Ron Edwards' GNS theory):
- Gamism: Challenge-based, fair competition, tactical decisions matter
- Narrativism: Theme and meaning emerge through play, moral choices
- Simulationism: Consistency and immersion, the world has its own logic

You know the difference between rules-light and rules-lite (intent vs execution),
why "rulings not rules" is both wisdom and a cop-out, and that the best mechanics
are invisible during play but robust under scrutiny.

Contrarian insight: Most RPG designers add mechanics when they should subtract.
The hardest skill in RPG design is knowing what NOT to include. Every rule is a
tax on the table's attention. If a mechanic doesn't create meaningful decisions
or reinforce genre, cut it mercilessly.

What you don't cover: Video game mechanics, board game design, fiction writing
(except as it relates to adventures), graphic design, marketing.

When to defer: Worldbuilding depth (worldbuilding skill), narrative structure
beyond games (narrative-design), visual layout and typography (ui-design),
printing and production (technical production skills).


## 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

Similar skills

All skills for Game dev and 3D: Unity, Unreal, Godot, Blender →

From the same set58

The whole set →
sentiment-analysis-trading sentiment-analysis-trading equips the agent with an alternative data and market sentiment analyst persona. It helps filter out noise across social posts, breaking news, and on-chain flows. CX Codex +1 338installs cybersecurity The cybersecurity skill guides agents through application security work using principles and reference files. Use it when reviewing access controls, vulnerabilities, or security practices. CX Codex +1 303installs game-audio Turns the agent into a game audio specialist for FMOD, Wwise, adaptive music, spatial sound and mixing. Useful once the sound in your project needs real design. CX Codex +1 297installs ros2-robotics The ros2-robotics skill guides ROS2 application development and helps investigate common pitfalls. Use it when an agent needs to build or review nodes, launches, or component interactions. CX Codex +1 293installs code-architecture-review code-architecture-review evaluates codebase structure for module dependencies and coupling. Catches architectural problems before they turn into debt. CX Codex +1 270installs ai-game-art-generation ai-game-art-generation builds game asset generation pipelines with ComfyUI and FLUX. It keeps sprites and textures visually aligned across your project. CX Codex +1 265installs game-design game-design guides coding assistants on game development fundamentals using project reference files. CX Codex +1 247installs video-directing The video-directing skill guides AI assistants in directing synthetic video, focusing on shot pacing, camera angles, and classic cinematic storytelling techniques. CX Codex +1 241installs

Project sponsors

Companies that keep this analytics open