chainkemists/CkFoundation

ck-game-feature-recipe

Use when adding a CkFoundation gameplay feature and need the standard AngelScript file set, composition order, discovery contract, processors, spawn vehicle, and tests.

ck-game-persistence-recipe

Use when making a CkFoundation gameplay feature survive save/load — declaring fragment postures, writing setup that reads restored values, consuming load completion, holding references across a load, and round-trip tests; not for the snapshot machinery itself…

ck-performance-and-analysis

Use when profiling, benchmarking, or making Ck performance claims with stats, Unreal Insights, A/B tests, scheduler pumps, signals, or memory; not for functional bugs.

ck-angelscript-interop

Use when exposing CkFoundation APIs to AngelScript, debugging ScriptMixin or generated bindings, or repairing AS codegen; not for AS syntax, tests, or build setup.

ck-build-and-env

Use when setting up a Ck engine/plugin workspace or fixing engine association, stale binaries, DLL locks, build config, module rules, or headless boot; not for failure triage.

ck-debugging-playbook

Use when triaging Ck build, UHT, linker, AngelScript, editor-boot, packaged-only, GC, DLL-lock, or PIE-versus-packaged failures; not for setup, profiling, or incident history.

ck-vfx-authoring

Use when authoring or porting a VFX in the CkParticles/CkUsf code-only pipeline: new behaviors, faithful recreations of reference Niagara effects, look shaders, cadence rows, A/B parity work in the VfxExamples gym. Carries the campaign's hard-won incident…

ck-change-control

Use when classifying and gating a Ck change, selecting compile/test/review evidence, or enforcing ensure and cross-environment checks; not for diagnosis or campaign planning.

ck-failure-archaeology

Use when checking whether a Ck failure, workaround, rejected design, or stalled branch has prior history before retrying, removing, or resurrecting it.

ck-feature-frontier

Use when choosing what Ck framework work to build, harden, optimize, or prioritize next; not for live bug triage, campaign execution, or performance measurement.

ck-game-angelscript-gameplay

Use when writing CkFoundation gameplay AngelScript: utils and mixin idioms, deferred requests, signal binding, hot reload, or deciding between AS and C++.

ck-game-build-and-cook

Use when building, cooking, staging, or packaging a CkFoundation game on Windows, including plugin script staging, fresh-workspace cooks, and stale outputs.

ck-game-debugging-playbook

Use when CkFoundation gameplay compiles but misbehaves at runtime: missed discovery or signals, ignored requests, invalid handles, interaction stalls, or PIE divergence.

ck-game-driver-architecture

Use when designing a CkFoundation game driver or director that owns subordinates, scopes tag discovery, routes requests, and exposes readiness to consumers.

ck-game-entity-composition-patterns

Use when choosing a CkFoundation game entity archetype, lifetime owner, context root, child-entity topology, or the narrow cases that justify an Actor bridge.

ck-game-framework-boundary

Use when game code would bypass CkFoundation public APIs, mutate fragments directly, add globals, copy internals, or when a game pattern may belong upstream; not for normal feature composition.

ck-game-project-bootstrap

Use when bootstrapping a new CkFoundation game repo: engine registration, Git and submodules, project targets, config, script generation, skills, and first entity.

ck-game-replication-patterns

Use when making CkFoundation gameplay multiplayer-safe: replication stance, ActorRelay ownership, rep-notify ordering, authority routing, or client readiness.

ck-game-testing-discipline

Use when choosing coverage and test layers for CkFoundation gameplay, structuring AutoTests, preventing shared-world contamination, or defining proof of no regressions.

ck-lifecycle-teardown-campaign

Use when executing Ck entity-teardown and signal-unbind work, especially mid-interaction destruction, leaked bindings, TeamListener cleanup, or EndPlay gaps; not for triage.

ck-macros-and-codegen

Use when reading or writing CK_ macros or adding Ck fragments, processors, requests, signals, tags, snapshot registration, or typesafe handles; not for architecture rationale.

ck-methodology

Use when Ck work spans sessions, many files, a new module, or architecture; for campaign docs, phase gates, stuck pivots, resumptions, and CTO reviews; not for single-change gates.

ck-plan-handoff

Use when /plan is invoked or when planning a Ck handoff package for a later lower-tier session. Planning only; do not implement or use to execute an existing plan.

ckecs-architecture-contract

Use when reasoning about why CkEcs is structured as it is or which invariants a change must preserve across handles, requests, signals, fragments, replication, and GC.

ckecs-domain-reference

Use when reasoning about EnTT and CkEcs internals: registry storage, views, entity versions, processor pumps, destruction, actor bridges, transient roots, or fragment GC.

ck-ship-pr

Publish CK superproject and submodule work like ck-ship-dev, but submodules go out as feature-branch PRs for the maintainer to merge instead of direct dev pushes. Use when the user asks to ship via PRs, or when the session's maintainer has a standing PR-first…

ck-ship-dev

Use when publishing CK superproject and plugin work through commit, fetch, rebase, post-rebase gates, submodule pushes, pointer bumps, and dev delivery.