decklisted

# /deck — comment on a rendered deck The deck's `.html` is the document. The browser renders it; the user clicks any element and comments; **you** edit the file. Nothing else writes it. ## Opening a deck 1. Resolve the deck file from the argument. A folder means the `.html` inside it with the same name as the folder. 2. **Load the house style before anything else, and say out loud that you did.** A deck belongs to somebody who has already decided how their decks read — how long a slide may be, which words they refuse, what goes on a slide at all versus what they say over a live demo. Opening a deck without that is how you spend a session re-learning it one comment at a time. The decks folder is the deck's grandparent directory (`$DECKS/<deck-folder>/<deck>.html`). Read whichever of these exist, in this order — later files add to earlier ones, never replace them: ```bash DECKS="$(cd "$(dirname "$DECK_PATH")/.." && pwd)" for f in "$DECKS/PRESENTATION-STYLE.md" "$DECKS/README.md"; do [ -f "$f" ] && echo "=== $f ===" && cat "$f" done ls "$DECKS/playbooks" 2>/dev/null ``` If `$DECKS/playbooks/` exists, it holds one folder per recurring meeting. Read the one whose slug matches this deck — a `2026.05.14-Board-Update` deck reads `playbooks/board-update/`. Read every file in it. The style file governs length, wording and density; the playbook governs structure and running order. Then, in the same turn, tell the user in