Skip to content

theonekit-cocos

Version: 0.0.0

TheOneKit kit theonekit-cocos β€” auto-generated reference.

  • art-pipeline β€” Opt-in companion for 3D asset work: the 2D concept (Gemini, via the router image role or t1k-extended-multimodal) -> 3D (Tripo) -> optimize-in-Blender pipeline is documented in the theonekit-tripo skill t1k-tripo-base-concept-pipeline, and Blender-specific gotchas ship in t1k-cocos-playable-tooling-gotchas/references/blender-*.md. Declares no dependencies of its own β€” the required base module depends on the art kit (theonekit-art, the renamed theonekit-blender), which ships the Blender and Cocos glTF/playable export skills (the former art-pipeline cross-kit deps were removed in issue #1020 when no such kit existed). Carries no skills of its own β€” a 2D or backend-only Cocos project never pays for this; opt in via t1k modules add art-pipeline.
  • base β€” Cocos kit baseline: ts-morph + dependency-cruiser script-graph adapter for scene/prefab diagram introspection, manifest-driven asset import pipeline for assets/_Incoming/ promotion, and the single JS->TS migration pipeline for Cocos Creator 2.4.x (dep-graph β†’ js2ts β†’ tsc-validate β†’ compref β†’ uuid-verify, orchestrated by migrate + cutover). Purpose: contribute reusable code to the studio library β€” the named destination for generic Cocos code is The1Studio/cocos-stdlib (@playablelabs/ packages); PLAGameFoundation is legacy (fixes only). The playable-ad runtime itself lives in the playable module.
  • blind-edit β€” Blind edit of Cocos Creator scene, prefab, material and .meta JSON without the editor: span-exact JSON editor, id-graph guard, static validator, look-spec shape and ONE canary-build confirm round
  • h5 β€” Opt-in H5-game build-job module. A full Cocos H5 game repo is created BY HAND from The1Studio/H5CocosTemplate (this module never creates one) and is built for every portal target by the cocos-platform-sdk PlatformMatrix pipeline via a thin Jenkinsfile loader. Carries two skills. t1k-cocos-h5-jenkins-setup validates that repo’s build preconditions and then creates + verifies its CocosPlayableLabs Jenkins job through core’s t1k-jenkins-job script. t1k-cocos-h5-tiktok-minis reviews or designs a game for TikTok Minis against the required-button checklist and the Strategy/Action/Simulation genre benchmarks. Distinct surface from the playable-ad path: a playable ad is a single ad-network deliverable provisioned by t1k-cocos-playable-pipeline, while this is a multi-portal full game repo on its own autobuild job.
  • omarchy β€” Opt-in Omarchy (Arch + Hyprland) Linux-host module. Installs winpodx, creates its Windows guest from one user-chosen JSON config, installs Cocos Dashboard + Creator inside the guest (human steps are one-click handoffs), adds Hyprland window rules and desktop entries for the Cocos windows, plumbs the cocos-mcp-server editor bridge from the guest to the host loopback, and verifies the chain by reusing base’s editor-doctor. Pod-build loop (sync the project into the guest, launch Creator with MCP, headless web build with log-based verdict, pull, verify the bundle). Host-side only: every script refuses to run off an Omarchy host, and nothing here ships in-editor code.
  • playable β€” Playable-ad runtime: FSM, lifecycle, signal bus, layout, transitions, SDK glue, and all ad-network deliverables. Purpose: contribute reusable code to the studio library β€” the named destination is The1Studio/cocos-stdlib (@playablelabs/ packages), PLAGameFoundation is legacy (fixes only), and PlayableAdsTemplate is a template rather than a destination.