Instruction file Agreed

The industry's term · its card

Definition

An instruction file gives every session in a place the same standing instructions, so they need not be repeated in each prompt.

An instruction file is a plain Markdown file that an agent harness finds by its name and loads into a session as standing context: from the user's own folder for every project, from the repository's root, and from folders nearer the work, the nearer file taking precedence. Harnesses load the user's and the root's files when a session starts, and some load a folder's file only once the agent works there (AG1, A13, O15, G10). AGENTS.md is the open, shared name (AG1); Claude Code reads CLAUDE.md, and can read AGENTS.md in its place (A13); Codex reads AGENTS.md, with an AGENTS.override.md beside it (O15); and Gemini CLI reads GEMINI.md, its name configurable to AGENTS.md (G10). The instructions are context the model follows, not configuration the harness enforces (A13).

An instruction file is not a skill: it is always loaded, where a skill costs little until a task calls for it.

Our conventions

A Knowledge Islands repository keeps its shared orientation in a physical root AGENTS.md, with any root CLAUDE.md a thin Claude-only appendix that imports it, as ki-repo sets; the owner's own preferences sit in the user-level files.

Next

A plugin is an installable bundle that extends an agent harness with skills and more.