More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Casual Game Design & QA Architect

    1

    Analyze casual game prototypes, identify gameplay and UI/UX issues, diagnose logic risks, and create actionable QA, bug-fixing, and regression-testing plans for polished, reliable game experiences.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Casual Game Design & QA Architect

    Casual Game Design & QA Architect

    Example session with this skill installed

    Analyze this matching game concept: players drag colored gems into slots. I have the source code. Check the drag-and-drop logic for state bugs and suggest a QA plan.

    • Read your context and instructions
    • Compiled the casual game design

    I have reviewed the provided source code for the "Gem Matcher" concept. The analysis focused on the GemManager.js and InputHandler.js files to identify potential state integrity issues during high-frequency interactions.

    Gameplay Logic and State Audit

    IDComponentEvidence ClassFindingImpact
    LOG-01Drag HandlerSource-supportedonDragStart does not lock the gem state; multiple gems can be flagged as 'active' simultaneously.High: Duplicate scoring and overlapping sprites.
    LOG-02Slot ValidationObservedcheckMatch() triggers before the drop animation completes.Medium: Visual desync where gems disappear before landing.
    LOG-03State ResetSource-supportedresetLevel() clears the grid array but fails to stop active tweens.Critical: Memory leaks and ghost interactions on retry.

    Proposed QA Matrix

    Test IDScenarioExpected ResultPriority
    QA-DRG-01Rapid multi-touch dragOnly the first registered gem moves; others remain static.High
    QA-DRG-02Interrupted drop (back button)Gem returns to original slot; isDragging flag set to false.Medium
    QA-SCR-01Match on last moveWin screen triggers only after final animation and score tally.High

    Next steps

    1. Implement a globalInputLock boolean in InputHandler.js to prevent simultaneous drags.
    2. Refactor checkMatch() to use a callback or Promise that resolves only after the TWEEN_COMPLETE event.
    3. Add a tweenManager.killAll() call to the resetLevel sequence.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Turn Casual Game Prototypes into Polished, Testable Game Experiences

    Casual Game Design & QA Architect is a structured expert workflow for analyzing casual games, identifying design and technical risks, improving player experience, and creating actionable quality-assurance plans.

    Instead of providing generic feedback, this Skill follows a repeatable process to examine the game’s core loop, player objectives, progression, interactions, UI/UX, visual consistency, game logic, state management, feedback systems, and overall playability.

    What This Skill Does

    1. Game Design Analysis

    • Evaluate the core gameplay loop, objectives, mechanics, progression, rewards, and replayability.
    • Identify confusing interactions, repetitive gameplay, weak feedback, and progression problems.
    • Assess whether the experience suits its intended audience and platform.

    2. UI/UX and Interaction Review

    • Analyze navigation, screen hierarchy, readability, touch targets, instructions, and interaction feedback.
    • Identify inconsistent layouts, unclear controls, frustrating flows, and accessibility concerns.
    • Recommend specific improvements to make the experience more intuitive and polished.

    3. Gameplay Logic and Bug-Risk Analysis

    • Examine game states, scoring, conditions, progression, rewards, resets, and persistence.
    • Identify potential logic errors, edge cases, contradictory states, and incomplete interactions.
    • Review supplied source code or project materials when available.

    4. Structured QA and Regression Testing

    • Create test cases covering normal gameplay, edge cases, invalid actions, state transitions, and recovery scenarios.
    • Build prioritized issue registers with reproduction steps, expected behavior, actual behavior when observed, severity, and recommended fixes.
    • Develop regression checklists to verify that changes do not break previously working features.

    5. Evidence-Based Recommendations

    • Separate confirmed defects from suspected risks and design opportunities.
    • Link findings to supplied screenshots, recordings, code, test results, or other available evidence.
    • Prioritize recommendations by player impact, functional risk, and implementation importance.

    Standard Workflow

    DISCOVER → SCOPE → ANALYZE → IDENTIFY RISKS → DESIGN TESTS → PRIORITIZE ISSUES → RECOMMEND FIXES → REGRESSION PLAN → FINAL QA REPORT

    Each stage builds on the previous one. When information is missing, the Skill identifies assumptions and requests essential details rather than presenting guesses as verified findings.

    Supported Use Cases

    • Reviewing casual and hypercasual game prototypes.
    • Auditing browser-based HTML, CSS, and JavaScript games.
    • Evaluating puzzle, matching, educational, and casual mobile-game experiences.
    • Analyzing children's games for clarity, usability, age-appropriate interactions, and functional reliability.
    • Reviewing screenshots, screen recordings, design documents, gameplay descriptions, and accessible source code.
    • Preparing actionable bug reports, test matrices, design recommendations, and release-readiness checklists.

    Expected Deliverables

    Depending on the available materials and requested scope, the Skill can produce a structured game audit, prioritized issue register, gameplay and UI/UX recommendations, QA test matrix, regression checklist, risk assessment, or final review report.

    Quality and Safety Standards

    The Skill distinguishes evidence from inference, avoids claiming that unperformed tests have passed, and identifies limitations caused by missing files, unavailable tools, or inaccessible runtime environments. It does not assume permission to modify files, execute code, access external services, or perform destructive operations. Such actions require appropriate authorization and available tools.

    Runtime testing and browser playthroughs are performed only when the environment supports them and the user has authorized the relevant scope. Recommendations are designed to be specific, actionable, and verifiable.

    Intended Audience

    Indie game developers, game designers, product designers, prototype builders, QA testers, small studios, and AI-assisted development teams seeking a more systematic approach to casual-game analysis and quality assurance.

    The goal: Transform informal game feedback into a repeatable, evidence-led workflow for building clearer, more reliable, and more polished casual gaming experiences.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.

    Cannot prove runtime performance through static analysis. Requires explicit authorization for file edits. Does not handle legal compliance audits.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    Permissions

    No special permissions declared or detected

    Listed1 month ago

    What's inside

    Frequently Asked Questions

    The skill identifies critical issues like 'broken' core loops where player progression stalls, state synchronization bugs between the UI and backend, and UX friction points that cause player drop-off in casual titles.

    You receive the full Casual Game Design QA workflow, including specialized modules for core loop modeling, state integrity testing, and a standardized reporting template for actionable bug remediation.

    Yes, the skill is framework-agnostic and performs effectively with mobile-first stacks like Unity and React Native, as well as web-based engines like Phaser or vanilla JavaScript.

    Unlike general prompts, this skill uses a systematic evidence-led framework that cross-references observed game state against intended logic, preventing the 'hallucinations' or overlooked edge cases common in standard AI chats.

    Simply provide the skill with your game's source code, logic flowcharts, or screen recordings of gameplay; it will then automatically inventory these assets to define the testable scope.

    New in Agents & Orchestration