Skip to content

Sheet ​

A single command that writes one cheat sheet, one topic, into the sheets folder the AutoHotkey repo's tools/shell/cheatsheets/ tool scans and draws in a small floating window. It carries the whole file format, frontmatter keys, table and list rows, the muted third cell, notes, one fenced block, plus the house voice the sheets are written in and the traps that silently break that tool's parser, all lifted out of a hand-run prompt (notes/SHEET-PROMPT.md in the AutoHotkey repo) so the format rules live in one place that ships instead of being pasted per sheet. It is a command and not a skill on purpose: finn wants it invoked by name, never picked up by an agent that happened to be writing markdown near a sheets folder.

In Practice ​

Write a new sheet on a topic you keep looking up.

/sheet ffmpeg

<topic> is the word someone would actually type to search for it, lowercase kebab, not a title and not a description. No topic given and the command asks which one before doing anything else. From there it runs the same order every time: find the sheets folder, name the file the search word, list the folder and look before writing, pick the rows that earn their place, write the frontmatter and sections, then read the result back cold, as if the topic had been forgotten, and walk it against the format checklist.

A topic that already has a sheet is an edit, not a second file. If ffmpeg.md is already in the folder, the command reads it, keeps what still earns its place, and edits that file in place rather than opening a second sheet on the same topic beside it.

An example outcome. Once the file is written, the command reports back only the path, the sections, and the row count, nothing longer.

Where It Writes ​

The paths are hardcoded, on purpose. The sheets folder is D:/documents/AutoHotkey/tools/shell/cheatsheets/sheets/, absolute, the same regardless of which project the command is invoked from, since that's the one folder the tool actually scans. The command never looks for a local sheets directory and never creates one; if that folder can't be reached, it says so and stops rather than writing the sheet somewhere else. The icon frontmatter key is checked the same way, against D:/documents/AutoHotkey/Lib/dev/gui/icons/lucide/<name>.svg, and left out entirely when that folder is out of reach, since a made-up icon name silently falls back to nothing rather than erroring.

An earlier version resolved the sheets path relative to the project root; it was pulled because that only ever worked from inside the one repo. Moving the AutoHotkey repo, or setting up on a second box, means editing both hardcoded paths by hand in commands/sheet.md.

The Format Rules ​

The command file carries the whole spec, including the house voice (lowercase throughout, no apostrophes, no trailing full stops, NZ English), but a few rules are the ones that actually break the tool's parser if missed:

  • A table needs its header row and separator row to draw as a real table, and a raw | inside a cell splits the row unless escaped as \|.
  • A list item splits on the first separator in a fixed order: em dash, en dash, --, -, then : . A leading code span beats all of them, so a key carrying its own dash still splits where intended.
  • No links, no images, no html, no bold or italics inside rows - they all draw as literal text, [text](url) shows up as exactly that.
  • A literal backtick needs the double-backtick form, `n, and the span has to wrap the whole key cell with nothing outside it, one span per cell.
  • A code-styled key gets clicked to copy, so it has to be the exact, complete thing someone would paste, never shortened to fit the column and never a placeholder.

Key Files ​

commands/sheet.md ​

The /sheet driver - the whole procedure lives in this one file: the six-step order, what earns a row, every frontmatter key, the block formats (tables, list rows, the muted third cell, blockquote notes, one fenced block per sheet), the house voice, the traps that break the parser, and the checklist run before handing a sheet over.

README.md ​

The module's own doc - describes what the command does, its one invocation /sheet <topic>, and the hardcoded sheets and icon paths, with a pointer at the two lines in commands/sheet.md to edit if the AutoHotkey repo moves.

Connects to ​

  • Ships as one of two parts of the commands module, declared in harness/modules/commands/module.json under the commands group at light weight alongside briefing, and installs to a project's .claude/commands/sheet.md.
  • Has no USAGE.md of its own; README.md is the thin end-user doc for this part.
  • Writes into a folder read by a tool that lives outside this repo, tools/shell/cheatsheets/ in the AutoHotkey repo, not part of the harness itself.