ui-runtime-verify

Refresh Cocos asset-db, run UI validation scripts, and produce runtime-verdict artifacts.

3|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/eaglhuang/cocos_new --skill ui-runtime-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-runtime-verify
Source: https://github.com/eaglhuang/cocos_new/tree/main/.github/skills/ui-runtime-verify
Command: npx skills add https://github.com/eaglhuang/cocos_new --skill ui-runtime-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines final validation of UI assets by refreshing the asset-db, running runtime UI checks, and writing back verdicts, ensuring changes to layout/skin/screen/content are verified in runtime rather than just static checks.

Core Features & Use Cases

  • Refresh Cocos asset-db and run runtime UI validation scripts (validate-ui-specs.js, headless-snapshot-test.js, capture-ui-screens.js)
  • Choose validation path per environment using cocos-screenshot or cocos-preview-qa to compare actual render, and write generated-review/runtime-verdict.
  • Use after modifying UI assets like layout, skin, panel, or content, to ensure visual integrity before merging.

Quick Start

Run the UI Runtime Verify workflow for the target screen, and report back generated-review and runtime-verdict.

Frequently Asked Questions about ui-runtime-verify

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

FAQPage Schema
How do I validate Cocos UI assets at runtime after modifying layout or skin files?

Runtime UI validation for Cocos assets works by refreshing the asset database and executing UI-spec validation scripts alongside headless visual tests. It ensures visual integrity for layout, skin, screen, and panel changes before merging.

What is headless visual regression testing for Cocos UI panels?

Headless visual regression testing for Cocos UI panels captures screenshots via environment-specific workflows like cocos-screenshot or cocos-preview-qa. It compares actual renders against specs to produce generated-review and runtime-verdict artifacts for decision making.

Can I run runtime UI validation scripts without setting up the Cocos asset database?

No, you cannot run runtime UI validation scripts without the Cocos asset database. The validation workflow requires refreshing the asset-db first to accurately identify and verify UI integrity across specified layout, skin, screen, and content targets.

What is the best way to automate UI integrity checks for Cocos screen changes?

The best way to automate UI integrity checks for Cocos screen changes is running headless snapshot tests that select a capture path based on your environment. This generates runtime-verdict artifacts to confirm visual correctness before merging.

Why do my static UI checks pass but Cocos runtime visual tests fail?

Static UI checks may pass but Cocos runtime visual tests fail because runtime validation executes UI-spec scripts and headless snapshots to verify actual rendering behavior. This catches dynamic layout, skin, and panel issues that static analysis cannot detect.