Typora

Promptfree, for everyone, and the only version there is

Copy the prompt for Claude CodeCopy the prompt for CodexCopy the prompt for Cursor

Copy

Build me a Markdown editor that replaces Typora: it renders as I type, with no split preview, and nothing in the cloud.

STACK
- A desktop application: Electron or Tauri, or a PWA if it can be installed and work offline
- CodeMirror 6 as the editing engine, with decorations doing the rendering. Do not write a text editor from scratch
- No server component at all. This is a file editor and the files are on disk

THE ONE FEATURE
- Markdown is rendered in place as you type. A heading becomes large, bold becomes bold, and the syntax marks disappear except on the line the cursor is on
- That last clause is the whole trick: the marks must be visible where you are editing and hidden everywhere else, so the document reads as a document but is always directly editable
- No split preview. A split preview is what this product exists not to be, and it is why people pay for it

HOW IT IS ACTUALLY DONE
- CodeMirror 6 with a decoration layer: parse the document, and for each construct apply a decoration that either styles the text or replaces the syntax marks with nothing
- The marks are revealed when the selection intersects the construct's range. That single rule produces the entire experience
- Block-level constructs — headings, quotes, lists, code fences, tables — get line decorations; inline constructs get mark decorations
- Images, maths and diagrams are replaced by widget decorations rendering the real thing, which un-render when the cursor enters them
- The document remains plain Markdown text at every moment. There is no separate model to keep in sync, which is what makes this approach reliable

WHAT MUST WORK PROPERLY
- Tables: editable as a grid, with Tab moving between cells and the source staying valid pipe-table Markdown. This is the hardest one and the one people use most
- Code blocks with syntax highlighting per language, and no Markdown rendering inside them
- Lists with correct continuation, indentation with Tab, checkbox toggling by click
- Maths with a local KaTeX, rendered inline and as a block
- Diagrams with a local mermaid, rendered as a widget
- Images shown inline, from a relative path, with a paste-an-image flow that writes the file next to the document and inserts the link. Where that file goes is configurable and stated
- Footnotes, front matter, and link reference definitions

FILES, WHICH ARE THE POINT
- Open a file, edit it, save it. Plain Markdown, on disk, nothing else
- A file tree for a folder, with search across it
- Watch the file for external changes and reload if untouched, or prompt if not — because the same file is also being edited by a script, a sync tool or another machine
- Autosave optional and off by default; some people want it and some are horrified by it
- Never rewrite parts of the file the user did not touch. Preserving exact whitespace, list markers and line endings is what makes this safe to use on a repository

EXPORT
- HTML with a chosen theme and inlined styles, PDF through the platform's own print pipeline with proper page breaks and a header and footer, and Word if you can
- The export theme is a CSS file, and so is the editor theme. That is the whole theming system and it is enough
- Export a folder as a static site, optionally

WHAT NOT TO ADD
- No account, no cloud, no sync. The files are on disk and any sync tool already handles them, which is the honest position and also the selling point
- No analytics. A text editor knows what you are writing and that is nobody's business
- No proprietary format. If the application disappeared, every document must still be a Markdown file

THE INTERFACE
- The document, and nothing else, by default. A sidebar and an outline that can be shown
- A focus mode dimming everything but the current paragraph, and a typewriter mode keeping the cursor line centred
- Dark and light, both readable, with measured contrast
- A word count that does not count the syntax
- Fast: opening a large document must be instant, and typing must never stutter. Parse incrementally and never re-render the whole document on a keystroke

OPERATIONS
- Configuration in a plain file the user can read
- No network access at all. That is a feature, and it should be verifiable

WHAT MATTERS MOST
The reveal-on-cursor rule and never rewriting untouched text. Build the decoration layer with the reveal behaviour first and edit a real document with it for a week; then check a file through a version control diff and confirm nothing changed except what you typed.

Give me the repository, the editor with its decoration layer, the export pipeline, the themes, and a README explaining the CodeMirror approach and what it deliberately does not do.