# Vercel Labs Integration brainstorm

Pick a stage to see what changes. Click an idea card on the right to load its full detail. The stage toggle composes ideas — each stage assumes the prior one shipped.

The dev loop
7 ideas (A=high, B=medium, C=small)
Selected idea — what shipping it actually means
Is this generic-enough? (your "is it generic good enough" question)
Short answer: #1 (`/ork:dev`) and #6 (memory snapshots) ship as opt-in skills — they only run when invoked, never break a non-Vercel stack. #2 and #3 default-on for any project, but #2 detects whether `agent-browser` is installed and skips silently otherwise; #3 falls back to markdown if `@json-render/mcp` isn't connected. #4 (emulate seed auto-discovery) runs only when it sees Stripe / next-auth / etc. in `package.json` — it's data-driven, not framework-locked. The plan does not assume the user is on Vercel: portless works on any localhost, agent-browser drives any Chrome-based browser, json-render renders to React (any host). The Vercel Labs packages happen to be best-in-class for these jobs; the abstraction is the integration, not the vendor.

### Prompt for Claude