By the end of this chapter you understand that the files running your AI projects are just plain text you can read and write, and the word technical has lost some of its power over you.
You set up a Project and loaded a file into it. Good. Now the word that has been hovering at the edge of all this: technical. The instructions, the constitution, the things builders pass around with names like CLAUDE.md. They look like a different world. They are not. This chapter takes the mystery out of them in one move.
An .md file is plain text. That is the whole secret. The .md just means it is written in Markdown, which is a way of writing where a hash makes a heading and a dash makes a list. You already understand it because you have read a thousand of these without noticing. There is no code inside. There is nothing to compile. It is a note, and the AI reads it the way you would.
AVATAR OPENER · ~90s
Watch: opening a scary-looking .md file and seeing it is just a note
HeyGen avatar · generated, consistent presenter
People freeze at file extensions the way they freeze at the permission box. The fear is that behind .md is something only programmers can touch. Open one and the fear dies. It is sentences. It is a to-do list with headings. The reason builders use these files is not that they are clever, it is that they are the simplest possible thing: text a human can write and a machine can read, with no translation in between.
What you fear it is
Code. Something only a programmer can open without breaking. A locked door with the word technical on it.
Result: you avoid it, so you stay a user, never a builder.
VS
What it actually is
A plain-text note with headings and lists. You can read it, write it, and change it in any text editor.
Result: you open it, edit it, own it. You are building now.
An .md file is a note the machine reads the same way you do.
A hash makes a heading. A dash makes a list. That is the entire syntax you need to start.
THE WHOLE SYNTAX
You can learn the useful parts of Markdown in the time it takes to read four cards. Everything else is optional decoration. These four cover almost everything you will write.
Headings
A hash and a space makes a heading. More hashes makes a smaller subheading.
Lists
A dash and a space starts a bullet. Stack them and you have a list.
Emphasis
Wrap a word in stars to make it bold. One star for a softer emphasis.
Code or quotes
Backticks mark something to copy exactly, like a filename or a command.
SEE IT
Here is a real .md file. It is the kind of thing that sits inside a Project and runs the whole show. Read it. Notice there is not one thing in it you could not have written.
A real .md file, start to finish
# My shop assistant
## What this is
You help me run my handmade soap shop. Assume that in everything.
## How to behave
- Match my voice from the constitution file.
- For customer replies: warm, short, no filler.
- Ask one question before writing if you are unsure.
## Things to never do
- Never invent a benefit the product does not have.
- Never use exclamation marks.
That file is doing serious work, and it is just headings and bullets. When a builder says they configured an agent, this is often all they mean. They wrote a note. The leap from user to builder is mostly the moment you realise you are allowed to open the note and change it.
NOW YOU TRY · APPLY
Open one and write one
Open any text editor, the plain notes app on your computer is fine. Write a short .md file for one corner of your life: a heading, a few bullets under it, one bold word. It can be a packing list, a recipe, your morning routine. Save it. You just wrote the same kind of file that runs AI projects.
Right if your file uses a heading and at least one list, and you could explain every mark in it to someone else.
Show the worked solution
There is no trick here, and that is the point. A packing list works perfectly: a heading like # Trip to Sofia, then bullets with dashes (- charger, - the good notebook, - meds), then a bold word for the thing you always forget (**passport**). Save it as trip.md or trip.txt, it barely matters. Read it back and notice two things. First, it is readable: the headings and bullets make it scannable to a human. Second, it would be just as readable to an AI, because there is no hidden layer, no code, nothing between your words and the machine. That is why builders use these files for instructions. The format that is clearest to you is also the clearest to the model. If you wrote a heading and a list, you have already written the same kind of file that powers a CLAUDE.md, which is exactly where we go next.
WATCH FOR
✗You see .md and assume it is code. It is plain text. Open it in any notes app and read it like a memo.
✗You try to learn all of Markdown first. Headings, lists, bold, backticks. That is the useful ninety percent. Start there.
✗You are scared to edit a file someone gave you. It is text. Change a line, save, see what happens. You cannot break plain text.
✗You keep waiting to feel technical enough. You will not. You just start opening the files. The feeling follows the doing.
WHAT YOU LEARNED
The takeaways
An .md file is plain text in Markdown. There is no code in it and nothing to compile.
The model reads it the same way you do, which is exactly why builders use plain text for instructions.
The useful syntax is tiny: headings (hash), lists (dash), emphasis (stars), and backticks for things to copy exactly.
The jump from user to builder is mostly realising you are allowed to open the file and change it.
Your project · step six
Take the Project instructions you wrote last chapter and look at them as what they really are: a plain-text file you fully control. Open them, read them as a document, tidy one line. You are no longer just talking to the tool. You are editing the text that shapes how it behaves. Next chapter that file gets a name and a job: your CLAUDE.md.
Technical was never a wall. It was a word on a door that, up close, turns out not to be locked.