Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›Web›Web — QR management·15 in this wave

Approve: QR managementTo do · blocker BUG: dynamic-QR detection hardcodes tactile.to, so white-label codes render the wrong symbolDone SPEC → backend: move QR render glue into the package, and make program_mode first-classTo do Build the desktop QR creation/design studioTo do Wire desktop 'Edit Design' to the new QR studioDone Make the desktop QR static/dynamic toggle functionalBlocked Bring QR module/eye shape pickers to the full native set on both web surfacesTo do Add gradient design controls to QR codes on both web surfacesDone Add per-eye frame and inner color controls to QR codes on both web surfacesDone Add interactive logo crop to QR logo embedding on both web surfacesDone Add the decorative shape library to QR codes on both web surfacesTo do Add stickers to QR codes on both web surfacesTo do Add QR readability/scannability grading to both web surfacesDone Add pixel randomizer, background image, and lighting effect to QR codes on both web surfacesTo do Sign off: QR management parityTo do

Wave

Web — QR management

New wave, created 2026-07-26 following Matthew's full-parity decision: 'on web, manage all the destinations and QR codes... do everything except physically encode the NFC.' Today apps/web (desktop) has ZERO QR design capability — TriggerLaunchpadPage.tsx explicitly stubs 'Edit Design' with 'QR Studio lives in the mobile apps for now' (line 278) and its Dynamic/Static toggle is decorative, not functional (lines 303-317). apps/web-mobile has a real but shallow QR editor (QREditorPage.tsx) — close to parity on shape picking (19/23 module shapes, 4/5 frames, 14/14 inners) but missing gradients, per-eye color, decorative shapes (58 unused assets), stickers, logo interactive crop, readability/scannability grading, pixel randomizer, lighting, and background image — all of which the native iOS QR studio (QRGeneratorPage.swift, 8,725 lines) has, and all of which the shared @tactile/qr-renderer engine already supports render-side. This wave brings both web surfaces to native QR-management parity.

TacTile › Launch TacTile › Web › Web — QR management

6/15 done9 open1 open blocker

Selected taskclear

Build the desktop QR creation/design studio

To doOwner · Vivt_e5d57404

Viv — Build a desktop QR creation/design studio on apps/web: content input, dynamic/static mode selection, live SVG preview, save. Done when: a signed-in user can create a new QR code end-to-end on tactile.to without the native app, the save call creates the underlying trigger record, and the new QR appears in Assets identically to one created from web-mobile or native. File: apps/web/features/qr/ (new), apps/web/features/assets/pages/TriggerLaunchpadPage.tsx.

Unlocks 1Approve: QR management

Show the prompt

You are Viv, the agent for the TacTile lane of Command.

Open the lane and work there:

```bash
cd ~/Command/tactile && claude
```

Read that lane's CLAUDE.md and lane.json before you touch anything — they
carry your identity, your scope, and the hazards specific to this lane.
Read state from the hub (https://internal.tactile.to) or ask. Never guess at it.

## The task

**Build the desktop QR creation/design studio** · to do

Viv — Build a desktop QR creation/design studio on apps/web: content input, dynamic/static mode selection, live SVG preview, save. Done when: a signed-in user can create a new QR code end-to-end on tactile.to without the native app, the save call creates the underlying trigger record, and the new QR appears in Assets identically to one created from web-mobile or native. File: apps/web/features/qr/ (new), apps/web/features/assets/pages/TriggerLaunchpadPage.tsx.

Where it sits: TacTile › Launch TacTile › Web › Web — QR management

## Unlocks 1

- Approve: QR management

## How to work this

- Do the work, don't just plan it. If the fix is obvious and safe, make it.
- Surface anything needing Matthew's sign-off instead of deciding it yourself.
- Short replies. Lead with the answer, then stop.
- Finish by saying what changed, what you verified, and what you'd do next.

To doIn progressDoneBlockedPick a wave on the left · tap a task to expand it

Lanes

Web — QR management

Build the desktop QR creation/design studio