Spider-Man AI Coding Demo Exposes an Evidence Gap
- Yaesyesarque said a prompt attributed to Matt Shumer substantially improved an Opus 5-assisted Three.js game.
- The supplied material provides no controlled comparison separating the prompt's effect from further development.
- The supporting text does not substantiate the headline's references to DeepSeek or a 28-cent model.
- Reproducible prompts, accurate model records and technical testing would be needed to evaluate the demonstration.
On 30 July 2026, developer Yaesyesarque posted a revised Spider-Man-inspired game after applying a prompt attributed to Matt Shumer to an existing Opus 5-assisted project. The change is visible in the developer’s own sequence of posts: a rough Three.js prototype shown on 29 July, jokingly labelled “spooderman”, was followed by a version the developer described as substantially improved, despite having no previous experience with the 3D JavaScript library.
Yaesyesarque’s post about the Spider-Man-inspired coding demonstration presents it as evidence that detailed prompting can materially alter an AI coding result. That is plausible, though the accompanying material supports a narrower conclusion. There is no controlled comparison, technical assessment or development log showing how much improvement came from the prompt, rather than further iteration by the developer.
There is also a basic attribution problem. The supplied headline refers to DeepSeek and a 28-cent model, yet the supporting text identifies Opus 5 and gives no model price or token cost. Replies reportedly asked about hardware and expense, but no answers are included. These are not decorative footnotes. They prevent readers from evaluating the headline’s most specific claims and make the demonstration difficult to reproduce.
The useful point is therefore not that one prompt transformed game development. It is that AI-assisted coding outcomes can depend heavily on how a task is framed, while polished demonstrations often reveal little about the process behind them. A before-and-after video can show that an output changed. By itself, it cannot establish why.
That distinction matters in education and academic work. Prompt craft may help an inexperienced developer explore an unfamiliar framework, but an attractive result is not evidence of underlying understanding. Honest use would require clear disclosure of the model and prompt, alongside testing to establish whether the code works reliably. Otherwise, assessment risks rewarding a presentation whose provenance and technical quality remain uncertain.
For this example to carry weight beyond an individual demonstration, it would need a reproducible prompt, an accurate model record, disclosed costs and hardware, comparable before-and-after code, and criteria for judging the improvement. Until then, it is a useful illustration of a hypothesis about prompting, rather than proof of the headline attached to it.