Skip to content

Your first session

  1. Rename the folder. Rename familiar-workspace/ to your project’s name and move it where you want it. This folder is the agent’s workspace.

  2. Add your sources (now or later). Copy in what you want the agent to know.

    Folder Suggested use
    1-Inputs/Sources/ Documents to ingest: reports, minutes, articles
    1-Inputs/Admin/ Scope, SOWs, contracts, timelines, correspondence
    1-Inputs/Templates/ Files to build from: a branded PowerPoint template, a Word report template, a standard workbook. Keep this name. The deck builder looks here.
    1-Inputs/Examples/ Past deliverables to learn a style from

    The other subfolders are suggestions. Add, rename or nest your own. Keep the five numbered top-level folders as they are.

  3. Open your agent in that folder. The agent finds its instructions in the folder it opens in.

    • Terminal: cd into the folder and start the agent (claude, for example).
    • VS Code: File → Open Folder, then open Claude Code.
    • Claude desktop app: the Code tab, with this folder chosen.
  4. Run the check-in: /ili-project-status check-in. It reads what is already in the folder. Then it asks only what the files cannot answer:

    • the project name and what it is for
    • the next concrete outcome, and any deadline
    • a signature: three characters that stand for this project, such as v_v or o.o

    When it finishes, the project has a configuration, a status snapshot and a first set of tasks.

  5. Start working. From the next session on, the first reply opens with the bound line: *(v_v) familiar bound*: Project Name.

The bound line shows that the instructions loaded. With several projects open in different windows, it also shows which project is answering. The fleet hub labels each project with its signature too.

You see It means Do this
Your project’s signature and name Loaded, right project Nothing
Another project’s signature The agent opened in another project’s folder Reopen it in the right one
Your default signature This project has no signature of its own Set one: /ili-system-settings preferences
not set No signature anywhere yet Set one: /ili-system-settings preferences
n/a The agent could not read the signature Ask it to try again. See Troubleshooting.
No line at all The instructions did not load See Troubleshooting

The bound line is a check, not a lock. The rules are instructions that the model follows.