Answer questions about Orkid ECS architecture and APIs with file-level guidance.
npx skills add https://github.com/tweakoz/orkid --skill orkecs-core
Please help me install this Agent Skill. Skill: orkecs-core Source: https://github.com/tweakoz/orkid/tree/main/.claude/skills/orkecs-core Command: npx skills add https://github.com/tweakoz/orkid --skill orkecs-core
Provides a focused, file-level reference for developers who need authoritative answers about Orkid's Entity Component System, scene composition, simulation lifecycle, and Python binding architecture so they do not have to manually search the repository.
Ask for a file-level walkthrough that explains how to create and stage an archetype, how spawning and simulation lifecycles proceed, and how PythonSystem subinterpreters are managed during updates.
High-intent search queries and answers about installing and using this skill.
Orkid's Entity Component System organizes game logic into Entities, Components, Systems, and Archetypes. This Skill maps key header and source locations under the ork.ecs namespace to provide authoritative file-level guidance for C++ ECS core development.
To create and stage an archetype in Orkid's scene editor, you define component data and register it within the scene composition. This Skill provides a file-level walkthrough of the spawn and simulation lifecycle flows from the scene editor/player tools.
Orkid uses a dual Python binding strategy where pybind11 handles controller bindings and nanobind manages simulation subinterpreters. This separation optimizes the PythonSystem script dispatch and update lifecycle within the simulation subsystem.
When adding a new component to Orkid's ECS, locate base classes and lifecycle hooks by referencing the ork.ecs headers. This Skill identifies specific file-level entry points for Python bindings and example editor integrations to streamline development.
PythonSystem subinterpreters are managed during simulation updates through the pyext_sim nanobind bindings. This Skill details the controller and simulation lifecycle, explaining how scripts are dispatched and subinterpreters are maintained across update loops.
Yes, Orkid's ECS core supports simulation subsystem development independently through its C++ APIs and Python bindings. This Skill guides you through the controller and simulation lifecycle details necessary to run updates without the scene editor.
hw-native-sysBuild and validate the PTOAS compiler toolchain from source in WSL.
igamenovoerAuthor and execute schema-rich Houmao agent collaboration loops from a loop directory.
akiojinDesign Unity Editor IMGUI interfaces for EditorWindow, Custom Inspector, and Property Drawer tooling.
tweakozAnswer developer questions about the Orkid C++ media engine with cited source file paths.
