skills.rest
dyCuong03
dyCuong03COMMUNITY
Explore all skills by this author →
GitHub

cocos-playable-qa

Audit Cocos Creator 3.8.x playable builds for bugs, performance, and ad policy compliance.

Updated Apr 3, 2026
Search Tags:#performance profiling#qa testing#cocos creator#bug filing#ad compliance#release sign-off#playable validation
One-click install
npx skills add https://github.com/dyCuong03/cocos-agent-team --skill cocos-playable-qa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cocos-playable-qa
Source: https://github.com/dyCuong03/cocos-agent-team/tree/main/skills/qa-tester
Command: npx skills add https://github.com/dyCuong03/cocos-agent-team --skill cocos-playable-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Cocos Creator playables often have hidden bugs, performance regressions, and ad platform policy violations that only surface during real-world testing, leading to rejected ad builds, poor user experience, or missed release milestones. This skill eliminates the risk of shipping broken or non-compliant playables by providing a structured, repeatable QA workflow.

Core Features & Use Cases

  • End-to-end QA passes: Covers structural scene integrity, behavioral interaction contracts, performance metrics, and ad platform policy compliance for Cocos Creator 3.8.x playables.
  • Regression testing: Compares current build performance and behavior against prior baselines stored in agentmemory to catch drift after code or scene changes.
  • Structured bug filing: Automatically assigns reproducible bugs to the correct role (design, engineering, TypeScript development) with clear severity levels and steps to reproduce.
  • Use case: After your team finishes a new playable milestone, run a full QA pass to verify FPS meets targets, CTAs fire correctly, bundle size is within ad platform limits, and all scenes match the design wireframe before requesting release sign-off.

Quick Start

Use the cocos-playable-qa skill to run a full quality assurance pass on your latest Cocos Creator 3.8.x playable build and generate a release sign-off report.

Frequently Asked Questions about cocos-playable-qa

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

FAQPage Schema
How do I run QA testing on Cocos Creator playable builds to prevent ad policy violations?▼

QA testing for Cocos Creator playables involves validating structural scene integrity, behavioral interaction contracts, and ad platform policy compliance to catch violations before release. This workflow checks bundle size limits and ensures CTAs fire correctly to prevent ad rejections.

What is performance profiling for Cocos Creator 3.8.x playables and when is it needed?▼

Performance profiling for Cocos Creator playables validates FPS metrics against defined budgets and compares current build performance against prior baselines. It is needed during post-build validation, regression testing after scene changes, and release milestone sign-off.

How do I file structured bug reports for Cocos Creator playable validation issues?▼

Filing structured bug reports for playable validation assigns reproducible issues to the correct role like design, engineering, or TypeScript development. Reports include clear severity levels and detailed steps to reproduce to streamline the resolution workflow.

Does this playable validation workflow support regression testing after scene modifications?▼

Playable validation supports regression testing by comparing current build behavior and performance against prior baselines stored in memory. This catches drift after code or scene changes to ensure new modifications do not introduce hidden regressions.

What's the best way to ensure release sign-off for ad-supported Cocos playables?▼

The best way to ensure release sign-off is running a full QA pass that verifies FPS targets, CTA functionality, bundle size limits, and scene wireframe matching. This structured validation generates a comprehensive report confirming all ad platform requirements are met.

Why do ad platform policy violations occur in Cocos Creator playable builds?▼

Ad platform policy violations occur in Cocos Creator playables when structural scene integrity or behavioral interaction contracts fail real-world testing. Hidden bugs and performance regressions surface during validation, causing poor user experience or rejected ad builds.

Related Skills

Explore More Software Engineering Skills→
dyCuong03dyCuong03

cocos-playable-engineer

Automate Cocos Creator 3.8.x playable scene, prefab, and asset hierarchy construction.

Community
Advanced
cenconq25cenconq25
39

team-qa

Coordinate end-to-end QA workflows for sprint or feature sign-off.

Community
Advanced
dyCuong03dyCuong03

theone-cocos-standards

Enforce Cocos Creator 3.x TypeScript standards for playable ads code quality and performance.

Community
Advanced
distribucionesfayosmoreno-sysdistribucionesfayosmoreno-sys

ui-visual-validator

Validate UI modifications for visual regression, compliance, and accessibility.

Community
Advanced