memory-palacelisted

Reproducible kit for mounting Henry Heffernan's 3D-CRT-monitor + Win98-desktop portfolio template (`/palace`) on top of an existing Next.js site. Ships drop-in build scripts, config snippets (webpack / Next / Vercel / tsconfig), placeholder showcase pages, NOTICE templates, a post-deploy DevTools verification snippet, and the 13-gotcha PLAYBOOK that catalogues every way this rollout breaks in production. Use when the user wants a /palace-style 3D portfolio with a clickable retro monitor mounted on their own site, when integrating a vendored CRA app inside a Next.js host, or when debugging "same-origin iframe but Chrome treats it as cross-origin", iframe stuck on broken-document, framer-motion type drift on Vercel, COOP/X-Frame-Options blocking own-iframe, or font fallback inside the inner OS.
bingran-you/bingran-you · ★ 2 · Code & Development · score 73

Install: claude install-skill bingran-you/bingran-you

# Memory Palace — copy-paste kit + production playbook **Live demo:** [bingranyou.com/palace](https://bingranyou.com/palace) — what you're aiming for. **Sibling skill:** [`win98-paper-theme`](../win98-paper-theme/SKILL.md) makes the *rest* of your site (front door, blog, every other route) speak the same OS dialect as `/palace`, so the hand-off between the 3D scene and the docs / posts feels like the same machine. Ship that one after this one if you want full visual cohesion. ## What this skill ships A complete, copy-paste-ready kit for cloning [henryjeff/portfolio-website](https://github.com/henryjeff/portfolio-website) (the outer 3D CRT room) + [henryjeff/portfolio-inner-site](https://github.com/henryjeff/portfolio-inner-site) (the inner Win98 desktop) and mounting them under `/palace` on your own Next.js site, with your own content. Two layers: 1. **Mechanical scaffolding** — drop-in build script, config snippets, placeholder content, NOTICE templates. Live under `assets/`. See `assets/INDEX.md` for the full map. 2. **Production knowledge** — 13 gotchas that each cost hours to debug if you don't know them coming. Live in `PLAYBOOK.md`. The mechanical part is mechanical. The reason this skill exists is the 13 gotchas. **Read `PLAYBOOK.md` before deploying.** Skipping it means you'll find them yourself. ## When to use - A user wants a 3D retro portfolio with a clickable CRT monitor (like henryheffernan.com) - A user is mounting any vendored CRA / webpack app inside