Any game (apps/porthole). Use when adding, changing, or regenerating game art -- Pets Club's dog poses, size variants and icons, or Biscuit's scenes and discovery illustrations. Covers regenerating each game's generated headers, reviewing the output, and what…
Any game (apps/porthole/games/<game>/). Use when adding or changing a player-visible mechanic, screen, reward, progression rule, or persisted state. Covers stating the feature contract before editing, the failing-test-first workflow, and the proof list before…
Any game (apps/porthole). Use before calling any gameplay or UI change done. Runs the playtest suite (`make -C apps/porthole playtest`), explains how to read apps/porthole/build/playtest/report.md and its FAIL/WARN severities, and says when to escalate to the…
Any game (apps/porthole/games/<game>/). Use when writing or revising content -- Pets Club stories and spelling words, or Biscuit stories, discoveries, daily adventures and words. Covers each game's content gate (both pixel-fit), the claim ledger for factual…
Any game (apps/porthole). Use when you need screenshot evidence of a screen or flow, or a quick ad hoc UI audit outside the formal playtest suite. Covers writing a raw snapshot script, running it, building a contact sheet, and reviewing it.
Any game (apps/porthole). Use when building, flashing, or bringing up Porthole firmware on the physical Waveshare board. Covers the exact build/upload/serial sequence, the PlatformIO-venv Python-dependency caveat, and how to set the clock.
Create, revise, and visually verify an IKEA-style mechanical assembly manual from HTML or similar source and annotated PDFs, with executable steps, clear diagrams, and traceable comment resolution.
Reconcile a commercial-parts bill of materials with Fusion interfaces, as-built parts, fasteners, spacers, kits, quantities, thread engagement, and fabrication or procurement status.