- Home
- Skills
- Agents & Orchestration
- Casual Game Design & QA Architect
More screenshots
Works with the AI tools you already use
Casual Game Design & QA Architect
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
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
- Generated the UI component
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
| ID | Component | Evidence Class | Finding | Impact |
|---|---|---|---|---|
| LOG-01 | Drag Handler | Source-supported | onDragStart does not lock the gem state; multiple gems can be flagged as 'active' simultaneously. | High: Duplicate scoring and overlapping sprites. |
| LOG-02 | Slot Validation | Observed | checkMatch() triggers before the drop animation completes. | Medium: Visual desync where gems disappear before landing. |
| LOG-03 | State Reset | Source-supported | resetLevel() clears the grid array but fails to stop active tweens. | Critical: Memory leaks and ghost interactions on retry. |
Proposed QA Matrix
| Test ID | Scenario | Expected Result | Priority |
|---|---|---|---|
| QA-DRG-01 | Rapid multi-touch drag | Only the first registered gem moves; others remain static. | High |
| QA-DRG-02 | Interrupted drop (back button) | Gem returns to original slot; isDragging flag set to false. | Medium |
| QA-SCR-01 | Match on last move | Win screen triggers only after final animation and score tally. | High |
Next steps
- Implement a
globalInputLockboolean inInputHandler.jsto prevent simultaneous drags. - Refactor
checkMatch()to use a callback or Promise that resolves only after theTWEEN_COMPLETEevent. - Add a
tweenManager.killAll()call to theresetLevelsequence.
casual-game-design-qa-architect.tsx
TSX · React component
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
What you get
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.
How to install
Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.
- 1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
- 2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
- 3
Ask your agent to use it
Restart the agent if it was already running. It picks the skill up automatically - no config needed.
Skills folder by agent
Click the path to copy it. Create the folder if it does not exist yet.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
30-day refund
Not a fit? Get your money back
Trust & safety
Security scanned
Verified clean 1 day ago
- Passed all security checks, Safe to install