t1k:playablelabs:base:engine-core
| Field | Value |
|---|---|
| Module | base |
| Version | 2.29.2 |
| Effort | low |
| Tools | — |
Keywords: engine feature budget, engine feature manifest, feature.json sidecar, playable features decision record, validate feature manifests
How to invoke
Section titled “How to invoke”/t1k:playablelabs:base:engine-core[kitRoot] [--json] [--allow-unknown] [--playable <file>]Engine Feature Schemas (scripts/validate-features.cjs)
Section titled “Engine Feature Schemas (scripts/validate-features.cjs)”The data and checker for the modular engine redesign: the JSON Schemas that describe a feature manifest, the feature sets, the always-on core list and an optional game decision record, plus the one script that checks them. The skill holds no game logic and no packer code.
What is in this directory
Section titled “What is in this directory”| Path | Holds |
|---|---|
schemas/feature.schema.json | feature.json, one sidecar per kit module (never read by the packer) |
schemas/core.schema.json | the always-on core list data/core.json; frozen in phase 1 |
schemas/playable-features.schema.json | playable.features.json, an optional game decision record at the game repo root |
schemas/cocos-cc-config-keys.json | the top-level features keys of Cocos cc.config.json at the pinned engine tag |
data/sets.json | the feature sets (manifestVersion: 1); phase 1 ships one set, core-only, with an unmeasured budget |
scripts/validate-features.cjs | the checker |
scripts/lib-schema-subset.cjs | the JSON Schema subset the schemas use; the checker imports it |
scripts/validate-features.test.cjs | the conformance test: one broken fixture per rule, each asserting its rule name and exit code |
Run the checker
Section titled “Run the checker”bun <skill-dir>/scripts/validate-features.cjs <kitRoot> [--json] [--allow-unknown] [--playable <file>]<skill-dir>is.claude/modules/base/skills/t1k-playablelabs-base-engine-corein the kit repo, and.claude/skills/t1k-playablelabs-base-engine-corein an installed project.<kitRoot>defaults to the current directory. The checker reads<kitRoot>/.claude/modules/<id>/feature.json,data/sets.json, anddata/core.jsonwhen present.- Exit codes, highest applicable wins (2 > 1 > 3 > 0):
0every check passed;1a check failed (cross-reference, sentinel, ownership, option reference);2manifest, schema or usage error;3an unmeasured budget. Exit 3 is not a pass. - Phase 1 has one unmeasured budget (
core-only), so a plain run exits 3 by design. Add--allow-unknownto pass while still listing it. Verified on the phase-1 tree: plain run exit 3,--allow-unknownexit 0. --jsonprints one record per finding and one summary record. Without it, one line per finding.
Run the conformance test
Section titled “Run the conformance test”bun test <skill-dir>/scripts/validate-features.test.cjsExpect 25 pass, 0 fail. A change to the checker or a schema that drops one of those 25 cases is a regression.
Executed by
Section titled “Executed by”Running scripts/validate-features.cjs, reading its report and running its conformance test are mechanical, so a cheap-tier agent may do them. Changing a schema, deciding whether an unmeasured budget may be waived, or judging whether a feature set is correct stays with the main session or a native agent. Routing SSOT: rules/orchestration-rules.md § “Task-Type → Agent Routing”.
Hard rules
Section titled “Hard rules”- The schemas are the SSOT. Edit them only together with a conformance case in
validate-features.test.cjs; the checker reads the schema files, it never copies them. core.schema.jsonis frozen in phase 1 anddata/core.jsondoes not exist yet. A missingcore.jsonis not an error.unmeasuredis never a pass. Do not write a figure intosets.jsonto clear exit 3; the measurement belongs to the phase that owns the size tool.- The test builds its fixtures under the OS temp dir. It needs no network and no installed packages.