Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问许可证需确认审计通过

boardgame-design桌游设计

Agent Skill

用于辅助界面设计、视觉规范、排版、配色、布局和交互体验优化。它适合让 Agent 根据产品场景整理页面结构、生成 UI 方案、检查视觉一致性或改进组件层级。使用时需要结合现有品牌、设计系统和用户任务,不应只堆装饰元素;涉及真实页面改动时,应通过截图或浏览器预览检查文本溢出、对齐和响应式表现。

总安装

245

周安装

10

GitHub Stars

2

下载量

78
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:boardgame-design(桌游设计)
来源仓库:https://github.com/fil512/upship
仓库路径:skills/boardgame-design
安装命令:
npx skills add https://github.com/fil512/upship --skill boardgame-design
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/fil512/upship --skill boardgame-design

简介

boardgame-design 提供桌游设计的全面指导,侧重德国式 Eurogame 机制和玩家 engagement。

  • 它强调策略主导、无淘汰设计和间接冲突,覆盖资源经济和 playtesting 方法论。
  • 适用于从零设计 playable 原型,并提供规则文档和平衡分析工具。
  • 使用时需明确游戏类型和目标玩家,避免过度随机或主题不一致问题。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Board Game Design Skill

Overview

This skill provides comprehensive guidance for designing engaging board games, with emphasis on German-style Eurogame principles. It covers mechanical design, balance analysis, asymmetric faction design, resource economy systems, playtesting methodology, and rules documentation.

Core Design Philosophy

The Eurogame Approach

German-style Eurogames emphasize:

  1. Strategy Over Luck: Minimize randomness; player decisions should drive outcomes
  2. No Player Elimination: Everyone stays engaged until the end
  3. Indirect Conflict: Competition through position, resources, and efficiency rather than direct attacks
  4. Multiple Paths to Victory: No single dominant strategy
  5. Elegant Mechanics: Maximum strategic depth from minimal rules complexity
  6. Bounded Play Time: Built-in mechanisms to limit game length (fixed turns, resource depletion, scoring thresholds)

What Makes Games Fun

  • Meaningful Decisions: Every choice should have trade-offs and consequences
  • Appropriate Challenge: Difficulty that creates satisfaction without frustration
  • Player Interaction: Opponents' actions should matter to your strategy
  • Emergent Complexity: Simple rules that create rich strategic possibilities
  • Steady Pacing: Interesting events throughout; no "grinding" phases
  • Replayability: Variability and multiple strategies encourage repeated play

Key Design Workflows

1. Mechanical Design

When designing core mechanics:

  • Identify the Core Loop: What is the most repeated action? It must be simple, fun, and have depth
  • Establish Core Constraints: A central limitation that drives all decisions (e.g., Lift ≥ Weight in UP SHIP!)
  • Design Feedback Loops: Actions should create cascading effects and player interaction
  • Create Tension Points: Moments of meaningful scarcity and difficult choices
  • Balance Simplicity and Depth: "Elegance" means rich strategy from few rules

2. Resource Economy Design

Resources are the lifeblood of strategic games:

  • Define Resource Types: Money, actions, time, components, information
  • Create Scarcity: Limited resources force meaningful choices
  • Design Flow: Sources (generation), sinks (consumption), and conversion paths
  • Ebb and Flow: Scarcity that changes over the game creates dynamic tension
  • Control = Power: Whoever controls a scarce resource gains strategic advantage
  • Multiple Currencies: Different resource types that don't directly convert create interesting trade-offs

The Action Economy: The most precious resource is often actions/turns. When designing:

  • Make every action feel valuable
  • Create opportunity cost between competing good options
  • Consider: "I take it, opponent takes it, or it doesn't happen"

3. Asymmetric Faction Design

Asymmetry increases replayability but requires careful balance:

Types of Asymmetry (from subtle to extreme):

  1. Asymmetric Results: Same rules, different outcomes from choices (Monopoly)
  2. Asymmetric Starting Positions: Different initial resources/positions (Catan)
  3. Asymmetric Abilities: Special powers that modify standard rules (Terra Mystica)
  4. Asymmetric Rules: Fundamentally different gameplay for each faction (Root)

Balance Principles:

  • Players should feel powerful, not restricted
  • Each faction needs at least 3 viable strategic paths
  • Trade-offs should be meaningful: strong at X, weaker at Y
  • Theme should justify mechanical differences
  • Consider self-balancing through player interaction (ganging up on leaders)
  • "Dial down" extremes: moderate bonuses are easier to balance

