Instructions file GitHub Copilot
Use when writing, editing, or reviewing any code. Enforces naming discipline, comment standards, and variable hygiene across the entire codebase.
🐾 Authority, not credentials, for AI agents: policy-approved actions, delegation that can only narrow, instant revocation, tamper-evident audit.
Instructions file GitHub Copilot
Use when writing, editing, or reviewing any code. Enforces naming discipline, comment standards, and variable hygiene across the entire codebase.
Instructions file GitHub Copilot
Use when changing Caracal commands, package scripts, the web console, runtime CLI launchers, command catalogs, completions, or command documentation. Enforces the runtime-script versus product-management boundary.
Instructions file GitHub Copilot
Use when writing, editing, or reviewing web console help, info pages, field examples, guided setup copy, or example-facing web console UI text. Enforces the approved Caracal demo naming universe.
Instructions file GitHub Copilot
Use when designing packaging, deployment, distribution, feature flags, shared components, or delivery workflows in caracal or caracalEnterprise. Enforces dev/prod separation, centralized shared layers, controlled rollout, and simple secure maintainable delivery practices.
Instructions file GitHub Copilot
Use when creating, updating, or reviewing any instructions.md file in the codebase.
Instructions file GitHub Copilot
Use when writing, editing, or reviewing Caracal documentation under caracal/docs/. Enforces production-grade technical writing, page-flow awareness, and scoped coherent docs edits.
Instructions file GitHub Copilot
Use when creating or editing any source file. Enforces the mandatory copyright header format for all files.
Instructions file GitHub Copilot
Use when updating infrastructure, dependencies, runtimes, build tooling, or platform-facing code in caracal or caracalEnterprise. Enforces latest stable versions and OS-, framework-, and environment-agnostic design through strict abstraction layers and standardized interfaces.
Instructions file GitHub Copilot
Use when refactoring, cleaning up, or reviewing code for legacy patterns, deprecated structures, fallback paths, backward compatibility layers, or duplicate logic.
Instructions file GitHub Copilot
Use when working in caracal or caracalEnterprise. Enforces strict isolation between the open-source and enterprise codebases, including imports, dependencies, shared logic, and license boundaries.
Instructions file GitHub Copilot
Use when adding, changing, or reviewing code in the multi-language client packages (sdk, admin, core, identity, oauth, revocation, verify, adapters, backends). Enforces functional capability parity across TypeScript, Python, and Go.
Instructions file GitHub Copilot
Instructions for Garudex-Labs/caracal, covering caracal sdk integration instructions, core directives and fallback behavior for unsupported scenarios.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: