Overview

What Is This

The "Overview" skill (ux-review) on the Happycapy Skills platform is a specialized quality assurance tool designed to validate UX design documentation. It serves as a crucial checkpoint between UX Design and the subsequent Visual Design or Implementation phases, ensuring that all user experience specifications, HUD (Heads-Up Display) designs, and interaction pattern libraries are complete, accessible, consistent with the Game Design Document (GDD), and ready for development. The skill analyzes documents for gaps in completeness, accessibility compliance, alignment with the GDD, and readiness for handoff, providing a verdict of APPROVED, NEEDS REVISION, or MAJOR REVISION NEEDED. This step is essential in preventing design deficiencies from propagating downstream, where changes become costlier and more disruptive.

Why Use It

Using the "Overview" skill provides several benefits in a modern game or software development workflow:

• Quality Assurance: The skill acts as an automated gatekeeper, preventing incomplete or non-compliant UX specs from advancing to production. This reduces the likelihood of costly reworks or implementation errors later.
• Consistency and Compliance: By validating against accessibility standards and GDD requirements, the skill ensures every design artifact meets organizational and legal standards.
• Efficiency: Automated checks speed up the review process, freeing up human designers and reviewers to focus on high-level challenges instead of repetitive validation tasks.
• Clarity of Feedback: The skill provides detailed verdicts and highlights specific deficiencies, making it clear what must be addressed before progression.
• Risk Reduction: Early detection of major issues in scope, user needs, or documentation completeness decreases project risk and supports smooth transitions between pipeline stages.

How to Use It

The "Overview" skill is user-invocable and accepts specific arguments to target the scope of the review. The argument syntax allows fine-grained or broad validation, depending on the project's needs.

Supported Arguments:

• A specific file path (e.g., /ux-review design/ux/inventory.md): Validates only the specified document.
• all: Finds and validates all files in the design/ux/ directory.
• hud: Validates only the design/ux/hud.md file, typically used for reviewing HUD designs.
• patterns: Validates only the design/ux/interaction-patterns.md file, focusing on interaction pattern libraries.

Example Usage:

## Validate a specific UX spec
/ux-review design/ux/inventory.md

## Validate all UX specs in the directory
/ux-review all

## Validate just the HUD spec
/ux-review hud

## Validate only interaction patterns
/ux-review patterns

When invoked, the skill uses its allowed tools (Read, Glob, Grep) to parse and analyze the targeted document(s). It checks for:

• Completeness: Are all required sections present? Are all user flows, wireframes, and behaviors documented?
• Accessibility Compliance: Are best practices for accessibility followed (such as color contrast, keyboard navigation, and screen reader support)?
• GDD Alignment: Does the spec align with the agreed-upon Game Design Document in terms of feature set, terminology, and player needs?
• Implementation Readiness: Is the spec sufficiently detailed for handoff to UI programmers or artists, or does it require further elaboration?

After analysis, the skill outputs one of three verdicts:

• APPROVED: The document is complete, consistent, and ready for handoff.
• NEEDS REVISION: Specific issues must be addressed before handoff, but no full redesign is necessary.
• MAJOR REVISION NEEDED: Fundamental problems with scope, user needs, or completeness that require significant rework.

Sample Output:

verdict: NEEDS REVISION
gaps:
  - Missing accessibility notes for HUD color usage
  - Player inventory flow not aligned with GDD v2.3
  - Incomplete wireframes for mobile layout

When to Use It

The "Overview" skill should be run at several critical points in the UX pipeline to maximize its effectiveness:

• After Completing a UX Spec: Run the skill after finishing a new UX design document using the /ux-design process.
• Before Handoff: Use the skill prior to handing off assets to UI programmers or art directors, ensuring all required information is present.
• Pre-Production to Production Gate: Before transitioning from pre-production to production, especially when a gate check requires that all key screens have reviewed and approved UX specs.
• Post-Major Revisions: After any significant changes to UX documentation, rerun the skill to confirm that the revisions meet standards and do not introduce new issues.

Important Notes

• The skill expects UX documentation to reside in the design/ux/ directory, with standard filenames such as hud.md and interaction-patterns.md. Custom or misnamed files may be missed by broad arguments like all, hud, or patterns.
• The skill does not perform a full design or usability review; it focuses on document structure, completeness, standards compliance, and alignment with upstream requirements.
• Verdicts are based solely on document content, not on in-game implementation or design tool prototypes.
• For best results, run the skill iteratively as documents evolve, not just at handoff.
• Address all gaps or required revisions before moving documents into production to avoid rework and implementation delays.

By integrating the "Overview" skill into your pipeline, you establish a robust, automated quality gate that ensures UX specifications are always implementation-ready, accessible, and aligned with project goals.