ChuuInstruct

00

How much do you want to decide?

Every setting below produces the same twelve sections of rules. The slider only changes how many choices you are asked to make. Nothing is withheld at the simple end.

Level

The file is for whoever will follow the rules — you, a teammate, a local model, an editor. You pick the filename when you take it.

Included at every level

These are the reason the file works. They are never optional and never behind a setting.

Validation tiersSix levels of proof. Only the top one earns the word "works."

PermissionNothing destructive happens until you name the target and answer.

PrivacyNothing leaves your machine without you being told first.

PriorityWhat wins when two rules collide.

Diagnosis and stop conditionsReads the whole log, and stops instead of spiralling.

Reasoning, with the Socratic underlayStarts from what is not known rather than guessing confidently.

01

About you

This is the part the assistant reads to know who it is talking to. Skip anything that does not apply — blank fields are left out of the file.

What should it call you? What do you do? Plain words. "Solo developer", "technical writer", "systems architect". What are you good at? What do you struggle with? Naming it stops the assistant from mistaking one for the other. Do you work alone? How much time do you get at a stretch? What are you working on? One per line. What are you building toward?

02

Your machine

Every fact here is an explanation you never have to give twice.

Operating system Shell you actually use Hardware worth knowing Only what limits you — graphics memory, total memory, disk space. Where your code lives Where big files go Models, caches, build output. Leave blank if it all goes in one place. Programs and tools you use One per line. Editors, runtimes, package managers, anything you expect it to reach for. Naming them stops it suggesting something you do not have. Directories that matter — optional One per line, as label: path. Everything you type here ends up in a file you paste into an assistant. Use a placeholder like work: (my work folder) if the real path is nobody else's business — the rules still work. Commands you always have to run One per line. The permission bypass, the tool with the odd name, the flag you always forget.

03

Sections

All of these are on by default. Turn one off only if you know you do not want it.

Validation — always included The tier ladder and the honesty rules around it. This is the part that stops "it works" from meaning "it compiled."

cannot be removed · it is the point of the file

Optional sections

PriorityWhat wins when two rules disagree.

PermissionNothing destructive happens without you naming the target first.

DiagnosisRead the whole log, one hypothesis at a time, and stop before spiralling.

ProjectStructure rules that survive renaming a folder.

MethodShort answers, fewest steps, sessions treated as a cost.

ReasoningHow to think through a problem: modality, scope, counterexamples. Shapes the logic, not the wording.

PrivacyNothing leaves the machine without you being told first. Reading stays inside the directories you named.

ConductDisclosure when it edits the rules, and never using "no" to dodge work.

Underlays

A stance under the thinking, not a method. Stack them. They sit under whichever style you choose, or under none.

SocraticNot a method — the absence of one. Starts from what is not known.

IrrationalDoes not treat reasonableness as the default virtue. Keeps contradiction and discomfort. Refuses a tidy answer that is only tidy.

ObservationalLooks before it names a principle. Steals analogies across domains, then checks they actually map. Leaves the unresolved marked.

Thinking style Adds a way of reasoning on top of the Reasoning section. Shapes how a problem is approached, not how the answer sounds.

04

Your own rules

Optional, and the most valuable screen here. If you have explained something to an assistant twice, write it once now. One rule per line — the builder puts each line in the right place.

Write these to fit, not to fight. Your lines are added inside a section, not placed above it. A line like "never explain anything" will sit next to a rule asking for explanation, and both will be followed badly. Nothing you write here can override validation or permission — those two always win.

Rules about how it talks to you Goes into Method. Rules about your projects Goes into Project. Rules about what it may touch Goes into Permission. Anything else Goes into its own section at the end.

05

Take the file

Save this as a file in the project, or paste it into a settings field that applies to every conversation rather than one. The rules do not name a vendor. The choice below only sets the filename and the import note.

Save as

Record (optional)

Written as a comment above the file, outside the instructions. Leave blank and the lines still appear, unfilled, so you can complete them after testing.

Built by Tested by Tested against Test prompt Result

Every tag has its closing tag — checked above.
Nothing is left in brackets — checked above.
Read it once before pasting. It is your file now.
Come back any time to build a new one. Nothing is stored.