u/No-Budget-3869

I’ve been experimenting with Codex + GPT-5.5 by pushing it into a pretty uncomfortable task: a code-only 3D Threejs forest ravine demo.

No downloaded art pack, no scanned assets, no WebGL fallback. The goal was to see how far I could get with procedural geometry, generated materials, Three WebGPU, TypeScript, and a lot of iterative visual feedback.

The interesting part wasn’t that Codex “one-shotted” it. It definitely did not. The useful workflow was more like:

1. Ask for a fast vertical slice first.
2. Keep the scope visible and runnable.
3. Give visual criticism after each iteration.
4. Use very specific resets when something looked wrong.

My takeaway: Codex is extremely strong when you treat it less like a magic prompt box and more like a persistent engineering partner.

Here is the public demo & source code: github

Hey r/chrome_extensions,

I recently published Comic Theme For X, a Chrome extension that gives X/Twitter a comic-book visual layer.

I built it because the X/Twitter timeline can feel like a dense wall of posts. I wanted browsing to feel more visual, easier to scan, and a bit more fun without changing the actual content or core behavior of the site.

The extension adds comic-style panel framing, speech-bubble styling, ink-like borders, and adjustable visual intensity. The default goal is to give the timeline more personality while still keeping it readable.

I also tried to keep the trust side simple:

• No backend
• No network requests
• No tweet or account data collection
• Only visual preferences are stored locally

It only runs on x.com and twitter.com.

Chrome Web Store: link-here

I’d really like feedback on three things:

1. Does the comic style feel fun, or does it become distracting?
2. Should the default intensity be even more subtle?
3. Any advice for keeping this kind of styling stable on X/Twitter’s dynamic SPA layout?