Turn AI-written Markdown into a properly typeset PDF.

The general-purpose one. Good for reports, proposals, manuals, specifications, and memos.

You are writing a document that will be typeset into a PDF by Lemmafour, a browser-based Markdown-to-PDF engine.

Reply with exactly ONE fenced code block containing only Markdown. No explanation before or after it.

Begin the document with YAML frontmatter, using only these keys:

---
title: <document title>
subtitle: <optional subtitle>
author: <author name>
date: <YYYY-MM-DD>
template: report
toc: true
headingNumbers: true
titlePage: true
---

Choose "template" from exactly this list, whichever best fits the document:
assignment, report, article, readme, resume, proposal, memo, specification,
manual, lecture-notes, minimal, archival

Body rules:
- Use #, ##, ### for headings. Never skip a heading level.
- Display maths on its own lines with $$ ... $$ and inline maths with $ ... $.
  Write standard LaTeX inside them.
- Diagrams: a fenced code block tagged mermaid. flowchart, sequenceDiagram,
  stateDiagram-v2, pie and xychart-beta all work. Never include a
  %%{init: ...}%% directive or a config: block inside the diagram.
- Tables: GitHub pipe tables with a header row and a --- separator row.
- Code: fenced blocks tagged with their language, for example ```python
- Callouts: :::note, :::tip, :::important, :::warning, :::caution
  Each opens on its own line and closes with a line containing only :::
- Footnotes: [^1] in the text, with [^1]: the footnote text at the end.
- Force a page break with a line containing only ::pagebreak
- Do not use raw HTML, inline CSS, emoji, or images loaded from the internet.

Now write the document described here:
<REPLACE THIS LINE with your topic, the audience, and roughly how long it should be>

When you are on mobile and do not want to paste twenty lines. Add your topic at the end.

Write this as Markdown for a PDF. Reply with one fenced code block only.
Start with YAML frontmatter: title, author, date, and template: report
Use # ## ### headings, $$ ... $$ for maths, GitHub pipe tables, and
```mermaid blocks for diagrams. No HTML and no emoji.

Topic: 

Uses the Pro academic template for two-column layout, numbered equations, and labelled figures and tables.

You are writing an academic paper that will be typeset into a PDF by Lemmafour, a browser-based Markdown-to-PDF engine.

Reply with exactly ONE fenced code block containing only Markdown.

Use this frontmatter:

---
title: <paper title>
author: <author name>
date: <YYYY-MM-DD>
abstract: <one-paragraph abstract>
template: article
columns: 2
headingNumbers: true
equationNumbers: true
toc: false
---

Structure: Introduction, Related work, Method, Results, Discussion, Conclusion.

Formatting rules:
- Display equations use $$ ... $$ on their own lines, in standard LaTeX.
- Give equations, figures and tables labels so they can be referenced:
  put {#eq:name}, {#fig:name} or {#tbl:name} at the end of the caption line,
  then refer to them in the prose as @eq:name, @fig:name or @tbl:name.
- Label sections with {#sec:name} after the heading text and cite them as @sec:name
- Use GitHub pipe tables for all tabular data.
- Use footnotes ([^1] with [^1]: text at the end) for references and sources.
  Do not use [@key] citation syntax — that needs a bibliography file.
- No raw HTML, no emoji, no internet images.

Paper topic:
<REPLACE THIS LINE with the subject, field, and approximate length>

Uses the Pro lecture-notes template with theorem, worked-example and solution blocks, plus a formula summary table.

You are writing study notes that will be typeset into a PDF by Lemmafour, a browser-based Markdown-to-PDF engine.

Reply with exactly ONE fenced code block containing only Markdown.

Use this frontmatter:

---
title: <subject and topic>
author: <student or course name>
date: <YYYY-MM-DD>
template: lecture-notes
toc: true
headingNumbers: true
equationNumbers: true
---

Write the notes with:
- ## for each major concept and ### for sub-points.
- $$ ... $$ for every formula, in standard LaTeX, plus a plain-English
  sentence directly underneath explaining what each symbol means.
- :::theorem for statements of rules and laws, closed with :::
- :::worked-example for a fully worked problem, closed with :::
- :::solution for the answer to a practice question, closed with :::
- :::tip for exam technique and common mistakes, closed with :::
- A summary table of key formulas at the end, as a GitHub pipe table.
- No raw HTML, no emoji, no internet images.

Subject to cover:
<REPLACE THIS LINE with the topic, level, and exam board or course if relevant>

Paste Markdown an assistant gave you earlier and this converts it to compile cleanly.

Rewrite the Markdown below so it compiles cleanly in Lemmafour, a browser-based Markdown-to-PDF engine.

Reply with exactly ONE fenced code block containing only the corrected Markdown.

Apply these corrections:
- Add YAML frontmatter at the top with title, author, date, and a template
  chosen from: assignment, report, article, readme, resume, proposal, memo,
  specification, manual, lecture-notes, minimal, archival
- Convert any raw HTML into equivalent Markdown, or remove it.
- Convert \( ... \) and \[ ... \] maths into $ ... $ and $$ ... $$
- Make sure every table has a header row and a --- separator row.
- Tag every fenced code block with its language.
- Remove emoji and any images loaded from a URL.
- Remove %%{init: ...}%% directives from any mermaid diagram.
- Ensure heading levels never skip (no ### directly after #).

Here is the Markdown to fix:
<PASTE YOUR MARKDOWN HERE>