Loading...
Loading...
Found 26 Skills
Generate a QA test plan for a sprint or feature. Reads GDDs and story files, classifies stories by test type (Logic/Integration/Visual/UI), and produces a structured test plan covering automated tests required, manual test cases, smoke test scope, and playtest sign-off requirements. Run before sprint begins or when starting a major feature.
Complete QA, playtesting, and code quality team for game development. Use when evaluating player experience, fun factor, game feel, code quality, test coverage, refactoring, performance testing, or build validation. Covers playtesting methodologies, UX research, unit/integration/e2e testing, code review, linting, accessibility, and continuous quality assurance. Triggers on requests for testing, QA, playtesting, code review, refactoring, bug tracking, or quality validation.
Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.
The foundational theory of interactive experience design - loops, motivation, feel, and the art of meaningful playUse when "game design, core loop, game feel, player motivation, game mechanics, meaningful choice, progression system, game economy, game balance, playtesting, GDD, game document, fun factor, engagement, flow state, risk reward, player agency, juice, game polish, 8 kinds of fun, bartle types, MDA framework, game-design, player-experience, core-loop, motivation, game-feel, MDA, playtesting, GDD, systems-thinking, player-psychology, engagement, flow-state" mentioned.
Official Roblox Studio MCP server tools reference. What each tool does, how to use it, reliability patterns, and workflows for script editing, building, playtesting, and debugging. Use when the AI has an MCP connection to Roblox Studio.
Use this skill when working with game balancing - economy design, difficulty curves, progression systems, reward schedules, playtesting analysis, or tuning game parameters. Triggers on any game design task involving resource sinks and faucets, XP curves, loot tables, difficulty scaling, player retention mechanics, or interpreting playtest data to adjust game feel.
Plan, run, and interpret game playtests. Use when validating prototypes, onboarding, difficulty, mechanics, UI clarity, retention, or fun; when writing playtest scripts, surveys, observation plans, or telemetry requirements.
Designing tabletop games - from core mechanics to manufacturing, from prototyping to KickstarterUse when "board game, tabletop, card game, worker placement, deck building, area control, playtesting, rulebook, kickstarter game, game balance, asymmetric factions, euro game, ameritrash, party game, dice game, prototype, game publisher, crowdfunding game, board-games, tabletop, game-design, mechanics, playtesting, kickstarter, manufacturing, rulebook, components, balance, player-interaction" mentioned.
Turn raw playtest observation into actionable design, UX, tuning, and production decisions.
Triage mixed game demo and playtest feedback into a prioritized fix brief, weighted evidence summary, and next artifact recommendation. Use when a team has playtest notes, Steam Playtest responses, creator or streamer demo reactions, survey comments, wishlist/context signals, bug lists, or performance findings and needs to decide what to fix first before the next build, festival, or launch beat, even if they only say "sort our playtest feedback", "what should we fix before Next Fest", "players are confused", "streamers bounced off the demo", or "turn these demo notes into priorities".
Invoke when the user wants to plan, execute, or analyze a structured playtest session with behavioral observation. Covers protocol design, observer guides, and data synthesis. Triggers on: "playtest", "player feedback", "usability test", "observation session", "playtest analysis". Do NOT invoke for QA bug testing (use game-qa-lead) or balance tuning (use game-balance-check). Part of the AlterLab GameForge collection.
Drive Roblox Studio from an AI agent via the built-in Studio MCP server - connecting Claude Code, Codex, Cursor, OpenCode, Gemini CLI; tools to explore the DataModel, read/edit scripts, run Luau in edit/server/client, playtest, read output, capture screenshots, simulate input, insert assets. Use when an agent should inspect, modify, or playtest an open Studio place, or to set up the connection.