ui-asset-qc

Automate UI asset quality checks for skins and screen packages.

3|Updated Mar 6, 2026

Search Tags:#automation #validation #qa #quality #atlas #proof-draft #ui-asset

Ready to run

npx skills add https://github.com/eaglhuang/cocos_new --skill ui-asset-qc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ui-asset-qc
Source: https://github.com/eaglhuang/cocos_new/tree/main/.github/skills/ui-asset-qc
Command: npx skills add https://github.com/eaglhuang/cocos_new --skill ui-asset-qc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates UI asset quality verification to ensure skins, screen packages, and related resources pass QA before entering the UI preview stage.

Core Features & Use Cases

Enforces 9-slice border validity, atlas consistency, and texture resolution rules.
Ensures skin-slot completeness and proper proof-draft coverage for screen packages.
Generates a review artifact and supports strict or warn-only validation modes prior to preview.

Quick Start

Run visual asset checks and UI spec validation for a given screen or family, then review the generated report before proceeding to preview.

Frequently Asked Questions about ui-asset-qc

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate UI asset quality validation before preview?▼

To automate UI asset quality validation, run checks on skins, screen packages, and proof drafts to enforce 9-slice borders, atlas consistency, and texture resolution rules. This generates a reviewed artifact report at artifacts/ui-source/{screenId}/review/generated-review.json before entering the preview stage.

What checks are needed for atlas consistency and 9-slice borders in screen packages?▼

Atlas consistency and 9-slice border validation require deterministic checks on your screen packages. The process verifies atlas uniformity, enforces 9-slice border validity, checks texture resolution, and ensures skin-slot completeness to pass QA before generating a consolidated review skeleton.

Can I validate proof-draft coverage and skin-slot completeness without blocking the pipeline?▼

Yes, you can validate proof-draft coverage and skin-slot completeness using warn-only validation modes. This configuration checks UI assets and generates review artifacts without strictly blocking your pipeline, allowing you to proceed to preview while logging coverage warnings.

What is the best way to enforce strict QA rules for texture resolution and skin families?▼

The best way to enforce strict QA rules for texture resolution and skin families is to apply strict validation mode during UI asset verification. This deterministically checks resolution rules and skin-slot completeness, failing the build if assets do not pass QA before preview.

Where does the automated UI asset review report get saved?▼

The automated UI asset review report is saved as a consolidated review skeleton at artifacts/ui-source/{screenId}/review/generated-review.json, with a raw version located at generated-review.raw.json, providing a structured output for QA verification before preview.