qmd-prover는 AI 코딩 조수에 대한 부가 기능입니다. Claude Code 또는 Codex — that help it 실제 수학을 쓰고 확인한다. 그것은 글쓰기 증거에 대한 분야를 설정하고, 그 후 그 분야는 다음을 확인합니다.

분야. 당신의 수학은 일반 텍스트 .qmd] 파일로 작성됩니다. .qmd 파일은 단지 일반 텍스트 파일 (모든 편집기에서 열 수 있습니다) Quarto라는 형식에 작성 마크다운. 내부, 모든 정의, lemma, theorem, 그리고 증거는 자체 ** 블록 **에 앉아. A 블록 3개의 대장의 선에 의해 열리고 닫히고, :::], 그것의 첫번째 선은 짧은 상표를 줍니다 어떤 종류의 것을 말한다. 여기에 완전한, 작은 예 — 하나의 정의, 하나의 theorem, 그리고 그것의 증거:

그 조각에서 읽기 :

• ::: … ::: 텍스트의 나머지 부분에서 한 블록을 울타리. 두 줄 사이의 모든 것 의 식민지는 그 블록에 속한다. ([T5]] 중간에 mathematical 표기법은 무엇인가? 작성; 그것은 진짜 기호로 나중에 렌더링.)
• **#def-even는 블록 ** 상표 ** - 짧은 이름, @id]입니다. 모든 문에는 하나가 있고, 그것은 전체적인 프로젝트를 통해 독특합니다. -.definition / .theorem /`.

qmd-prover

qmd-prover is an add-on for your AI coding assistant — Claude Code or Codex — that helps it write and check real mathematics. It sets up a discipline for writing proofs, and then checks that the discipline was followed.

The discipline. Your mathematics is written in plain-text .qmd files. A .qmd file is just an ordinary text file (the kind you can open in any editor) written in a format called Quarto markdown. Inside it, every definition, lemma, theorem, and proof sits in its own block. A block is opened and closed by a line of three colons, :::, and its first line gives it a short label and says what kind of thing it is. Here is a complete, tiny example — one definition, one theorem, and its proof:

::: {#def-even .definition name="Even number"}
An integer $n$ is **even** when $n = 2k$ for some integer $k$.
:::

::: {#thm-sum-even .theorem name="Sum of two even numbers"}
If $a$ and $b$ are even, then $a + b$ is even.
:::

::: {.proof of="thm-sum-even"}
By @def-even, write $a = 2k$ and $b = 2m$. Then $a + b = 2(k + m)$,
which is even by @def-even.
:::

Reading that from the pieces:

• ::: … ::: fences one block off from the rest of the text. Everything between the two lines of colons belongs to that block. (The $…$ in the middle is just how mathematical notation is written; it renders as real symbols later.)
• #def-even is the block’s label — its short name, its @id. Every statement has one, and it is unique across the whole project.
• .definition / .theorem / .proof says what kind of block it is. name="…" is the plain title a reader sees.
• The proof is its own separate block, and of="thm-sum-even" links it to the statement it proves. A statement and its proof are never mixed together.
• @def-even inside the proof is a pointer: it says “this step uses the definition labeled def-even.” Every time a proof leans on another result, it names that result this way, right at the spot where it uses it. Those pointers are what make every assumption visible.

You never type any of this — the assistant writes it. What matters is that the discipline is fixed, so the assistant (and the checks) can always tell which result depends on which.

Among all the results you build, one theorem is the one you ultimately want proved — that theorem is your goal. In the example above, the theorem thm-sum-even would be the goal, and the definition exists only to support it.

How the discipline is checked. Because every proof follows the discipline, the work can be checked in two layers:

• Mechanical checks (no AI). A plain program reads all the references @id and confirms the wiring is sound: every block has a unique label, every proof links to a real statement, every @id points at a result that actually exists, and no chain of citations loops back on itself. This