Testing Asymmetry:

  • Asymmetry creates combinatorial explosion of test cases
  • Focus playtesting on faction vs. faction matchups
  • Track win rates by faction over many games
  • Watch for perceived imbalance vs. actual imbalance

4. Balance Analysis

Balance ensures fair competition and strategic viability:

Pre-Playtest Balance:

  • Mathematical modeling of cost-benefit ratios
  • Compare similar options: are costs proportional to power?
  • Check for dominant strategies on paper
  • Model income/resource generation over game length

Balance Levers:

  • Costs (acquisition price, upkeep, opportunity cost)
  • Power (immediate effect, ongoing benefit, win condition contribution)
  • Availability (scarcity, prerequisites, timing)
  • Risk (variance, dependencies, counter-play)

Handling Runaway Leaders:

  • Catch-up mechanisms (bonus for trailing players)
  • Diminishing returns on accumulated advantage
  • Player interaction as natural balancing (targeting the leader)
  • Hidden scoring until game end

5. Playtesting Methodology

Playtesting is iterative, time-consuming, and essential:

Phase 1: Solo Testing

  • Test core loop alone
  • Verify basic mechanics work
  • Identify obvious broken strategies
  • Goal: Does the game function?

Phase 2: Guided Testing

  • Play with interested friends/colleagues
  • Watch for dominant strategies and unexpected behavior
  • Begin mechanical balancing
  • Goal: Is the game playable and interesting?

Phase 3: Blind Testing

  • External playtesters with no guidance
  • Observe without intervening
  • Test rulebook clarity
  • Goal: Can people learn and enjoy it independently?

Best Practices:

  • Observe behavior, don't just ask opinions (actions reveal more than words)
  • Track specific metrics: game length, decision time, win rates
  • Change one variable at a time when iterating
  • Distinguish "perceived balance" from actual balance
  • Feedback loop: implement → test → analyze → repeat

6. Rules Documentation

Clear rules prevent confusion and arguments:

  • Organize by Phase/Turn Structure: Players should find rules in play order
  • Define Terms Early: Establish vocabulary before using it
  • Handle Edge Cases: Anticipate conflicts and provide resolution
  • Include Examples: Concrete illustrations of abstract rules
  • Create Quick Reference: Summary card for experienced players
  • Cross-Reference: Link related sections for easy navigation
  • Playtest the Rulebook: Rules are a product that needs testing too

Supporting Resources

This skill includes reference files in references/:

  • eurogame-principles.md - Deep dive on German-style design philosophy
  • balance-methodology.md - Systematic approaches to game balance
  • design-checklist.md - Validation checklist for complete game designs

When This Skill Activates

Claude uses this skill when you:

  • Request help designing a new game or game system
  • Ask for balance analysis of existing mechanics
  • Want to design or validate asymmetric factions
  • Need help with resource economy design
  • Ask for rules clarity review
  • Request playtesting methodology guidance
  • Ask about making a game "more fun" or "more engaging"

Example Workflows

Example: Designing a New Resource System

When asked "How should I design an engineer economy?":

  1. Define the resource's role (what does it enable?)
  2. Identify sources (how are engineers acquired?) and costs
  3. Identify sinks (how are engineers consumed/spent?)
  4. Create scarcity tension (never enough for everything)
  5. Add trade-offs (using engineers for X means not using them for Y)
  6. Model mathematically (income vs. consumption over game length)
  7. Design focused playtest to validate

Example: Balancing Asymmetric Factions

When asked "Is faction X balanced?":

  1. List faction's unique abilities and constraints
  2. Compare power level to other factions' abilities
  3. Identify intended trade-offs (what's the cost of the benefit?)
  4. Check for unintended synergies or exploits
  5. Review win rate data if available
  6. Suggest adjustments if needed (dial up/down specific abilities)
  7. Design faction-focused playtest scenarios

Example: Making a Mechanic More Engaging

When asked "This part of the game feels boring":

  1. Identify the specific mechanic/phase in question
  2. Analyze: Is there meaningful choice? Tension? Consequence?
  3. Check pacing: Too slow? Too predictable?
  4. Look for "grinding" (repetitive actions without interesting decisions)
  5. Consider adding: scarcity, trade-offs, player interaction, or stakes
  6. Propose targeted changes that preserve overall design
  7. Plan A/B playtest comparing old vs. new version

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

37.59%
按下载量换算29

Claude

26.98%
按下载量换算21

Cursor

17.56%
按下载量换算14

Gemini CLI

8.63%
按下载量换算7

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills