agentic: Instructions file for Codex

Agentic Library — Agent Instructions

This repository is a centralized library of vendor-agnostic agentic configurations. It is never used directly by end-user agents. Its fragments are composed into target project repositories via the tooling provided here.

What This Repo Contains

• agents/ — Composable AGENTS.md building blocks (fragments)
• skills/ — Reusable agent skill definitions
• vendors/ — Vendor-specific adapter configurations
• profiles/ — Composition presets for common project types
• tooling/ — Scripts and utilities (called via just)
• schemas/ — JSON Schemas for all structured files

Rules for Working in This Repo

File Authoring

• Fragment files in agents/ must be self-contained: no cross-references to other fragments, no project-specific paths, no hardcoded credentials.
• Every fragment starts with a single H2 heading (## Section Name) that matches its purpose.
• Fragments must not exceed 300 lines. Split larger content into multiple focused fragments.
• Use {TOKEN_NAME} syntax for project-specific values that get substituted at compose time (e.g., {BUILD_CMD}, {PROJECT_NAME}).

Skill Authoring

• Every skill directory must have a SKILL.md with valid YAML frontmatter.
• Frontmatter must include: name, description, version, tags, vendor_support.
• Skills must declare all supporting files in resources: frontmatter.
• Use SemVer for version (MAJOR.MINOR.PATCH).

Vendor Adapters

• Never edit vendor-generated output files manually. They are derived artifacts.
• The canonical source of truth is always AGENTS.md (assembled from fragments).
• adapter.json files must validate against vendors/_schema/adapter.schema.json.

Documentation

• Any change that introduces, renames, or removes a vendor output file, symlink path, tooling flag, or just recipe must include a corresponding update to the affected docs in the same commit. Relevant files: README.md, docs/vendors.md, docs/commands.md, docs/extending.md, and any vendors/*/README.md.
• When adding a new vendor adapter, add it to the Supported Vendors table in README.md and docs/vendors.md, and document its output files and symlink paths.
• When adding a new just recipe or CLI command, add it to docs/commands.md.
• When adding or updating a skill that references tooling paths or output filenames, verify those paths are still accurate before committing.
• When skills are added, renamed, regrouped, removed, or their user-visible metadata (for example name/description in skill frontmatter) changes under skills/, update docs/skills.md in the same change.