orkid

Answer developer questions about the Orkid C++ media engine with cited source file paths.

35|16|Updated Feb 10, 2013
One-click install
npx skills add https://github.com/tweakoz/orkid --skill orkid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orkid
Source: https://github.com/tweakoz/orkid/tree/main/.claude/skills/orkid
Command: npx skills add https://github.com/tweakoz/orkid --skill orkid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill centralizes knowledge about the Orkid C++ media engine so developers can quickly find architecture details, subsystem responsibilities, build guidance, and Python binding conventions without manually searching the entire repository.

Core Features & Use Cases

  • Subsystem routing: Detects which Orkid subsystem (core, lev2, ecs, data, obt.project) is relevant and directs follow-ups to specialized sub-skills and files.
  • Repository-guided answers: Cites key headers, scripts, and directories to provide actionable, source-referenced guidance for debugging and development.
  • Build and environment assistance: Explains ork.build.py, CMake integration, environment variables, and common build/workflow patterns.
  • Use Case: When porting or debugging the renderer, the Skill points to Vulkan backend files, shader locations, and build flags to modify.

Quick Start

Ask the skill for an architecture overview of a specific Orkid subsystem and request cited file paths to follow up.

Frequently Asked Questions about orkid

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

FAQPage Schema
How do I build the Orkid C++ media engine and configure its environment variables?

To build the Orkid C++ media engine, use the ork.build.py script, which handles CMake integration and environment variable configuration. The skill provides source-referenced guidance for common build patterns and workflow setup.

What is the architecture of the Orkid media engine's subsystems?

The Orkid media engine architecture is divided into subsystems including core, lev2, ecs, data, and obt.project. The skill routes architecture queries to specialized sub-skills and cites key header file paths for each subsystem.

How do I use Python bindings with the Orkid C++ engine?

Python bindings for the Orkid C++ engine allow developers to interact with engine subsystems from Python. The skill explains binding conventions and cites relevant script files to help you integrate Python with the engine's architecture.

Where are the Vulkan renderer backend files and shader locations in the Orkid engine?

When debugging or porting the Orkid renderer, the skill points to specific Vulkan backend files, shader locations, and build flags to modify. It consults repository source files to provide actionable, source-referenced guidance.

Does the Orkid engine use an Entity Component System for application frameworks?

Yes, the Orkid engine includes an ECS (Entity Component System) as one of its core subsystems. The skill provides detailed answers about the ECS architecture and routes follow-ups to specialized guidance for application framework development.

What's the best way to navigate the Orkid engine's asset catalog and threading system?

The best way to navigate the Orkid engine's asset catalog and threading system is by querying the skill for subsystem-specific guidance. It cites key headers and directories, routing you to specialized sub-skills for detailed reflection and asset management tasks.