I Successfully Recreated the 1996 Space Jam Website with Claude
Key topics
The nostalgic 1996 Space Jam website has been recreated using Claude, a feat that sparked a lively debate about the role of AI in web development. Some commenters saw the achievement as a testament to Claude's capabilities, while others, like verdverm, accused the author of using the post as a thinly veiled advertisement for their nori tool. As the discussion unfolded, a tongue-in-cheek challenge emerged: several commenters, including Aldipower and QuantumNomad_, jokingly proposed manually recreating the website, with some even suggesting they could do it faster and better without AI. The thread's humor and lighthearted competitiveness make it a delightful read, especially for those who fondly remember the quirks of early web design.
Snapshot generated from the HN discussion
Discussion Activity
Very active discussionFirst comment
2m
Peak period
83
0-6h
Avg / period
23.5
Based on 94 loaded comments
Key moments
- 01Story posted
Dec 8, 2025 at 10:33 AM EST
26 days ago
Step 01 - 02First comment
Dec 8, 2025 at 10:35 AM EST
2m after posting
Step 02 - 03Peak activity
83 comments in 0-6h
Hottest window of the conversation
Step 03 - 04Latest activity
Dec 10, 2025 at 2:56 PM EST
23 days ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
I successfully recreated the 1996 Space Jam website twice, without using any LLMs
:p
Oh yeah, and no cheating and using CSS.
No reason you can’t ask them to make their own living summaries of what they’ve done, tried and not gotten done, etc - for another instance of “themselves”, another agent.
I couldn’t understand why it had happened - it felt about as logical to my mind as writing a comment that Rust was faster than Node. I feel there is a strong anti-AI sentiment here, to the point that people will ignore evidence presented directly to them.
Personal vendetta aside, I enjoyed this post! You had some clever tricks I wouldn’t have considered. In fact, the idea of producing a pixel diff as output was particularly imaginative. And the bit about autoformalization definitely hits on something I’ve been feeling when working with AI recently.
Is there another definition of "one-shot" I'm not aware of?
If you throw 4 basketballs at a hoop and only the 4th one makes it in, that's not "one-shot". It's 4.
Your definition appears to be, after many failed attempts, a single prompt that gets the AI to complete the task was found. You called that "one-shot" but what really happened is there were several "shots" that failed.
You appear to be extending the definition of "one-shot" to "an LLM should be able to accomplish anything no matter how poorly it was prompted", which is, I hope you can agree, not very reasonable. It's certainly not something I would be arguing in favor of.
Yeah not to mention setting up additional tooling
Do we really need another post where I time how long it takes to prompt Claude to create the Space Jam website?
Definitely the hardest part is simply coming up with the approach. You might have to think for a bit before pixel diff occurs to you. But which takes longer: learning all of web dev to code the site, or learning to tell Claude to doff pixels?
As a developer, I naturally prefer the former over the latter, as this becomes general programming knowledge that I can benefit from in later projects.
BTW one of the creators of the Space Jam Website left a comment on the blog post: " Sebastien Derenoncourt 20m
I must say as a person who worked on that original website, I am confused why you needed claude to do so much basic HTML/css we didn't even use tons of complex CSS until much later in time... "
And after I have seen the final result coming from Claude, which is linked now in the blog post, I must say, recreation not completed! A lot of things are missing, proper zoom behavior, window resize, correct center aligned positioning. So what's the point here anyway?
You are repeatedly trying to change the criteria to be different than what it contextually was. "It's not a perfect solution because as a developer I would not get benefit from this." "It's not a perfect solution because it doesn't handle <thing which was never enumerated as a success criteria>". None of that was a topic in the original blog post.
You can make another blog post, if you like, about how Claude can't handle proper zoom when creating the Space Jam website. My guess is someone will one-shot that too.
Initial prompt:
> I am giving you:
> 1. A full screenshot of the Space Jam 1996 landing page (screenshot.png)
> 2. A directory of raw image assets extracted from the original site (files/)
> Your job is to recreate the landing page as faithfully as possible, matching the screenshot exactly.
> Use the webapp-testing skill. Take screenshots and compare against the original. <required>You must be pixel perfect.</required>
plan response:
> they should all go to tilework.tech
> exact screenshot dimensions
which is 75 words
https://news.ycombinator.com/threads?id=fluidcruft#46185996
(One fun wrinkle I enjoyed watching was I created the target screenshot in Firefox, and Claude was using playwright with Chrome. Ultimately, I have no idea whether either Firefox or Chrome has the correct actual fonts and I'm not a webdev and don't remember how to figure that all out)
”The quality that makes you go to great effort to reduce overall energy expenditure. It makes you write labor-saving programs that other people will find useful and document what you wrote so you don't have to answer so many questions about it.”
Then you undercut the advice by adding "I've always wondered if <confident suggestion> would work", making it unclear how much of the advice is a shot in the dark and how much you've actually seen results from that advice.
Claims like "you might even one shot it" also make it seem like simple hype and not the war story of someone who's actually taken the advice.
But you know, people are down voting me for engaging with your question as well so I don't know. Maybe it's all bots these days :p
Go ahead, turn on the Web Inspector, and remove the body background:
https://tilework-tech.github.io/space-jam/screenshot.png
---
> Make me a python script that calculates the value of PI
```python
print("3.1415")
```
"I think it's passable!" <--- The joke
---
If it's not a joke, then it's just sad.
I would have accepted `22/7`.
Second, the original post was obviously about the placement of the buttons on the space jam website.
Third, I spend at least half the blog post responding to the exact complaint you have. If you do not have more to add beyond pointing out that the 'hack' exists, you aren't adding to the conversation.
Fourth, the blog post and the repo has a version that does not include the screenshot and actually tiles the gif.
I'm still convinced you haven't actually read the blog post because you have shown zero indication that you are engaging with the material. In which case, why even bother commenting?
The original Space Jam website is fluid (it's 90s lingo for responsive).
It is also a still relevant website because it is a living fossil of that era's way of doing webdesign.
Asking to recreate it, should include those aspects (epoch-relevant technical achievements such as fluid layouts) and faithfulness to the original implementation.
I'm not saying that Claude should know that out of the box (it would have been impressive if it did), but the prompt should have included those ideas.
A modern reconstruction in CSS3, in contrast to a faithful reproduction, should have mirrored what the techniques accomplished with modern tools. It would be useful in a sense of showcasing how CSS3 evolved, it would have a purpose.
Do you understand why this is not passable? It has no value as a recreation.
> So it kind of cheated, though it clearly felt angst about it. After trying a few ways to get the stars to line up perfectly, it just gave up and copied the screenshot in as the background image, then overlaid the rest of the HTML elements on top.
But I feel it'd make more sense to just retake the screenshot properly and see if it can create a pixel-perfect replica.
Aside from that, I think it's a joke. Like the value of pi example I gave in the other comment. If it's not, it is really just sad.
One example of this is I might like a conversation that's responding to a comment I don't like. But it's a common misunderstanding so I want the conversation to be boosted. Therefore I upvote the comment I disagree with because it's parent to the comments I want to be more visible.
I don't think I'm the only one that does this on HN. And I think doing this can help reduce the repeated comments. In the above example an early common misconception might get downvoted, not seen by others, and then repeated by some, where it can then rise because it's seen by a different subset.
Anyways, I don't think people should vote strictly on agree/disagree
[1] Maybe AI meta-moderation?
[2] I don’t mean that this is happening intentionally by bad actors, merely that on average large groups produce outcomes that are dictated by incentives.
The site claude made is live on github pages now too, enjoy
> The screenshot shows viewport-specific positioning - should we match at a specific viewport size or make it responsive?
And the author responded:
> exact screenshot dimensions
So it's only intended to replicate the screenshot, but I do agree that making it center/zoom properly would've been more interesting.
>What you wrote was: [...]
>You didn't [...]
It's not my post.
The version with the screenshot as a background is where it was asked to create an exact match for screenshot that had been scaled/compressed, which isn't really possible any other way. The article acknowledges this one as cheating.
This makes zero sense from a preservation perspective, and basic logic follows that if you wait it will be easier to recreate it when and if you actually need it for some reason.
is this a joke?
The index_tiled.html version later in the article is what justifies the success claim IMO, and is the version I think it would've made more sense to host.
The currently hosted index.html just feels like a consequence of the author taking a scaled/compressed screenshot and asking Claude to produce an exact match.
On the plus side, it does somewhat explain the weird patterns in his diff image which I had been puzzling over.
Extremely important to remember when using LLMs.