Results for “board-game”

Turns a one-sentence game concept into a complete, playable design with rules, components, and variations, and also designs gamification systems for real-world goals.

Balance game systems including difficulty curves, stat tuning, economy rates, matchmaking fairness, and player power progression. Use when tuning numbers and systems for fair, engaging gameplay. Also trigger for "game balance", "difficulty tuning", "stat balancing", "nerf", "buff", "power curve", or "difficulty curve".

Design game user interfaces and user experience flows including HUD, menus, inventory screens, accessibility, and player feedback systems. Use when designing how the player interacts with game systems visually. Also trigger for "game UI", "game UX", "HUD design", "menu design", "inventory UI", "game accessibility", or "game interface".

Implements gamification elements in educational content with points, badges, leaderboards, and quests

Generate, continue, revise, polish, and stress-test game theory research papers. Use when the user provides a game theory topic, phenomenon, draft, outline, model idea, literature anchor, reviewer comments, or asks for 博弈论论文生成, 选题建模, 文献迁移, 模型修正, 均衡分析, 数值模拟, 论文润色, 改稿打磨, or R&R response work.

Play Yoink, an onchain capture-the-flag game on Base. Yoink the flag from the current holder, check game stats and leaderboards, view player scores, and compete for the trophy. Uses Bankr for transaction execution.

Play an onchain capture-the-flag game on Base by yoinking the flag from the current holder, checking game stats and leaderboards, and competing for the trophy using Bankr for transaction execution.

Create game plans with strategy and tactics. TRIGGERS - Use when user needs help with game-plan related tasks.

Plan a chunk of work too big for one agent session by putting it on a shared whiteboard — a map of investigation tickets on GitHub Issues — working them until nothing is left to decide, then snapshotting the board into a handoff artifact. Tickets needing nobody are worked back-to-back; the session stops when the human is the blocker. Use only when the user explicitly invokes whiteboard or asks to draw, work, run, or snapshot a whiteboard/map — not for ordinary planning requests.

当需要将个人目标或生活挑战转化为结构化、可执行的游戏化系统时

Game design principles. GDD structure, balancing, player psychology, progression.

Plan and execute game QA including functional testing, playtesting, performance testing, compatibility testing, and bug tracking workflows. Use when setting up quality assurance for a game project. Also trigger for "game QA", "playtest", "bug tracking", "game testing", "QA plan", "regression testing", or "compatibility testing".

当需要主动设计和构建个人职业生涯，而非被动接受传统就业时

当需要将生活或工作中的复杂情境转化为可管理、可执行的系统时，或当感到迷茫、缺乏动力、陷入社会比较时，调用此模型来重新构建认知和行动框架

Re-onboard a churned customer with the same care they got the first time. Reads why they left and whether they left the door open, picks the ones worth winning back, and builds a warm re-onboarding sequence, not a "we miss you" discount blast. Built for any post-sale or growth team, customizable to your product and win-back window. Trigger on "win back churned customers", "re-engage a lost account", "build a win-back sequence", "which churned customers should we chase", "boomerang play", "re-onboard a customer who left", or any win-back question.

Brainstorm and develop game concepts, exploring genres, themes, target audiences, and unique selling points. Use when starting a new game project from scratch or pivoting an existing idea. Also trigger for "game idea", "what kind of game", "I want to make a game", "game pitch", or "explore game concepts".

World-class level design expertise - spatial storytelling, player flow, blockout methodology, and the invisible hand that guides players without them knowingUse when "level design, blockout, graybox, whitebox, player flow, level layout, combat arena, exploration space, map design, multiplayer map, pacing, weenie, landmark, gating, metroidvania, open world design, linear level, environmental storytelling, teaching through design, playtesting, heatmap, metrics, sightlines, level-design, game-development, spatial-design, blockout, graybox, player-flow, pacing, environmental-storytelling, combat-design, multiplayer-maps, open-world, linear-design, metroidvania" mentioned.

Sets up and audits the Claude Code harness for a project: CLAUDE.md, .claude/rules, skills, subagents, settings.json permissions, hooks, verification loop. Commands: kickoff (scaffold new setup), check-playbook (score an existing one), scouting-report (last scorecard), adjust (fix bloat/misplaced instructions), drill (turn advisory prose into real hooks/permissions/CI), decline (record an accepted risk), gameplan (work order with acceptance criteria before building), watch-film (check a diff against that order for scope creep/weakened tests/false claims). Use for setting up Claude Code, or on: "Claude ignores my CLAUDE.md", "it's huge and still misses things", "it said done but ran nothing", "it changed files I didn't ask about", "it weakened a test to pass", "rule, skill, or hook?", "is my setup any good". Not for code quality (code-audit), test coverage (test-assessment), one-off prompt wording (genie-proof-prompts), new skill authoring (skill-creator), or compacting a conversation (handoff).

