ck-game-feature-recipe

Generate CkFoundation gameplay features with a four-part data model and AutoTests.

4|Updated Aug 15, 2023
One-click install
npx skills add https://github.com/chainkemists/CkFoundation --skill ck-game-feature-recipe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck-game-feature-recipe
Source: https://github.com/chainkemists/CkFoundation/tree/main/.claude/skills/ck-game-feature-recipe
Command: npx skills add https://github.com/chainkemists/CkFoundation --skill ck-game-feature-recipe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides the canonical, maintainer-approved path for adding gameplay features to CkFoundation projects, preventing common architectural pitfalls like race conditions, improper entity composition, and silent failures.

Core Features & Use Cases

  • Feature Lifecycle Management: Defines the strict four-part data model (dynamic handle, fragment split, utils composer, and EntityScript) required for consistent feature integration.
  • Discovery & Timing Safety: Implements robust patterns for asynchronous entity composition and discovery to ensure features are correctly bound and ready for use.
  • Use Case: When adding a new gameplay element like a door, lootable bin, or employee, follow this recipe to ensure your code aligns with the framework's AngelScript-first doctrine and passes all required AutoTests.

Quick Start

Use the ck-game-feature-recipe skill to generate the standard file set and implementation sequence for a new gameplay feature in your CkFoundation project.

Frequently Asked Questions about ck-game-feature-recipe

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add new gameplay features to an Entity Component System without causing race conditions?

To add gameplay features safely, use a standardized architectural blueprint that implements dynamic handles, fragment-based data models, and deferred-request processors to ensure system stability and prevent race conditions.

What is the correct file structure for integrating AngelScript gameplay capabilities in Unreal Engine?

The correct structure requires a strict four-part data model: a dynamic handle, a fragment split, a utils composer, and an EntityScript, ensuring consistent feature integration within the AngelScript-first framework.

How do I ensure asynchronous entity discovery is ready before binding new gameplay components?

Implement robust patterns for asynchronous entity composition and discovery to guarantee features are correctly bound and fully ready for use before execution, preventing silent failures.

Do I need unit tests when building gameplay elements like doors or lootable bins in ECS?

Yes, you must pass required AutoTests. The workflow enforces strict adherence to unit-testing requirements for all new gameplay capabilities to prevent improper entity composition and maintain framework stability.

What is the best way to prevent silent failures when composing entities in a gameplay framework?

The best way to prevent silent failures is following a maintainer-approved recipe that governs deferred-request processors and asynchronous discovery patterns, ensuring proper entity binding and timing safety.

Can I use this gameplay feature recipe for non-CkFoundation Entity Component System projects?

No, this recipe provides the canonical path specifically for CkFoundation projects. It enforces the framework's unique AngelScript-first doctrine and specific four-part data model requirements.