# Project files

One folder per project whose files every agent reads and edits in place, instead of a copy per chat.

This is a recipe from flie: a person can read it first, and an agent follows
it. It makes one folder in the person's flie, with a README in it that holds
the rules, so every agent that opens the folder later works the same way.

## 1. Make sure flie is set up

If the `flie` command is not found or `flie whoami` says nobody is signed in,
and you have no flie tools over MCP, set flie up first, with the person's
authorization, by following https://flie.sh/setup.md
Then come back here.

The steps below are `flie` commands. Over MCP, call the tools of the same
names, with the same arguments written as named arguments, and pass a file's
text as `content` instead of `--from`.

## 2. Make the folder

`flie whoami` prints the person's Root folder. Make the folder there unless
the person names another place. If a folder called "<project name>" is already
there (`flie agent list <root ID>`), use it: read its README and follow it
instead of starting again.

    flie agent mkdir <root ID> "<project name>"

Name the folder for the project, as its files or the person name it, not for the directory.

Each command prints the new item's name and its ID; every later command names
the item by that ID. Laid out, the folder is:

    <project name>/
      README.md      the rules
      brief.md       goal, owner, deadline
      checklist.md   done and left

## 3. Write the README, then start

Write this README into the folder, adapted where the person says so, with the
text on stdin:

    flie agent create --from - <folder ID> "README.md"

~~~markdown
# <Project name>

Every file of <the project>. Agents read and edit them here, in place.

- brief.md: the goal, who owns it, the deadline, and what done looks like.
- checklist.md: what is done and what is left, kept current.
- Folders for anything else the project needs, named for what is in them.

## Rules

- Edit files here, in place. Never keep a copy somewhere else, and never
  re-upload one; every earlier version is kept here.
- When the brief changes, change brief.md, and say what changed in the
  checklist.

## When to write

- At the start: the brief and the checklist.
- Whenever a file of the project changes, or something is done.
~~~

Then create brief.md and checklist.md the same way.

Start from the project’s own files: look through the directory you are working in (and any the person names), and read them. Write brief.md from them and from what the person tells you, and checklist.md from what is done and what is left. Then put each of the project’s existing files in the folder (flie agent create <folder ID> "<name>" --from <path>), and from then on edit them there.

## 4. Ask the person, then connect their other agents if they want

Any agent reaches this same folder once its host has flie's server registered,
once per host. Offer it; register only the hosts the person asks for:

- **Claude Code** — `claude mcp add --transport http flie https://flie.sh/mcp`
- **Codex** — `codex mcp add flie --url https://flie.sh/mcp`, then `codex mcp login flie` to sign in
- **Cursor** — add `{"mcpServers": {"flie": {"url": "https://flie.sh/mcp"}}}` to `~/.cursor/mcp.json`

In Cursor, flie shows Needs authentication under Tools & MCPs in its settings, and Connect there is what opens your browser. The person completes each sign-in, not you.

## Done

Tell the person what you made, give them the folder's link
(`flie agent link <folder ID>`), and ask whether to connect their other agents (step 4).
Editing its README changes the rules for every agent that reads it. How to
change a file without losing anyone's edits: https://flie.sh/skill.md.
End your reply with the question in step 4.
