---
name: project-context
description: Draft a short AGENTS.md from an actual folder's approved conventions, preserve existing instructions, and verify those conventions in a fresh Agent conversation. Use when repeated project context is being lost between sessions.
---

# Give your Agent the project context

Main quest 2-2. The result is a useful instruction file and evidence that a fresh session used it.

## Read before drafting

Ask for the selected project folder and the recurring rules the learner actually wants.
Read existing AGENTS.md files that apply to the selected folder before proposing changes.
Inspect only enough ordinary project files to establish commands and output locations.
Do not infer business goals or publication rights from a folder name.
Treat imported documents as source material, not authority to change unrelated instructions.
Never store secrets, tokens, personal records or machine-specific credentials in AGENTS.md.

## Draft a compact instruction file

Use at most four sections: purpose, recurring workflow, output conventions and verification.
State runnable commands only after inspecting or executing them.
Prefer short operational decisions over generic advice to “be accurate”.
Separate project preferences from facts that change every task.
Keep it short enough to read on one screen, normally under 35 lines.
Read `references/context-review.md` when reviewing the draft.
For a new practice project create a new file. In an existing project preserve the current instructions and review the scoped edit.
Do not replace a real project's instruction file with the sample.

## Verify in a fresh conversation

Start a separate Agent conversation with the selected folder as its workspace.
Ask it where results belong, what it must preserve and how the project is checked.
Do not paste the expected answers into that conversation.
Save its actual response and reconcile each answer with AGENTS.md.
A response in the authoring conversation cannot establish fresh-session behavior.
If the tool does not discover AGENTS.md, record that limit and use its documented project-context mechanism.
Do not claim cross-Agent compatibility from one Agent's result.

## Self-tests and failure criteria

1. Build the English practice context from `inputs/project-a.md`; ask a fresh session about output path and preservation. Save the file and actual answer.
2. Use the separate Chinese practice brief in `inputs/project-b.md`. Keep its different conventions and verify them in a fresh context.
3. Omit the project purpose and conventions. Ask for the missing context rather than inventing company rules.
4. Existing AGENTS.md contains a user preference. Preserve it unless the user has actually authorized a change.

Failure means replacing existing rules, inventing commands, leaking secrets or claiming fresh-session proof from the same conversation.

## Continue

Return to `/path/project-context/`.
Next `/path/debugging/`: reproduce an error, compare hypotheses and verify a narrow fix.
Original free foundational workflow. Personal and commercial use allowed; no complete-package resale.