Look around. Try a small click.

This lesson works as a written guide with interactive examples. You can explore here before opening the real application or provider dashboard. A recorded video has not been added yet.

Read the short lesson

What will make more sense

Use supported project instruction files for durable project guidance and check the selected agent’s scope rules.
A source-of-truth rule helps many tasks inside this project.
Use the selected agent’s documented instruction formats and loading rules.

One idea to keep

Use supported project instruction files for durable project guidance and check the selected agent’s scope rules.

The short lesson

Read the explanation at your pace

Some guidance applies whenever an assistant works in a particular project. It might identify the approved business facts, explain the folder layout or state a project-specific convention. In supporting agent systems, AGENTS.md is one way to preserve that kind of working agreement. Its purpose is different from a reusable skill that applies only to a particular kind of task.

Morningtide Flowers has a small example project containing business-facts.md, a fictional enquiry and draft replies. Its prepared AGENTS.md says which file owns confirmed business facts and explains that this is practice material. An assistant working in that project can use the guidance to avoid treating a sample price or an old draft as the current source.

AGENTS.md is supported by several agent systems, including Codex and compatible VS Code harnesses, but it is not universal. Other assistants may use different instruction formats, settings or loading behavior. Check the documentation for the agent you selected. Renaming a file to AGENTS.md does not make every product recognize it, and simply opening it does not prove it became active project guidance.

Scope also matters. A project-level file should describe that project's needs. Some systems support more specific guidance in subfolders, with their own discovery and precedence rules. You do not need nested instruction files for this first example. The useful concept is that guidance should apply where it belongs, rather than accidentally controlling unrelated client work or personal projects.

Do not confuse a project instruction file with a named custom-agent configuration. Some applications use other file formats to define an agent's role, tools or behavior. This course focuses on readable project instructions and reusable skills. A file can explain a method, but it does not automatically change the application's available tools, system permissions or account access.

The browser activity asks which information belongs in the example project's general guidance. Choose the source-of-truth rule that is relevant across its tasks. Optional practice reads the supplied file rather than installing anything globally. You are learning to place durable project knowledge where a supported agent can find it, then verify that the intended guidance was actually included in the working session.

Try it here

Try it here · no installation needed

Choose the next small step

Follow the prepared example, then select a response to see why it fits. Nothing is connected or changed.

This is a local learning example with prepared responses. It does not run VS Code or contact an AI service.

STEP 1Identify project-wide guidance

STEP 2Use a format the selected agent supports

STEP 3Check the scope and actual loading behavior

What belongs in this project’s general guidance?

Choose an option to see the explanation. You can try every option.

A prompt you can keep

These are example words to copy into your own AI chat when you want to try them. Copying does not send a request.

Read the prepared example for this lesson. Explain the proposed action, its target and the expected result. Keep this as an explanation; do not change files or connect accounts.

A tiny next step, if you want one

Optional: try 2 small actions at your own pace

You can finish this lesson by exploring the example above. These real-app actions are optional, and there is nothing to submit.

Optional: open example-project/AGENTS.md.
Optional: read your selected agent’s official project-instructions documentation before considering its use in a real project.

A quick confidence check

These checkmarks are a personal reminder. Choose what feels familiar, and come back whenever you want.

Use supported project instruction files for durable project guidance and check the selected agent’s scope rules.
I can explain why the matching choice fits this example.
I know which small action I could try later, if useful.

Your place is saved in this browser when storage is available. There is no grading or account sync.

Try a short question

Choose an answer to see why it fits. You can try again or explore every explanation.

What belongs in this project’s general guidance?

Choose an option to see the explanation. You can try every option.

Will every AI product automatically recognize AGENTS.md?

Choose an option to see the explanation. You can try every option.

If something looks different

My assistant or VS Code uses a different label.

Use the official help for your selected assistant and version. The course teaches the decision; the exact menu or capability can differ.

I do not have the account or feature used in the example.

Use the prepared browser example and downloaded notes. No account connection or paid service is required to complete this course.

Sources and further help

Read the official product guidance and related learning resources when you need them. You do not need to read every reference now.