For non-developers · 5 min read

Markdown for non-developers

The only six things you need to know to read every Markdown file your AI will ever hand you.

By Yigit Ihlamur5 min read

ChatGPT, Claude, and Gemini default to Markdown when they write anything structured: meeting summaries, project plans, draft emails with headings. If you've been using AI for more than a few weeks, you've already seen the files. The good news: Markdown is small. Six rules cover roughly 95% of what an AI will ever emit. Once you know them, the raw text looks like a normal document.

This is the reference card. Not exhaustive; just the parts you'll actually encounter.

1. Headings start with #

One # is a top-level heading. Two (##) is a sub-heading. Three (###) is a sub-sub-heading. The hash sign always sits at the start of the line with a space after it.

# Quarterly review ## Q3 highlights ### Engineering

When the file renders, each level gets a different size and weight, like the headings in a Google Doc.

2. *Stars* mean emphasis

One star (or one underscore) around text makes it italic: *example* renders as example. Two stars make it bold: **example** renders as example. Three (sometimes) renders as both bold and italic, but AI assistants rarely use it.

If you see ~~text~~ with tildes, that's strikethrough, the equivalent of a line through the word.

3. Lists are dashes or numbers

Bullet points start with a dash (-) or asterisk at the start of the line. Numbered lists use literal numbers followed by a period.

- First point - Second point - Nested point (indent two spaces) - Third point 1. Numbered first 2. Numbered second

One thing that catches people out: AI assistants sometimes write 1. for every item in a numbered list. When rendered, the actual numbers come out as 1, 2, 3 anyway. Don't be alarmed if the source looks wrong; the output is right.

4. Links use square brackets and parentheses

The pattern is [visible text](actual URL). The visible text goes in square brackets, the URL in parentheses right after.

See our [website](https://docs.vela.partners) for details.

Renders as: See our website for details. Same idea for images, with a ! in front: ![alt text](image-url).

5. Code uses backticks

Single backticks around inline text mark it as code, usually a filename, command, or short snippet:git statusrenders in a monospace font.

Three backticks on a line by themselves start a code block, with another three backticks ending it. Inside, AI assistants often include a language hint (python, js) for syntax highlighting.

6. Tables use pipes and dashes

Markdown tables look intimidating in source but render cleanly. Vertical bars separate columns, a row of dashes separates the header from the body.

| Name | Role | Status | |-------|----------|--------| | Sam | Designer | done | | Lee | PM | review |

You'll mostly see these in AI-generated summaries of data or status reports.

That's almost everything

Other Markdown features exist (block quotes with >, horizontal rules with ---, footnotes with [^1], task lists with - [ ]) but they're either uncommon in AI output or self-explanatory in context. The six rules above cover the vast majority of what you'll see.

The bigger jump is from "I now know what these symbols mean" to "I'm reading the file in a way that renders the symbols properly." Notepad, TextEdit, and most email clients show the raw syntax. To see the file the way the AI intended, drop it onto a Markdown viewer.

One short takeaway

Markdown is a small, learnable format. Six rules cover what your AI will throw at you. Knowing them won't make you a developer, but it does mean you'll never again wonder why your file is full of asterisks.

Related reading: