bindings-synchronization
Guidelines and SOP for synchronizing public C++ API changes (methods, enums, options structs) to Java (Android JNI) and JavaScript/TypeScript (Web/WASM Embind).
20.26k repo starsObserved in 1 repos
Development
Development skills
Browse reusable Agent Skills, each with a clear purpose and practical guidance.
cpp-header-inclusion
Enforce the strict topological header inclusion layering and reordering rules in Filament. Use this skill when adding or modifying `#include` directives in C++ source or header files.
20.26k repo starsObserved in 1 repos
Development
cpp-static-thread-safety
Enforce C++ static thread safety annotations and correct synchronization primitives. Use this skill when designing multi-threaded classes or editing guarded member fields.
20.26k repo starsObserved in 1 repos
Development
filament-build-clean
Clean and build Filament targets for development, debugging, and production. Use this skill whenever you need to clean the workspace or compile desktop targets.
20.26k repo starsObserved in 1 repos
Development
filament-lifetime
Enforce correct Filament object creation and destruction lifecycles. Use this skill when initializing rendering pipelines or allocating/deallocating GPU buffers and entities.
20.26k repo starsObserved in 1 repos
Development
filament-math
Enforce correct mathematical primitives and naming conventions in Filament code. Use this skill when performing coordinate transformations, vector math, or projection setups.
20.26k repo starsObserved in 1 repos
Development
header-self-containment
Enforce strict header self-containment so that every header file compiles independently. Use this skill when creating or modifying C++ header files.
20.26k repo starsObserved in 1 repos
Development
preprocessor-guard-hygiene
Enforce preprocessor guard rules and macro-dependent inclusion hygiene in C++. Use this skill when modifying conditional imports or preprocessor directives.
20.26k repo starsObserved in 1 repos
Development
coding
Route code, repository, and data/SQL work to isolated Kortix sessions instead of burning your main context on it. Use when asked to implement a feature, fix a bug, make failing tests pass, work a ticket/issue, refactor, navigate or change a codebase, ship a PR, review a pull request, or run SQL/warehouse analysis against a dataset — and when the user wants two agents or parallel reviewers/investigators on the same work. Covers the explore-vs-session routing call, deciding where the code lives (this project's repo vs cloning an external GitHub repo) or where the data lives, finding the repo with gh, spawning sessions in parallel, dual PR reviews, and reporting results back. Triggers: 'implement', 'fix the bug', 'make the tests pass', 'work this ticket', 'refactor this', 'open a PR', 'review this PR', 'run two agents on it', 'query the warehouse', 'analyze this dataset'.
19.97k repo starsObserved in 1 repos
Development