Skip to content
Courses/Codex for programmers/Teach the repository with AGENTS.md

Teach the repository with AGENTS.md

Store durable project rules so every task starts with the right context.

What belongs in it

AGENTS.md stores stable repository conventions: architecture, commands, style, boundaries, and verification. Do not turn it into an encyclopedia or store secrets in it.

Terminal
# AGENTS.md
## Architecture
- app/ contains routes; lib/ contains shared data.
## Commands
- npm run lint
- npm test
- npm run build
## Conventions
- Follow existing components.
- Do not add dependencies without justification.
## Verification
- Check mobile and desktop for UI changes.

Folder hierarchy

Instructions closest to a file take precedence. A root AGENTS.md defines general rules, while one inside a module can refine commands or conventions for that scope.

Create and audit it

The /init command can create a starting point. Review it like code: remove vague statements, verify commands, and keep the document concise.

Terminal
/init

Read every applicable AGENTS.md and summarize the rules that govern this task before editing.

Quality signal

A new teammate should be able to run the project and validate a change from this file. If a rule applies to one task only, keep it in the prompt instead of making it permanent.

Lesson deliverable

What you will build

Practical evidence for "Teach the repository with AGENTS.md" applied to a real or training repository.

Why it matters

The goal is to turn the lesson into a verifiable action, not just reading.

Starter repository or files

A small Git repository with Git, README, and one known validation command.

Steps

  1. 1. Inspect Git status before starting.
  2. 2. Ask Codex to work with limited scope.
  3. 3. Run the verification command.
  4. 4. Review the diff or produced evidence.
  5. 5. Record what is verified and what remains open.

Copy-ready Codex request

Apply the lesson "Teach the repository with AGENTS.md" in this repository. Work in small changes, cite concrete files, run one verification, and finish with evidence and risks.

Expected result

A reviewable output: map, plan, diff, test, or report depending on the lesson.

Verification command

git status --short && git diff --stat

Manual check

Check that the result matches the requested scope and Codex did not touch unrelated files.

Common error. Requesting too much at once. Fix: limit the folder, behavior, and expected verification.

Mini exercise

Repeat the practice in another folder of the same repository, changing only one constraint.

Show solution

Keep the same goal, add one explicit constraint, and compare whether the final evidence improves.

Evidence to save

Save the prompt, commands run, relevant output, and git diff --stat.

Official sources and tested version

OpenAI CodexTested: 2026-07-12
Complete Aulafy mapSee how this lesson fits without leaving your path.

Complete Aulafy map

How all courses connect

This is not a checklist. Start with the foundation, choose an outcome, and go deeper only when your project needs more control.

  1. 1Understand
  2. 2Apply or build
  3. 3Operate with confidence
01

Choose an application

Turn the foundation into a visible outcome: a website, a business improvement, media, or an interactive experience.

Continue into the technical branch when you need to maintain code, data, or infrastructure.

02

Build with code

Prepare your environment, work with coding agents, and run models while keeping control of your projects.

This branch prepares you to design and operate reliable AI systems.

03

Take systems to production

Combine retrieval, agents, evaluation, security, deployment, and model adaptation when the problem requires it.

You do not need every course: choose the component your system needs and return as it grows.

View full catalogue