Everything it does.

All of it in service of one thing: showing you a set of documents you own but have never seen together.

Finding them

• Reads Markdown (.md), plain text (.txt), HTML (.html), Word (.docx) and PDF (.pdf), anywhere beneath the folder you point it at.
• Reads nothing until you choose a folder. The chooser opens on your Claude skills folder, so the common case is one click; take that one and the plugins tree beside it comes too, as a second root.
• Opens a single document as well, from the button beside the folder one. It reads that file and lists no directory around it, so whatever sits beside it stays unread.
• Browse to any other folder instead, a notes folder or a project's documentation; the choice is remembered for next time.
• Hidden and cache directories are passed over; so is a branch that leads to no document at all, so every branch you can open leads somewhere.
• A folder it cannot open costs only itself rather than the whole tree.
• A Word document is turned into HTML as it is read, so it reads like everything else here. HTML rather than Markdown because escaping into it is total: whatever the author typed stays text, where Markdown would read an indent as a block of code and a leading hyphen as a list. Word arranges pages with tables as often as it tabulates anything, so a table that is really layout gives up its contents as the paragraphs they are rather than being drawn as a table.
• A PDF is read back into the document its page was laid out to be, with its pages marked. A PDF holds no headings, no paragraphs and no lists; it holds glyphs, each with a place, a size and a face. Ask it for the words alone and a CV arrives as a wall of monospace with every heading, every bold phrase and every bullet gone, so the sizes and the faces are read the way your eye reads them: larger than the body is a heading, bold is emphasis, a bullet opens an item, lines running on are one paragraph. That is a reading of the page rather than anything the file says, because the file does not say: no fonts, no rules and no pictures come across, while a form's grid becomes reading order, since a document read back as prose is prose. Where a PDF is a scan, a picture of a page rather than the words on it, no text can be taken and it says so instead of showing you nothing; a PDF that is password protected says that.
• Opening a folder of them does not read them. Listing forty PDFs of twelve pages was measured at 7ms where extracting them all took 515ms; the text is fetched for the one document you pick.
• Runs nothing a document carries. A page's scripts are dropped rather than executed, so a document somebody sent you cannot act on your machine; anything needing a script runtime is inert and shows as the plain text around it.
• Fetches nothing on a document's behalf. A picture stored beside the document is shown; one held at a web address is not fetched and not shown, because the reading surface has no way to reach the network at all.

Finding your way around

• The tree mirrors your folders exactly, to whatever depth they go, with the file's own name on each document so you can find it again anywhere else.
• Every folder opens and closes on its own arrow; Enter or Space works it from the keyboard.
• Each folder carries a count of what it holds, so a shut branch tells you whether it is worth opening.
• Folders you leave open are remembered, so a run opens as the last one closed.
• Everything opens shut and nothing is selected until you select it. A reader who has chosen nothing is not shown something chosen for them.

Reading one

• The selected document is rendered to be read, not shown as raw text.
• Plain text is shown exactly as it was typed, since its line breaks are the author's own layout rather than the renderer's.
• The fields it declares are laid out plainly; an oversized field gets a heading of its own after the body rather than crowding the top.
• A document that cannot be read is still listed, with the reason shown in the pane rather than raised as a dialog.
• The text column is held to a readable line length, so a wide window gives margins rather than longer lines.
• The page reads itself gently down and hands control straight back the moment you scroll.

Reading it your way

• Light and dark, switched from the tray and remembered between runs.
• Three text sizes, stepped by one button that always shows the size it would move to.
• Changing either keeps your place: you stay on the words you were reading rather than being thrown to the top.
• Full keyboard navigation, as one explicit ring that wraps at both ends.

Editing, elsewhere

• Open the selected document in the editor you choose; on Windows one is already picked for you.
• The control stays disabled until there is genuinely something to do: a document selected, an editor chosen and that editor still where you left it.
• Come back to the window and the library is re-read, so an edit made outside shows up without a refresh button.
• It never writes to a document itself, which a structural test enforces rather than leaving to discipline.

Finding out how it works

• A guide sits first on the Help menu. It names every picture in the two trays with the icon itself rather than with a description of it, so a control you have just met can be identified rather than guessed at.
• Then it says the one thing no screen can state while it is happening: what each of the five kinds of document becomes on the way to the pane.
• Everything a control can say for itself is left to the control, so every button carries its own tooltip and the guide stays short enough to finish.

Staying current

• Asks GitHub whether a newer release exists, a few seconds after opening and once a day after that.
• It speaks only when there is something to download. Ask from the Help menu and it answers either way.
• Skip a release and it is never mentioned again; the next one still reaches you.
• That is the only request it makes of its own accord; nothing about you goes with it.