prism openai implementation guide
No fluff — just the commands that work on macOS to download a live site, prep Codex context, and run the rebuild locally so you can ship updates fast.
start here
Every step keeps your local rebuild simple: download the current experience, extract the words that convert, and hand Codex a clean brief so the regenerated build matches what's live today.
goal
step 1
Keep everything in one spot so assets, text files, and Codex context stay organized.
cd ~/Desktop
mkdir site-rebuild && cd site-rebuildstep 2
Use wget to grab every reachable page and its assets directly to disk.
Install wget (if needed):
brew install wgetDownload the live site:
The command below updates automatically with the URL you enter.
wget -r -l inf -p -E -k -nc https://example.comFlags in plain English:
.html extensions so files open cleanly.Expected structure:
site-rebuild/
├── example.com/
│ ├── index.html
│ ├── about/
│ ├── images/
│ └── ...step 3
Optional, but it helps Codex keep every headline and paragraph accurate.
Install ripgrep:
brew install ripgrepExtract headings and paragraphs:
rg -o '<p>.*?</p>|<h[1-6]>.*?</h[1-6]>' ./example.com > all_text_raw.htmlStrip the HTML tags:
sed -E 's/<[^>]+>//g' all_text_raw.html > all_text_raw.txtResult: a clean all_text_raw.txt file ready for Codex context.
step 4
A live sitemap.xml gives Codex a definitive page list.
curl -O https://example.com/sitemap.xmlstep 5
Codex reads context from the .codex directory — keep instructions and source text here.
mkdir .codexAdd project instructions:
echo "Website rebuild project for https://example.com
- Use Next.js + Tailwind
- Keep copy identical to original
- Modernize layout only" > .codex/instructions.mdCopy extracted text for Codex:
cp all_text_raw.txt .codex/current-site.mdstep 6
With context in place, let Codex generate the rebuild in a fresh Next.js project.
Export your OpenAI key first:
export OPENAI_API_KEY="your_api_key_here"Ask Codex for the rebuild:
codex ask "Rebuild this website locally with the same text and structure using Next.js and Tailwind." \
--with .codex/instructions.md .codex/current-site.mdCodex writes directly into the current folder — expect directories like pages/, components/, and public/.
step 7
Run the usual Next.js dev workflow and confirm the copy, layout, and routes match the original.
pnpm install
pnpm devVisit the local build:
http://localhost:3000reference
Keep this snapshot intact — it's the fastest way to iterate on the rebuild, hand assets to teammates, or version control the work.
site-rebuild/
├── example.com/ ← downloaded site
├── all_text_raw.txt ← readable copy for Codex
├── sitemap.xml ← structure map (optional)
├── .codex/
│ ├── instructions.md
│ └── current-site.md
├── package.json ← generated by Codex
├── pages/
├── components/
└── public/wrap up
You now have a local mirror of the live site, Codex-ready context, and a running Next.js build on localhost. From here, you can modernize the design, iterate on copy, or push the rebuild into your repo.
next experiment
We ran the Model Test Key from this guide through GPT-5.1 Codex (High) and documented the full run: generation time, UI polish, responsive behavior, sitemap completeness, and the live video breakdown.