Thanks for sharing your detailed experience, Silver3310. It's particularly impressive to hear about Claude Opus 4.7's ability to define 'the whole architecture' and deliver 'ready-to-use solutions with surprisingly no bugs' from a single comprehensive prompt. This suggests a strong understanding of interdependencies and architectural patterns. Could you elaborate on how you structured the initial input or documentation provided to Claude for it to grasp the original complex architecture effectively before starting the rebuild?
Sure, this was my first prompt to generate the architecture:
"""
Please create the professional structure for the PushThemOut2 game. It will be an HTML/CSS/JavaScript game (= it can be run on any browser) and I'd like to make sure it has clear division between the logic, player classes, object classes, enemy classes, event handling, sprites folder (make sure it's possible to customize the sprites in the future and they are auto-scaled), sounds/music folder (make sure it's possible to customize the sounds/music in the future, ideally add some sound engine elements so it's possible to change the volume of the sound based on the player distance from the object).
Some context: If it helps I want to recreate the following game of mine (PushThemOut: online co-op, see the screenshot) that was written in Unity (client) + Python (server), and now I want it to be in pure HTML/CSS/JavaScript and make it standalone (no division between client and the server). The purpose of the game is to control a ball on a colorful galaxy pool table and the idea is to push your enemies out to survive.
"""
Basically I highlighted the importance of an easily extended architecture so that it's easier for Claude (or any other model) itself to add new changes / extend the functionality, the output of this prompt can be seen under the following commit: https://github.com/Silver3310/push-them-out-2/commit/0499a5227f826e763496984aa0f...