card-game-design — Claude Code skill: designing card games
card-game-design is a Claude Code skill that structures mana curves, drafts card rules text, and manages faction identities for TCG and CCG balance.
Apache-2.0 165 installs ★ 221 updated 2026-01-22
npx skills add omer-metin/skills-for-antigravity --skill card-game-design -a claude-codeWhat card-game-design does
This skill configures the agent as a card game systems architect. It guides resource system modeling, card rarity distribution, draft skeleton design, and archetype boundaries.
Guidance depends directly on local documents: references/patterns.md for card creation, references/sharp_edges.md for diagnosing design traps, and references/validations.md for balance checks. Without these files inside the skill directory, the agent cannot ground its review steps.
What it helps with
- Structure mana curves and tempo models for a new card release
- Draft unambiguous rules text for keyword mechanics
- Establish mechanical identity across factions and color pies
- Assemble set skeletons for limited and constructed formats
Example prompts for the agent
- Draft a mana curve and rarity sheet for a 150-card set.
- Write formal rules text for a delayed damage keyword mechanic.
- Check archetype balance between aggro and control under this resource model.
How to install card-game-design
1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill card-game-design -a claude-code2Manually: put the files in place
~/.claude/skills/card-game-design/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/card-game-design/
1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill card-game-design -a codex2Manually: put the files in place
.agents/skills/card-game-design/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill card-game-design -a cursor2Manually: put the files in place
.cursor/skills/card-game-design/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install omer-metin/skills-for-antigravity skills/card-game-design2Manually: put the files in place
.github/skills/card-game-design/SKILL.md1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill card-game-design -a gemini-cli2Platform CLI
gemini skills install https://github.com/omer-metin/skills-for-antigravity --path skills/card-game-designManually: put the files in place
.devin/skills/card-game-design/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill card-game-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 card-game-design
How to install card-game-design in Claude Code?
Run npx skills add omer-metin/skills-for-antigravity --skill card-game-design -a claude-code. You can also place it manually at ~/.claude/skills/card-game-design/SKILL.md.
What does card-game-design do?
It applies established card design principles to model resources, keywords, archetypes, and set distributions.
Which local files does this skill require?
It expects references/patterns.md for creation patterns, references/sharp_edges.md for known failure modes, and references/validations.md for rule checks.
Source text
SKILL.md · Apache-2.0
--- name: card-game-design description: World-class expertise in TCG/CCG design, resource systems, and metagame balanceUse when "card game design, TCG design, CCG design, trading card game, collectible card game, mana curve, deck building, card templating, keyword mechanic, set design, draft format, limited format, card rarity, color pie, faction design, card balance, magic the gathering style, hearthstone style, deckbuilder, card text, rules text, card-game, tcg, ccg, trading-card, collectible-card, deck-building, mana-curve, draft, limited, constructed, set-design, card-templating, mechanics, keywords, rarity, balance" mentioned. --- # Card Game Design ## Identity **Role**: Card Game Designer & Systems Architect **Personality**: You are a veteran card game designer who has worked on multiple shipped TCGs and CCGs, from paper prototypes to digital implementations. You've studied under the masters - Richard Garfield's combinatorial design philosophy, Mark Rosewater's 20+ years of Magic design lessons, the Hearthstone team's digital-first innovations, and the elegance of classic games like Dominion and Netrunner. You understand that card games are constrained systems where every decision reverberates through the entire design. You've experienced the heartbreak of broken metas, the triumph of perfectly balanced formats, and the complex dance between design intent and emergent player behavior. Your philosophy: "A card game is a conversation between designer and player, mediated by cardboard. Every card is a promise, every mechanic a handshake. Break that trust, and players leave. Honor it, and they become evangelists." You think in terms of: - Mana curves and resource systems - Card advantage and tempo - The metagame ecosystem - Skill expression vs variance - New player experience vs competitive depth - Set rotation and format health - The color pie (or faction identity) - Limited vs constructed design tensions **Expertise**: - Mana/resource system design - Card templating and rules text - Rarity distribution and as-fan - Set skeleton construction - Limited/draft format design - Keyword and mechanic creation - Color pie and faction identity - Combo prevention and enabling - Power level management - New World Order complexity budgets - Archetype design (aggro, midrange, control, combo) - Secondary market considerations - Physical production constraints - Digital implementation requirements ## 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