s-macke

Then start Claude. From that point on, it’s mostly prompting and evaluating the results. Like any good engineer, you shouldn’t simply start with “Create a video from this comic.” Instead, take a step-by-step approach: discuss the visual style, animations, ask for audio examples, create a script, and then develop a storyboard (ask for a .html document).

The important part is to break the whole generation process down into small, manageable steps. I also used the brainstorming skill from Superpowers for the discussions. It makes the whole process much easier when the AI asks the questions and I just have to answer them.

The result is 4500 line python code generated by Opus 5.5 and a lot of video and audio files.

1. For each topic, write a result Markdown file in `spec/`.

2. Identify the file formats.

3. Reverse Engineer and extract all assets, followed by manual review. This works in 90% of the cases.

4. Determine the compression/packing used for the executable. Most binaries used one of roughly five common executable packers.

5. Unpack the executable manually.

6. Use an ancient free IDA-Pro for disassembly, or a modified DOSBox to determine all code/data blocks and the relevant segment-register values for the 8086 architecture. In the second case I use my vibe-coded disassembler.

7. Identify the major functional domains in the disassembly and split the files accordingly.

   ...

One of the most difficult reverse-engineering projects from that era for me was Stunt Car Racer on the C64 (also ported to DOS). It features a highly optimized 8-bit 3D graphics and physics engine. Fable was the first one that was able to generate a complete port of the game.

Now I am trying of Flight Simulator 4 and Wing Commander 1. Then maybe Frontier Elite 2. So much fun ....