Design, implement, budget, and verify readable real-time game visual effects: particles, smoke/fog, lightning, fire, trails, impacts, bloom/glow, and layered spell timelines. Use when a user needs a VFX spec, lifecycle, engine handoff, particle pooling, effect composition, reduce-motion fallback, or frame-budget diagnosis. Triggers on: game VFX, spell effects, particle system, impact burst, procedural lightning, smoke, bloom, magic aura, or VFX performance.

Design in-game economies including currencies, progression systems, loot tables, monetization, and resource flow. Use when building the economic backbone of a game. Also trigger for "game economy", "loot table", "drop rates", "currency system", "progression design", "monetization strategy", or "reward system".

Guides visual style selection, asset pipeline choices, and animation workflows for game development.

2D game development principles. Sprites, tilemaps, physics, camera.

Plan and execute rapid game prototypes to validate mechanics, test assumptions, and find the fun before committing to full production. Use when building playable proofs-of-concept. Also trigger for "prototype", "game jam", "proof of concept", "find the fun", "playable demo", or "rapid prototype".

Design badge and achievement systems for learning. TRIGGERS - Use when user needs help with badge-system related tasks.

Agent validation overhaul: reward weight overrides, fitness decline gate, pinned data, staged experiments

Analyzes game AI systems in a codebase, covering behavior trees, finite state machines, GOAP, utility AI, pathfinding, steering, perception, difficulty adaptation, NPC dialogue, and AI debugging tools for Unity, Unreal, and Godot projects.

Read, write, and browse the AgentHub message board for agent coordination. Use when the user runs /hub:board or asks to post, read, or inspect coordination messages between competing AgentHub agents.

Index and router for a C-level advisory bundle of 33 skills covering 14 C-suite roles, orchestration, cross-cutting capabilities, and culture. Use to explore the bundle, decide which advisor skill fits a question, or find entry points like the onboard interview, chief-of-staff routing, and board-meeting protocol.

Read, write, and browse the AgentHub message board for agent coordination. Use when the user runs /hub:board or asks to post, read, or inspect coordination messages between competing AgentHub agents.

Route web-game auto-playtesting with WAI Play (waiterve/wai-play): decide whether the next move is a testability check, authoring or repairing the `GameFlowAgentAPI` bridge, running a real browser playtest, reading the five-dimension quality report, or unblocking a key node the agent cannot reach. Use when the user wants an AI agent to actually play their HTML5 / canvas / vibe-coded web game and return reproducible evidence, scores, and fix suggestions across the five supported types (survivor-like, arcade shooter, platformer, puzzle/card, visual novel). Triggers on: wai-play, WAI Play, auto-playtest, AI plays my game, web game testing agent, GameFlowAgentAPI, GameFlowIntegration, jumpToScenario, game quality score, playtest evidence. Route Unity/Unreal frame-time work to `game-performance-profiler`, engine build failures to `game-build-log-triage`, human playtest notes to `game-demo-feedback-triage`, and generic browser automation to `browser-harness`.

Renders a story, question, or meme as a realistic Reddit post card with vote rail, comments, and awards, suitable for video overlays or social media sharing.

Turn an at-risk account into a churn-save play. It diagnoses the real reason behind the risk (not the stated one), lays out the commercial and non-commercial levers you can pull, and builds a multi-touch save sequence with owners and dates. Built for B2B customer success teams, customizable to your CRM and product analytics. Trigger on "this account is going to churn", "build a save play", "why are they leaving", "at-risk renewal", "how do I keep this account", or any retention rescue.

Design multiplayer systems including networking architecture, matchmaking, social features, anti-cheat, and multiplayer game modes. Use when adding online or local multiplayer to a game. Also trigger for "multiplayer", "online play", "co-op design", "PvP design", "matchmaking", "netcode", or "multiplayer architecture".

Game art principles. Visual style selection, asset pipeline, animation workflow.

Building interactive experiences that engage, challenge, and delight playersUse when "game, gamedev, game development, phaser, unity, unreal, godot, gameplay, game loop, sprites, collision, physics, player, level, tilemap, games, gamedev, interactive, gameplay, physics, engines, performance, player-experience" mentioned.