For someone who has a project and a coding agent, and wants the agent to keep a library of documents beside the code: notes, explanations, records of what was decided and measured.

You will not learn a command line here. You will learn what to ask your agent for, what it does in reply, and where to look at the result.

How every chapter is told: you ask, the agent acts, you get a result YOU ASK in plain words, in your agent THE AGENT ACTS follows a skill, runs the commands YOU GET files in your project, pages to read
Each chapter is told in this order. Read the left box as your part, the middle as the agent's, the right as what lands in your repository.

Who it is for, and what it assumes

You have

A git repository, and a coding agent that can run commands in it.

You do not need

To learn the folio command. Your agent runs it, the way it runs git.

You end with

A library in your project, a few linked documents, and a way to review them.

How to read it

In order, once. Each chapter assumes the ones before it and nothing else, so a later chapter may use a word an earlier one taught.

Inside a chapter, a stepper walks through what happens one step at a time: press Next, or pick a step. With scripts off, the steps read as a list. After each idea comes a check-yourself: answer it in your head before you open it.

The last two chapters are about comments. Read the final one when people other than you will review the library.

Do you need to learn the folio command before you start?
No. Your agent runs it. Each chapter shows what to ask for, and the commands appear only so you can see what the agent did.