Knowledge

@knowledge is reference context stored in your library. Assistants can load it directly or when an instruction references it; only the requested files are fetched, so context stays focused. Files are static (no arguments or dynamic fields) and are sent as-is when referenced.

Reference from an instruction using @fileName. See Referencing @knowledge in /instructions for syntax.

Common knowledge context

• API documentation (schemas, endpoints, response formats, error codes)

• Architecture and design (system diagrams, database schemas, component relationships)

• Development standards (style guides, coding standards, review checklists)

• Domain and business logic (business rules, validation logic, permissions)

• Workflows and procedures (deployment workflows, onboarding guides, operational steps)

Example

A brand-compliance knowledge file. When an instruction says “base your review on @brand-guidelines”, the model receives this:

Title: brand-guidelines.md
Description: Official brand colors and typography for consistent styling.

Primary colors: Honey #E69135, Anti-flash white #E7E8E9, Black #040406.
Secondary: Teal #63D0BD, Lavender #A68BF3, Warm Orange #E99363.

Typography: Headings use ES Build (Arial fallback). Body text uses Inter (Arial fallback).
Use only these fonts; flag any other font in code as non-compliant.