abstract-strategy
Design abstract strategy games with perfect information, no randomness, and strategic depth. Use when designing a board game, exploring abstract strategy games, brainstorming game mechanics, or evaluating game balance. Keywords: board game, game design, strategy, mechanics, balance.
What this skill does
# Abstract Strategy Game Design ## Purpose Design abstract strategy games—games with perfect information, no randomness, and strategic depth. Provides frameworks for ideation, design, and evaluation. ## Core Definition Abstract strategy games require: - **Perfect Information:** All game state visible to all players - **No Randomness:** Outcomes determined solely by player decisions - **Minimal Theme:** Mechanics over narrative - **Player Agency:** Success depends on strategic thinking --- ## Quick Reference: Game Types | Type | Core Mechanic | Examples | |------|---------------|----------| | Connection | Form paths/networks | Hex, TwixT | | Territory | Control areas | Go, Othello | | Capture | Eliminate pieces | Chess, Checkers | | Pattern | Create arrangements | Gomoku, Pentago | | Racing | Reach goal first | Chinese Checkers | --- ## Design Principles ### The Holy Grail: Depth-to-Complexity Ratio **Maximum strategic depth with minimum rules complexity.** How to achieve: - Start with single strong core mechanism - Remove anything that doesn't support the core - Every rule should create multiple strategic implications - Prefer emergent complexity over explicit rules ### Meaningful Decision Architecture Four components of meaningful choice: 1. **Awareness:** Players understand options 2. **Consequence:** Immediate and long-term effects 3. **Permanence:** Decisions have lasting impact 4. **Reminders:** Game state reflects past choices **Ideal Parameters:** - Branching factor: 20-40 moves/turn for human play - Horizon: 3-5 moves ahead with effort - Multiple paths: 3-4 viable strategies minimum --- ## Core Mechanisms Toolkit ### Board Topology - **Grids:** Square, hexagonal, triangular, irregular - **Connectivity:** How spaces relate - **Edges:** How boundaries affect strategy - **Size:** Larger = exponentially more complex ### Piece Systems - **Uniform:** All pieces identical (Go) - **Differentiated:** Unique abilities (Chess) - **Transforming:** Change during play (Checkers kings) - **Ownership:** Fixed vs. capturable ### Movement & Placement - **Placement only:** Pieces don't move once placed (Go) - **Movement only:** Pieces start on board (Chess) - **Hybrid:** Both placement and movement (Hive) ### Victory Conditions - Elimination, Position, Pattern, Territory, Points, Stalemate --- ## Balance Considerations ### First-Player Advantage Mitigation - **Pie Rule:** Second player can swap after first move - **Komi:** Point compensation for second player - **Variable Setup:** Randomized starting positions - **Simultaneous:** Both move at once ### Avoiding Degenerate Strategies - No single dominant path - Counter-strategies exist for every strong position - Passive play punishable - Aggressive play doesn't guarantee victory --- ## Design Process ### Three Starting Points **1. Mechanism-First** 1. Identify interesting core mechanic 2. Build minimal game around it 3. Add only what enhances core 4. Remove everything else **2. Experience-First** 1. Define target player experience 2. Identify mechanisms that create it 3. Prototype and test rapidly 4. Iterate on feedback **3. Constraint-Based** 1. Set specific limitations (components, time, space) 2. Find creative solutions within constraints 3. Often leads to elegant designs ### When to Add/Remove Complexity **Add when:** - Core feels solved too quickly - Players master in <10 plays - Decisions feel obvious **Remove when:** - Rules take >10 minutes - Players forget rules - Strategies feel arbitrary **Scrap when:** - No tweaking fixes fundamentals - Core mechanism isn't interesting - Feels like inferior version of existing game --- ## Brainstorming Techniques ### 1. Mechanism Extraction from Non-Games Extract from physics, biology, economics, chemistry, social systems: - Pieces that "decay" unless refreshed (entropy) - Moves creating "waves" along patterns (physics) - Pieces forming "bonds" limiting movement (chemistry) - "Market" squares with fluctuating values (economics) ### 2. Extreme Property Isolation Take one property to absolute extreme: - Game where pieces visible only when adjacent to your others - Every move must maintain rotational symmetry - Pieces exist only one turn unless refreshed - Board wraps in non-intuitive ways (Klein bottle) ### 3. Impossible Constraint Challenges Start with seemingly impossible constraints: - Game on a 1D line - Pieces in probability clouds until observed - Victory condition voted on by piece positions - Pieces leave "trails" becoming new pieces ### 4. Anti-Pattern Starting Points Design intentionally bad games, then invert: - Always-draw game → Add accumulating positional advantages - Pure calculation → Add pieces that change rules - Dominant strategy → Make it vulnerable to specific counters ### 5. Mathematical Structure Mining - Pieces move along Hamiltonian paths only - Positions valued by prime factorization - Fractal boards with repeating patterns - Moves must preserve mathematical invariants --- ## Evaluation Framework ### Strategic Richness Indicators **Depth:** - Games last 20+ meaningful turns - Opening, midgame, endgame feel distinct - Multiple viable opening strategies - Comebacks possible but not trivial **Complexity:** - New players grasp rules in <5 minutes - Experts keep discovering patterns - High-level play looks different from beginner ### Common Failures | Problem | Symptoms | Solution | |---------|----------|----------| | Analysis Paralysis | Excessive turn time | Limit options, clearer objectives | | Solved Game | Same outcome always | Increase branching, add variety | | Kingmaker | Loser picks winner | Simultaneous resolution | --- ## Testing Protocol ### Phase 1: Proof of Concept - Test core mechanic in isolation - Verify basic fun factor - Identify broken strategies ### Phase 2: Mechanics - Test each subsystem - Look for unintended interactions - Measure game length ### Phase 3: Integration - Full game, all systems - Different skill levels - Quantitative data ### Phase 4: Blind Testing - Players learn from rulebook only - Identify ambiguities - Test learning curve --- ## Testing Checklist ### Mechanical - [ ] All rule interactions verified - [ ] Edge cases resolved - [ ] Victory achievable but not trivial - [ ] No unbreakable stalemates ### Balance - [ ] First player wins 45-55% - [ ] Multiple strategies win regularly - [ ] No dominant opening - [ ] Skill affects outcome ### Experience - [ ] Games complete in target time - [ ] Players want rematch - [ ] Decisions feel meaningful - [ ] Players improve with practice ### Accessibility - [ ] Rules learned in <5 minutes - [ ] Rules fit one page - [ ] No ambiguous situations - [ ] Components distinguishable --- ## Quick Evaluation Filters **30-Second Test:** Can you explain core concept in 30 seconds? **Originality Test:** Does it feel like variant of existing game? **Decision Test:** Are there obviously interesting decisions? **Depth Test:** Could this sustain interest for 50+ plays? --- ## Session Structure (2 Hours) 1. **10 min:** Pick 3-4 brainstorming techniques 2. **60 min:** Generate 15-20 ideas per technique 3. **20 min:** Expand 5-10 promising ideas 4. **20 min:** Combine and explore hybrids 5. **10 min:** Apply filters, select for prototyping --- ## Anti-Patterns ### 1. Complexity as Depth **Pattern:** Adding rules, exceptions, and special cases to make the game feel "deeper." **Why it fails:** Complexity and depth are different. Complex rules create burden; depth emerges from simple rules with rich interactions. Chess has simpler rules than many shallow games. **Fix:** Ruthlessly remove complexity that doesn't add strategic options. If a rule requires explanation but doesn't create interesting decisions, cut it. ### 2. Solved Game Blindness **Pattern:** Creating a game where optimal play always produces the same outcome—often draws or first-player wins. **Why it fails:** Once players discover the solution, the ga
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.