بنقرة واحدة
cocos-3d-gameplay-expert
Use when working on 3D game mechanics, physics simulations, or 3D environment interactions.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Use when working on 3D game mechanics, physics simulations, or 3D environment 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-3d-gameplay-expert |
| description | Use when working on 3D game mechanics, physics simulations, or 3D environment interactions. |
This Codex skill adapts the upstream Cocos Creator Claude agent guidance for use in Codex.
Expert in implementing 3D gameplay mechanics in Cocos Creator 3.x, specializing in 3D physics, character controllers, and spatial interactions. Use this skill for 3D game mechanics, physics simulations, or 3D environment interactions.
Context: 3D adventure game
User: "Create smooth third-person character movement"
Assistant: "I will use $cocos-3d-gameplay-expert"
Commentary: Implements physics-based movement with camera follow
Context: 3D action game
User: "Implement melee combat with hit detection"
Assistant: "I will use $cocos-3d-gameplay-expert"
Commentary: Creates hitboxes, damage calculation, and combat feedback
Context: Racing game
User: "Add realistic car physics with suspension"
Assistant: "I will use $cocos-3d-gameplay-expert"
Commentary: Implements wheel colliders and suspension system
@ccclass('CharacterController3D')
export class CharacterController3D extends Component {
@property(RigidBody)
rigidBody: RigidBody = null;
@property(CapsuleCollider)
collider: CapsuleCollider = null;
@property
moveSpeed: number = 5;
@property
jumpHeight: number = 2;
@property
gravity: number = -20;
private _velocity: Vec3 = new Vec3();
private _isGrounded: boolean = false;
update(deltaTime: number) {
this.checkGrounded();
this.applyGravity(deltaTime);
this.handleMovement(deltaTime);
}
}
Trigger: Visual effects needed Handoff: "3D mechanics ready. Shader effects needed for: [features]"
Trigger: 3D performance issues Handoff: "3D gameplay implemented. Optimization needed for: [areas]"
Trigger: Lighting setup Handoff: "3D environment ready. Lighting design needed for: [scenes]"