원클릭으로
cocos-2d-gameplay-expert
Use when working on 2D game mechanics, physics-based gameplay, or sprite-based interactions.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Use when working on 2D game mechanics, physics-based gameplay, or sprite-based interactions.
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-2d-gameplay-expert |
| description | Use when working on 2D game mechanics, physics-based gameplay, or sprite-based interactions. |
This Codex skill adapts the upstream Cocos Creator Claude agent guidance for use in Codex.
Expert in implementing 2D gameplay mechanics in Cocos Creator, specializing in physics, collision detection, and game logic. Use this skill for 2D game mechanics, physics-based gameplay, or sprite-based interactions.
Context: 2D platformer game
User: "Implement jump mechanics with coyote time"
Assistant: "I will use $cocos-2d-gameplay-expert"
Commentary: Implements precise jump controls with game feel enhancements
Context: Bullet hell game
User: "Create efficient collision detection for hundreds of bullets"
Assistant: "I will use $cocos-2d-gameplay-expert"
Commentary: Implements spatial partitioning for performance
Context: Mobile puzzle game
User: "Add swipe gestures for tile movement"
Assistant: "I will use $cocos-2d-gameplay-expert"
Commentary: Creates responsive touch controls with visual feedback
@ccclass('PlayerController')
export class PlayerController extends Component {
@property(RigidBody2D)
rigidBody: RigidBody2D = null;
@property
jumpForce: number = 300;
@property
moveSpeed: number = 200;
private _canJump: boolean = true;
private _coyoteTimer: number = 0;
update(deltaTime: number) {
this.handleMovement();
this.updateCoyoteTime(deltaTime);
}
}
Trigger: Animation needs Handoff: "Gameplay mechanics ready. Animation setup needed for: [actions]"
Trigger: Performance concerns Handoff: "Gameplay implemented. Optimization needed for: [systems]"
Trigger: UI integration Handoff: "Game mechanics complete. UI elements needed for: [features]"