trmnl-paper

Use when the user wants to build, edit, or redesign screens for TRMNL e-paper devices. Handles dashboards, KPI displays, item lists, data tables, quotes, rich text, charts, and any screen layout — converting content briefs, data descriptions, or plain HTML into `<x-trmnl::...>` Blade component markup. Also use when they mention "trmnl-blade", "TRMNL Framework", "e-paper screen", or describe content for an e-ink display, even without naming TRMNL directly.

Use when the user wants to push, deploy, or update screen content on a TRMNL device via a LaraPaper instance. Builds the JSON payload with device credentials (MAC address + device API key) and sends to `/api/screens`. After an actual send, it can read back `image_url` from the current screen endpoint, review the rendered result, and route layout fixes back to `trmnl-paper-blade`. Also use when they say "send to device," "update the display," "deploy this screen," or need to construct the LaraPaper screen update request for already-prepared markup.

Use when the user wants image-first TRMNL screens rendered with Takumi-style JSX and Tailwind instead of assembling everything with `x-trmnl::` components. Best for 800x480 poster-like screens, pixel art, screenshot-like compositions, hero illustrations, or layouts that should be rendered as one image and then wrapped in minimal TRMNL markup. Also use when they mention Takumi, JSX-to-image, Tailwind image rendering, pixelated artwork, or want a rendered WebP/PNG handed off to `trmnl-paper-screen`. Prefer `trmnl-paper-blade` instead for KPI dashboards, item/table/progress-heavy screens, or layouts that should remain structured and locally editable.