dev-setup-temp-resource

name

dev-setup-temp-resource

description

Set up and use the committed `_temp-resource/<issue>-<topic>/` convention for handing scratch resources (prototypes, design references, fixtures, sample data) from one Claude Code session to a LATER session through git — not Dropbox/cclogs. Use when: (1) setting up `_temp-resource/` in a repo, (2) a planning or dev session must delegate files a later session will need — especially `/big-plan` → `/x-wt-teams`, or any handoff to Claude Code web where Dropbox/cclogs is unavailable, (3) deciding where to put prototype output (e.g. from `/prototype-first-wisdom`) that you've decided a downstream session should reuse, (4) reading resources a prior session left under `_temp-resource/`. Keywords: _temp-resource, temp resource, delegate resources, share prototype across sessions, web Claude Code handoff, "use this PR as base".

Dev Setup: Temp Resource

A repo-committed handoff channel for scratch resources that one session produces and a later session consumes. Git is the channel — so it works where Dropbox/cclogs does not (most importantly Claude Code web, which has no Dropbox).

The convention

• Location: _temp-resource/ at the repo root, committed (NOT gitignored). Being in git is the whole point — the resources ride the branch/PR to whatever machine or web session picks the work up.
• Per topic: _temp-resource/<issue-number>-<topic-slug>/, e.g. _temp-resource/4444-tweak-header/. The number is the GitHub issue — the epic for /big-plan, the single issue for /x-as-pr.
• Temporary: delete the topic subdir when the delegated work merges, so it never reaches the default branch. Harmless if left (tooling ignores the dir), but prefer clean.

When to use it — and when not

Use it only when delegating to a later session AND the resource is not already in the repo and is too big/binary to express inline in the issue (a prototype, a design mockup + screenshots, test fixtures, sample data).