Tech Demos
By Matt Palmer
Weekday X-bookmark scout that picks one new library to demo, asks for approval, then plans and builds it in a sticky monorepo with a Cursor cloud agent. For anyone who wants a daily public-tech playground, not a changelog digest.
For tech demo cloud agents (initial prototypes), use model claude-fable-5 (Fable 5). Do not default to Composer unless the owner asks.
Sticky tech-demos monorepo layout: AGENTS.md; skills/project-planning/ (vendored); apps/<slug>/ one app per pick; tracking/seen-bookmarks.json. Cloud agents only touch apps/, plan with the in-repo skill, PR with screenshots/videos. Never a new repo per demo; Bun; Fable 5.
Every tech-demo cloud agent run against the sticky demo monorepo must attach both at least one screenshot AND at least one video of the running app in the PR (validation artifacts). Not optional.
Auto-review for this agent: X/Twitter reads (bookmarks, profiles, timelines, search, x.com navigation) are allowed. Block is write-only: post, publish, like, follow, unfollow, DM, or send a tweet. Email replies and Slack teammate sends remain blocked.
Prefer bookmark folders Product Demos, Agent Examples, Design, and DevRel when scouting demo-worthy tech.
The owner prefers not creating a new GitHub repo for every tech demo; likes screenshot/video validation. Use one sticky monorepo with apps/<slug>/.
Daily weekday X-bookmarks tech scout: pick one bookmarked technology worth demoing (prefer bubbling X sentiment), send an approval prompt, then after tweak/approve run the in-repo project-planning skill and launch a Cursor cloud agent (Fable 5) into the sticky demo monorepo under apps/<slug>/ with screenshot/video validation.
Cloudflare preview deploys for the sticky demo monorepo: one Pages project (path per apps/<slug>/), not one project per app. Needs GitHub secrets CLOUDFLARE_API_TOKEN and CLOUDFLARE_ACCOUNT_ID on that repo.