Now, or this afternoon.
Claude Code reads the file AGENTS.md at every start. Its last part, Your team’s rules, holds no rules yet, only three
steps as a placeholder. Now you fill it in, together with Claude Code. Claude Code interviews you, you answer,
Claude Code writes.
Let Claude Code interview you
-
In Claude Code, send this:
Interview us, one question at a time, and write our team's rules into AGENTS.md, under the heading "Your team's rules". Ask, then wait for our answer. First ask which project we have. Then look at our workflows in n8n and our flows in Langflow. Then go through these six principles, one at a time. For each, suggest our rule in one or two sentences, and ask us whether it fits or what to change: 1. One task per piece: each flow does one job. 2. A contract for each flow: which fields go in, which come out. 3. One place for the data. 4. A fixed rule decides; the model only proposes. 5. Each part may do only what its job needs. 6. Where a person decides. At the end, show us the whole text before you save it. Replace only the three steps under the heading. Leave everything above the heading as it is. -
Claude Code interviews you, one question at a time. Answer in a few words.
-
Claude Code shows the whole text before it saves. Is it right? Say what to change, then agree.
Check that Claude Code knows your rules
-
Leave Claude Code with
/exit, and start it again:cd ~/kingo-pod && ./kingo claude -
Send this:
What are our team's rules? Answer in six short lines.
Claude Code names your team’s rules. From now on, every teammate’s Claude Code builds the same way: your
names, your contracts, where a person decides. Nobody has to explain it again in each session. Your teammates want the
same rules? Send them the text under Your team’s rules. Each pastes it into their own
~/kingo-pod/claude/AGENTS.md, under that heading (open the file as in the homework).
How do you start Claude Code? Match each situation with its command. All four start Claude Code inside the sandbox, nono.
| Situation | Command |
|---|---|
| Claude Code asks you before every command | ./kingo claude |
| Claude Code works without asking you | ./kingo yolo |
| Your own folder, for example for your thesis: no n8n, no Langflow | ./kingo claude --in ~/projects/thesis |
| Your own Claude subscription pays, with Anthropic’s models | ./kingo claude --login |
More about the four
- In
./kingo claude, Shift+Tab switches the mode. In plan mode, for example, Claude Code first makes a plan and changes nothing until you agree. ./kingo yoloasks nothing, but the sandbox stays. Your laptop stays protected.--intakes a folder inside your home folder: not a Windows folder, and not kingo-pod. Claude Code can write only there. There it reads that folder’s ownCLAUDE.mdorAGENTS.md, not your team’s.--loginasks you to log in once, at the first start. You need no OpenRouter key.
Quiz. Which model does Claude Code use in the course, and where is that written?
- Claude, from Anthropic, always
- GLM 5.3 Flash through OpenRouter, written in
claude/.claude/settings.json - The model of your Langflow flows
Show the answer
GLM 5.3 Flash, through OpenRouter. It is written in ~/kingo-pod/claude/.claude/settings.json. Want another
model? The page ws2_claude_model.html in your download shows how.
An example: Anthropic’s Claude Sonnet 5.5, with an Anthropic API key. The page shows it in four steps, under Use Anthropic’s API, or another provider:
- Save the key in
~/.config/kingo/anthropic.key. - Give the sandbox the route to Anthropic, in
~/kingo-pod/my-nono-profile.json. - In
settings.json, delete the line"ANTHROPIC_API_KEY": "",, and let the lines that name the model say Anthropic’s models, for exampleclaude-sonnet-5-5. - Start
./kingo claudeagain.
This afternoon, your team’s page: Team A · KSMC · Team B · Kgoda · Team C · K-Motor