Skip to content

t1k:cocos:base:skill-domain-routing

FieldValue
Modulebase
Version4.51.9
Effortlow
Tools—

Keywords: cocos skill, discover skill, find skill, playable skill, route to skill, routing, skill domain, skill for, skill lookup, skill routing, which skill

/t1k:cocos:base:skill-domain-routing

Intent-based discovery: the SSOT for “which t1k-cocos-* skill handles X” (core skills such as cook, fix, plan: theonekit-core/.claude/skills/t1k-help/references/skill-domain-routing.md; placement: references/placement-rationale.md).

Each bullet reads intent → skill. 109 skills across 6 modules: base (33), blind-edit (1), h5 (2), omarchy (4), playable (69), art-pipeline (0). Rows marked theonekit-core ship from another kit. Bullets are cut to their opening clause; full wording: references/routing-full-descriptions.md.


Module: base — Cocos tooling and conventions

Section titled “Module: base — Cocos tooling and conventions”

Required module (every preset). Applies to any Cocos Creator project, playable ads included.

  • Start a brand-new Cocos H5 game (not a playable ad): which template to clone, what it ships, what it deliberately leaves out → skills/t1k-cocos-base-knowledge-sweep/references/starting-point-templates.md
  • Start a brand-new playable ad from a concept brief → t1k-cocos-playable-gen (scaffolds from concept-brief.md); the folder layout it targets → skills/t1k-cocos-playable-modularize-structure-audit/references/blueprint.md
  • Look up naming, @ccclass/@property decorators, the SignalBus named-method rule, lifecycle… → t1k-cocos-base-code-conventions
  • Work out why a collision-group bit test (collider.getGroup() & BIT) reads false, or decide… → t1k-cocos-base-code-conventions
  • Decide whether a pattern (pooling, FSM, SignalBus, component split, service singleton) is… → t1k-cocos-base-architecture-patterns
  • Scan Cocos TypeScript for the traps no editor check sees — Map/Set iterator spread or for…of… → t1k-cocos-base-source-scan-guard
  • Ask the studio corpus “do we already have this?” — the FIRST prior-art step, run before… → t1k-cocos-base-knowledge-sweep
  • Structure a feature module, decide where game logic lives, or make logic unit-testable without… → t1k-cocos-base-clean-architecture
  • Add or change an engine-free packages/* library package in a Cocos pnpm workspace — rung… → t1k-cocos-base-engine-free-package, t1k-cocos-base-package-developer
  • Design an entity-component-system (components, systems, queries, ordering) → t1k-gamedev-ecs-design (theonekit-gamedev, a hard dependency of cocos:base); this kit ships no ECS skill, the runtime is the studio library The1Studio/CocosECS
  • Know how theonekit-gamedev’s neutral skills (test, arch, debug, knowledge, assets) detect and run on a Cocos project → t1k-cocos-base-gamedev-adapter
  • Clean-room recreate a Cocos project from a link, APK or zip (extract, spec, rebuild, validate) → t1k-cocos-base-cleanroom-adapter

docs/system-design.md is the handoff contract the family grades against, so its artifact and grading are two skills. Route by which you need:

You want to…Skill
Author, migrate, or verify docs/system-design.md; generate docs/design-manifest.json; resolve the templatet1k-cocos-base-system-design
Judge whether the code conforms to it, or which pattern the code is now obliged to uset1k-cocos-base-architecture-patterns
Read the doctrine itself (SOLID, module boundaries, class roles, anti-patterns)Neither — the project’s own docs/system-design.md § Code Structure Rules
  • Author a design doc from the canonical template, or convert a non-canonical / ASCII-tree doc… → t1k-cocos-base-system-design
  • Turn the doc into the machine-readable module map consumers use, or check it still matches the… → t1k-cocos-base-system-design
  • Understand state: as-is | to-be | converged, parse, or priorArt before trusting a… → t1k-cocos-base-system-design

architecture-patterns never writes the doc: it reports a stale doc, and system-design repairs it.

  • Generate @ccclass class diagrams, a module dependency graph, or a scene/prefab hierarchy;… → t1k-cocos-base-script-graph
  • Ask a structural question grep cannot answer — who calls this, what breaks if I change it, is… → t1k-cocos-base-code-graph
  • Raise TSDoc quality so annotated code is actually discoverable by doc_search (so the reuse… → t1k-cocos-base-doc-flywheel
  • Run the whole TSDoc chain (audit → author → annotate → export → verify) in one call → t1k-cocos-base-doc-pass
  • Work out which t1k-cocos-* skill handles X in the first place → t1k-cocos-base-skill-domain-routing
  • Work out which Cocos agent to spawn for a task (ideation, runtime bug, feature, optimization,… → t1k-cocos-base-agent-domain-routing
  • Work out why a Spine 4.2 physics constraint that reacts in Spine Editor or spine-unity does… → t1k-cocos-base-spine
  • Import, validate, rename, or promote assets from _Incoming/ to canonical locations under the… → t1k-cocos-base-asset-import
  • Hand-author a Cocos 3.8.7 .effect shader, its .mtl material, and the material wiring → t1k-cocos-base-effect-authoring
  • Port a Unity .shader (Amplify, Shader Forge, hand-written) into a Cocos 3.8.7 port spec → t1k-cocos-base-unity-shader-port
  • Edit scene/prefab/material/.meta JSON or a look-spec colour with the Cocos editor CLOSED, then verify it in ONE canary build → t1k-cocos-blind-edit-assets

The single JS→TS pipeline. The optional migration module shipped a drifted fork of these six skills and was absorbed into base on 2026-08-15; t1k-cocos-migration-* no longer resolves.

  • Run the full 5-phase pipeline (PRECONDITION → t1k-cocos-base-migrate
  • Build the require-graph, Export-Form Registry, and component-name graph the pipeline reads → t1k-cocos-base-dep-graph
  • Codemod one .js into a coexistence .cv.ts (ts-morph) → t1k-cocos-base-js2ts
  • Gate the converted file with the TypeScript version pinned to the editor bundle → t1k-cocos-base-tsc-validate
  • Rewrite string-name component lookups (getComponent("Foo") and friends) for JS/TS coexistence → t1k-cocos-base-compref
  • Attach a .cv.ts component to a prefab/scene without deleting the JS (.meta + UUID re-point) → t1k-cocos-base-uuid-verify

TypeScript pin for the JS→TS gate and the TSRS exemption: references/maintainer-notes.md.


Module: playable — the playable-ad runtime

Section titled “Module: playable — the playable-ad runtime”

Optional module (requires base). The largest module: 69 skills.

  • Set up game flow states (boot, loading, gameplay, end card, CTA, audio) → t1k-cocos-playable-gameflow
  • Manage object lifecycle, init order, and teardown for non-Component systems → t1k-cocos-playable-lifecycle
  • Implement a finite state machine with decorator registration and async transitions → t1k-cocos-playable-fsm
  • Set up touch detection, gesture recognition, or 3D raycasting → t1k-cocos-playable-input-service
  • Build adaptive canvas layouts for portrait/landscape — aspect-ratio detection, safe-area insets → t1k-cocos-playable-layout
  • Show pooled toast notifications and UI feedback → t1k-cocos-playable-toast
  • Implement screen transitions between game states (fade, slide, scale, curtain) → t1k-cocos-playable-transitions
  • Drive interactive tutorials and step-by-step animated hints → t1k-cocos-playable-tutorials
  • Build a UI prefab from a reference image, reusing existing project UI/assets → t1k-cocos-playable-ui-from-image
  • Reconstruct whole screens from a Figma file — discover screens over the REST API, map… → t1k-cocos-base-figma-to-ui
  • Install @playablelabs/ui-loading-endcard into a “Ready”-template playable, author its… → t1k-cocos-playable-ready-figma
  • Localize the game end-to-end: scan scene/prefab/config/dynamic text, generate locale tables,… → t1k-cocos-playable-localize
  • Move a playable onto the pre-engine HTML splash (remove LoadingView) → t1k-cocos-playable-splash-setup
  • Author reusable flying-animation clips with object-pool integration → t1k-cocos-playable-animation-core
  • Use preset animation sequences (bounce, shake, pop — 20 presets) or register custom ones → t1k-cocos-playable-animation-presets
  • Add juice to existing tweens and to bare show/hide with @playablelabs/motion → t1k-cocos-playable-juice
  • Measure / fit / center / hit-test a runtime-loaded sp.Skeleton — uploaded spine renders at… → t1k-cocos-playable-spine-fit
  • Convert a Unity ParticleSystem prefab into a Cocos 3.8.7 cc.ParticleSystem → t1k-cocos-playable-unity-particle
  • Make a 3D cc.ParticleSystem render under a Canvas (2D/UI space) → t1k-cocos-playable-particle-ui
  • Rig an unrigged FBX in headless Blender and export named in-place looping clips Cocos imports → t1k-cocos-playable-fbx-rig-animate
  • Track level progression and scale difficulty per level → t1k-cocos-playable-progression
  • Compute and display score, combos, and flying reward effects → t1k-cocos-playable-score
  • Pool and recycle prefabs — spawn/recycle lifecycle, category organization → t1k-cocos-playable-object-pool
  • Use async/await utilities and cancellation tokens → t1k-cocos-playable-async-utilities
  • Decouple systems with a type-safe SignalBus → t1k-cocos-playable-signalbus
  • Wire fonts globally or per-label → t1k-cocos-playable-font-service
  • Reach for pure math/data helpers (Math, Array, Vec, Coordinate, Time) → t1k-cocos-playable-utilities
  • Load, cache, and de-duplicate typed resources against a size budget → t1k-cocos-playable-asset-management
  • Reduce build size: engine module pruning, texture/mesh compression, ad-network budget compliance → t1k-cocos-playable-build-size
  • Make a 3D playable run smoothly: draw calls, first-use stalls, memory, weak devices → t1k-cocos-playable-runtime-perf
  • GPU/fill-rate → t1k-cocos-playable-gpu-perf
  • Decide what a playable may defer past its first view and author the per-game lazy-load policy… → t1k-cocos-playable-lazyload
  • Make a Creator 3.8.7 build compile the studio engine fork (The1Studio/cocos-engine) instead… → t1k-cocos-playable-studio-engine
  • Headless-verify a built playable or running preview in Chrome over CDP — console errors, JS… → t1k-gamedev-playable-preview-verify
  • Integrate an ad-network SDK (TheOne, Voodoo), postMessage parameter updates, CTA routing → t1k-cocos-playable-sdk-core
  • Add or extend playable-ad event tracking — decide whether the playable should emit analytics… → t1k-cocos-playable-analytics
  • Use custom editor scripts, the config watcher, or the Cocos MCP server tools → t1k-cocos-playable-editor-tools
  • Upload, tune, preview and export through the PlayableLabs platform MCP → t1k-cocos-playable-playablelabs-mcp

Parameter System (dashboard-tunable config)

Section titled “Parameter System (dashboard-tunable config)”

Start at the orchestrator; it routes to the rest.

  • Run parameter discovery → implementation → wiring end-to-end → t1k-cocos-playable-parameter (orchestrator)
  • Scan the scene Canvas or *Config.ts files for tunable candidates → t1k-cocos-playable-parameter-scan
  • Decide the node shape / preset for a grouped node (Button, Image, Text, CurrencyUI, HPBar, Countdown) → t1k-cocos-playable-parameter-composite
  • Generate the flat-primitive PlayableConfig entries and typed ParameterController wiring → t1k-cocos-playable-parameter-implement
  • Assign scene node UUIDs to @property references over MCP → t1k-cocos-playable-parameter-mcp
  • Find DEAD parameters — defined but never wired, no-op onUpdate, or wired to a missing @property → t1k-cocos-playable-parameter-audit
  • Produce the operator-facing parameter guide (XLSX + DOCX) → t1k-cocos-playable-parameter-guide
  • Draft AI-context entries (description, aliases, aiHints, examples) for PlayableConfigMeta → t1k-cocos-playable-pla-gen-metadata

Modularize — legacy project → CPM packages

Section titled “Modularize — legacy project → CPM packages”

Start at the orchestrator; the four pillars run in order.

  • Audit and modularize a legacy playable toward the CPM model → t1k-cocos-playable-modularize
  • Grade folder layout against the blueprint (Pillar A) → t1k-cocos-playable-modularize-structure-audit
  • Classify subsystems REUSE/EXTEND/KEEP/CONTRIBUTE (Pillar B) → t1k-cocos-playable-modularize-reuse-scan
  • Decide target module architecture (Phase 2.5) → t1k-cocos-playable-preproduction
  • Synthesize audits into an ordered refactor plan (Pillar C) → t1k-cocos-playable-modularize-refactor
  • Contribute local work back to @playablelabs (Pillar D) → t1k-cocos-playable-modularize-contribute
  • Package a standalone capability into cocos-stdlib → t1k-cocos-base-stdlib-contribute
  • Harvest reusable code from PLA repos → t1k-cocos-playable-stdlib-harvest
  • Dry-run what the stdlib detector would flag → t1k-cocos-playable-stdlib-scan
  • Run one autonomous lane over assets/scripts/ → t1k-cocos-playable-stdlib-autocontribute
  • Rewire a PLA project onto published packages → t1k-cocos-playable-stdlib-adopt
  • Cut a gameplay folder into vertical mechanic folders → t1k-cocos-playable-mechanic-split
  • Remove cc imports from game logic → t1k-cocos-base-engine-decouple
  • Measure function-granularity shape against a pinned baseline → t1k-cocos-playable-primitive-decompose
  • Measure how much own code consumes the stdlib → t1k-cocos-playable-reuse-coverage
  • Record a golden-master characterization → t1k-cocos-playable-characterization
  • Take a playable through the whole stdlib retrofit → t1k-cocos-playable-pla-retrofit
  • Migrate off the PLA git submodules to vendored packages → t1k-cocos-playable-submodule-to-package

Competitor Analysis, Estimation & Target Design

Section titled “Competitor Analysis, Estimation & Target Design”
  • Reverse-engineer a competitor playable from its URL → t1k-gamedev-playable-extract
  • Turn an Insightrackr catalog row into a runnable reference → t1k-gamedev-playable-insightrackr
  • Capture a Play Store listing as design reference → t1k-cocos-playable-market-reference
  • Port a reference HTML playable to a Cocos build: 3D layout, 2D surface (HUD, audio, end card), parity audit → t1k-cocos-playable-ref-port
  • Scope a playable before code exists → t1k-cocos-playable-preproduction
  • Decide the target module structure for an existing codebase → t1k-cocos-playable-preproduction, t1k-cocos-playable-modularize
  • Run a whole playable from a reference or concept prompt → t1k-cocos-playable-pla-from-ref
  • Observe a real reference game and emit REFERENCE.md → t1k-gamedev-playable-ref-capture
  • Author the pre-code design pack → t1k-gamedev-playable-design-pack
  • Synthesize SFX from a JSON cue spec → t1k-designer-audio-sfx-synth (theonekit-designer); import it → t1k-cocos-base-asset-import
  • QA a playable’s gameplay flows via window.__qa → t1k-gamedev-playable-qa-flows
  • Run the shared preview verifier on a Cocos playable → t1k-cocos-playable-gamedev-adapter

Production Pipeline — Plane tracking & Jenkins builds

Section titled “Production Pipeline — Plane tracking & Jenkins builds”
  • Log an agreed breakdown or an estimate report to Plane as a work-item tree, bind the repo to… → t1k-cocos-playable-pipeline
  • Understand why work-item titles read Client|Playable|Task rather than core’s… → t1k-cocos-playable-pipeline
  • Go from a concept-brief.md to a scaffolded playable in one command — validate the brief,… → t1k-cocos-playable-gen
  • Resolve and write project-info.json for a Cocos playable-ad project — git remote, Jenkins… → t1k-cocos-playable-project-info

Multi-Platform Publishing — @playablelabs platform SDK

Section titled “Multi-Platform Publishing — @playablelabs platform SDK”
  • Ship one Cocos game to many portals (Poki, CrazyGames, Yandex, WeChat, Douyin, Telegram,… → t1k-cocos-base-platform-integrate
  • Know why a feature is missing on one portal but present on another, and why unsupported and… → t1k-cocos-base-platform-integrate
  • Decide whether a rewarded ad may grant persisted currency on a given portal → t1k-cocos-base-platform-integrate § “Reward trust”
  • Turn a shipped Cocos Creator 2.4.x APK into an editable project that opens in the editor and builds, brief the worker lanes, verify their evidence → t1k-cocos-base-apk-unbuild

  • Know which gate must be GREEN before “it opens in the editor” (build, gate.py, verify-all.cjs, the editor-open probe) → t1k-cocos-base-apk-unbuild § 5

  • Port a shipped game into a Cocos Creator 3.8.7 template game (extract, data, art and colour parity, UI, polish): APK/XAPK → core t1k-apk-port + t1k-cocos-base-apk-port, iOS IPA → t1k-cocos-base-ipa-port

  • Unpack an XAPK or IPA and detect the engine → core t1k-apk-port (xapk-unpack.cjs --target cocos for an APK; ipa-unpack.cjs --target cocos for an IPA, exit 4 = FairPlay-encrypted), then t1k-cocos-base-ipa-port for an IPA

  • Read an IL2CPP method body (literal-pool floats, constants, call targets), or the dumper rejects the metadata version → core t1k-apk-port (il2cpp-setup.cjs); iOS Mach-O: t1k-cocos-base-apk-port

  • Work around a Cocos MCP or Write-tool gotcha (project targeting, manage_asset url param,… → t1k-cocos-playable-tooling-gotchas
  • Make an editor MCP write falsifiable — resolve the per-editor port and server name, confirm… → t1k-cocos-base-editor-mcp-truth
  • Fix a bug in the Cocos MCP Server extension itself — reproduce over HTTP, failing test,… → t1k-cocos-playable-mcp-fix

Optional (t1k modules add h5), depends on base. Unlike playable (one ad-network deliverable), this is a multi-portal game repo built by its own Jenkins job, made by hand from The1Studio/H5CocosTemplate.

  • Set up the H5 game repo’s Jenkins autobuild job, check its build preconditions… → t1k-cocos-h5-jenkins-setup
  • Diagnose an H5 game job started by an unrelated cocos-platform-sdk merge → t1k-cocos-h5-jenkins-setup
  • TikTok Minis review/design → t1k-cocos-h5-tiktok-minis

Module: omarchy — Creator on an Omarchy host (opt-in, t1k modules add omarchy)

Section titled “Module: omarchy — Creator on an Omarchy host (opt-in, t1k modules add omarchy)”
  • Set up Creator via winpodx: guest, launchers, Hyprland rules → t1k-cocos-omarchy-winpodx
  • Install Dashboard/Creator in the guest → t1k-cocos-omarchy-guest
  • Reach the guest editor from mcp__cocos-creator__* → t1k-cocos-omarchy-editor-bridge
  • Verify the Omarchy + winpodx chain → t1k-cocos-omarchy-doctor
  • Sync, launch, web build, pull → t1k-cocos-omarchy-pod-build

Symptom lookup: full games and Unity ports

Section titled “Symptom lookup: full games and Unity ports”

User phrases for recurring mistakes. A hidden skill (autoload: user-only) is not in the skill list: Read its SKILL.md.

  • Children faded, subtree vanishes, CanvasGroup/ScrollRect/trimmed sprite differ from Unity, popup backdrop passes taps, back button; screens differ from the APK, fixes “on disk” unseen; uGUI prefab mismatch (preserveAspect, LayoutGroup, RectMask2D) → t1k-cocos-base-apk-port
  • Toon too dark, hit flash, render queue, WebGL2 off, HDR greys the map → t1k-cocos-base-effect-authoring
  • Particles too small/white, sub-emitters, pooled particle does not replay (hidden) → t1k-cocos-playable-unity-particle
  • Null sprite, hand-written subMeta, 9-slice border, auto-atlas, alpha halo → t1k-cocos-base-asset-import, t1k-cocos-base-editor-mcp-truth
  • flatMap/fromEntries/replaceAll typecheck error, debug key in release → t1k-cocos-base-source-scan-guard
  • Rename the CocosTemplate/ folder → t1k-cocos-base-cleanroom-adapter; pool not loaded after stage reload, teardown crash → t1k-cocos-playable-object-pool
  • Lost save, double IAP grant, balance owner (hidden) → t1k-cocos-base-platform-integrate
  • Generator overwrote another lane’s rows, duplicate keys → t1k-cocos-base-architecture-patterns
  • Label tiny in a long language, pooled labels skip the language switch (hidden) → t1k-cocos-playable-localize; squares for a language → t1k-cocos-playable-font-service
  • fitHeight letterbox, notch, design resolution → t1k-cocos-playable-layout; toast over a popup → t1k-cocos-playable-toast
  • Camera shake, damage numbers, haptics → t1k-cocos-playable-juice; reward count-up → t1k-cocos-playable-score; entrance scales a button to zero → t1k-cocos-playable-animation-presets
  • Spine 4.1 will not import → t1k-cocos-playable-spine-fit

Boundary notes (modularize vs mechanic-split, Plane/Jenkins, platform SDK, apk-unbuild): references/boundary-notes.md.

check-routing-coverage.cjs (scripted: t1k-list-classifier lists each uncovered skill); the intent row is written by t1k-cocos-base-developer. Maintainer facts and module requirements: references/maintainer-notes.md; core-routing SSOT: theonekit-core orchestration-rules.md § “Task-Type → Agent Routing”.