القائمة
Use when working on creating custom components, implementing component communication patterns, or refactoring existing component architecture.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use this skill when the user asks to release the iOS app, upload a build, submit to App Store Connect review, or "在 App Store 上架/提交审核" for WordMagicGame.
Seed a lesson-import draft on a deployed Happyword API (Preview or prod) and optionally run the extract-pending cron so it reaches `pending` (待复核). Uses tools starting with `hw_`. Invoke when the user wants to upload a textbook photo for review against a specific Vercel URL, mirror E2E `test_lesson_import_cron_e2e`, or smoke-test lesson import + cron on a branch deployment.
Investigate why a Vercel preview / production deployment of the FastAPI server is broken (404 on every path, 500 on every path, e2e CI red, etc.). Pulls the right log surface for the symptom and maps HTTP error headers to root causes. Use whenever the deployed server returns wrong responses, the server-ci e2e job fails, or autofix loops keep retrying without converging.
Health-check every active Vercel Preview deployment listed in the live manifest at `https://happyword.cool/api/v1/public/preview-urls.json`. Probes `GET /api/v1/public/health` through Vercel Deployment Protection (`x-vercel-protection-bypass` header), prints a one-line status per preview, and exits non-zero if any are sick. Use when the user asks to "test preview health", "check previews", "are PR previews alive?", before merging anything that touches `server/`, after a fleet-wide redeploy or env-var rotation, or after rotating `VERCEL_AUTOMATION_BYPASS_SECRET` — do NOT loop ad-hoc `curl` calls or use `tools/vercel/smoke-prod.sh` (production-only) for this.
Drives a per-feature visual + spec-anchored gap scout across HarmonyOS / iOS / Android using tools/parity_scout/. Use when asked to "find iOS / Android gaps vs HarmonyOS main", "check parity for <feature>", or "screenshot the three platforms and tell me what's different".
Drives a per-feature visual + spec-anchored gap scout across HarmonyOS / iOS / Android using tools/parity_scout/. Use when asked to "find iOS / Android gaps vs HarmonyOS main", "check parity for <feature>", or "screenshot the three platforms and tell me what's different".
| name | cocos-component-architect |
| description | Use when working on creating custom components, implementing component communication patterns, or refactoring existing component architecture. |
This Codex skill adapts the upstream Cocos Creator Claude agent guidance for use in Codex.
Expert in designing and implementing Cocos Creator components following best practices. Use this skill for creating custom components, implementing component communication patterns, or refactoring existing component architecture.
Context: Need for new gameplay component
User: "Create a health system component"
Assistant: "I will use $cocos-component-architect"
Commentary: Creates reusable, well-structured component with proper lifecycle
Context: Multiple components need to interact
User: "Implement event system between player and enemies"
Assistant: "I will use $cocos-component-architect"
Commentary: Designs efficient message passing system
Context: Legacy component code
User: "Refactor the movement system to be more modular"
Assistant: "I will use $cocos-component-architect"
Commentary: Breaks down monolithic components into smaller, focused ones
Trigger: Scene context needed Handoff: "Component designed. Need scene integration analysis for: [components]"
Trigger: Advanced TypeScript patterns Handoff: "Component structure ready. Need TypeScript optimization for: [features]"
Trigger: Component performance concerns Handoff: "Components implemented. Performance tuning needed for: [systems]"