ODAI Development Guidelines

Document ODAI SDK architectural patterns, type systems, and development workflows.

2|1|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/darshan3v/odai --skill odai-development-guidelines
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ODAI Development Guidelines
Source: https://github.com/darshan3v/odai/tree/main/.agent/skills/odai_development_guide
Command: npx skills add https://github.com/darshan3v/odai --skill odai-development-guidelines

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive guide to the architectural patterns, type systems, and development workflows for the ODAI SDK, ensuring consistency and maintainability.

Core Features & Use Cases

  • Architectural Overview: Understand the layered C++ and C ABI design.
  • Type System & Data Flow: Learn how C and C++ types are managed, including ABI stability considerations for enums and unions.
  • Implementation Patterns: Follow best practices for adding new features and designing interfaces.
  • Use Case: A new developer joining the ODAI project can use this Skill to quickly grasp the established coding standards and architectural principles, enabling them to contribute effectively from day one.

Quick Start

Review the ODAI SDK Development Guidelines to understand the project's architecture and coding standards.

Frequently Asked Questions about ODAI Development Guidelines

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

FAQPage Schema
How does the ODAI SDK maintain C ABI stability while using C++ implementations?

The ODAI SDK maintains C ABI stability by carefully managing type definitions and conversion processes at the boundary. It enforces strict architectural patterns that separate the stable C interface from the underlying C++ implementation, ensuring backward compatibility.

What coding standards and naming conventions are enforced for ODAI SDK development?

ODAI SDK development enforces coding standards and naming conventions automatically using clang-tidy and clang-format. These tools ensure consistent code formatting and architectural compliance across the entire C++ and C ABI codebase.

How do I handle memory management and error handling in the ODAI SDK?

Memory management and error handling in the ODAI SDK follow established architectural patterns designed for the C ABI. The guidelines detail specific strategies for safe memory allocation and error propagation across the C++ and C boundary.

How to design interfaces and add new features to the ODAI SDK codebase?

To add new features, follow the ODAI SDK implementation patterns for interface design and data flow. The guidelines detail how to manage type sanitization and conversions, ensuring new code integrates seamlessly with the existing architecture.

When do I need to consider ABI stability for enums and unions in C and C++ type systems?

ABI stability for enums and unions is critical whenever modifying the ODAI SDK type system. The development guidelines specify how to manage these C and C++ types to prevent breaking changes in the compiled interface.

Can I use the ODAI SDK development guidelines to understand the full architectural workflow?

Yes, the ODAI SDK development guidelines provide a comprehensive architectural overview. New developers can use them to quickly grasp the layered C++ and C ABI design, enabling effective contributions from day one.