AI Agent Use Cases

Added today

44All 189

Prompt to Prepare a Shopping Cart from a Recipe Photo

The author reports that Grok Bot receives a recipe photo, organizes the ingredients and quantities, and creates a shopping list by excluding ingredients already available at home.

Grok Bot
Life & Hobbies

1–20 of 189

Life & Hobbies

Running a 1997 Game Again on a Modern PC

They used Claude Code to fix the runtime environment for an old DirectX game. Afterwards, they examined the internal structure and created strategy materials.

How it works

  1. They tasked Claude Code with running a 1997 PC game on modern hardware. According to the author, it took 30 minutes to reach the first successful run, during which a basic reverse engineering environment was also set up.
  2. They repeatedly examined various parts of the game to analyze the internal code. When screen handling interfered with PC use, they extended a DLL that connects to DirectX as an intermediary and used Windows' Private Desktop feature to run the game without displaying the screen.
  3. By running multiple game instances at the same time, they found related memory addresses and game logic scripts. They combined scenario file edits, level data modifications, and memory manipulation to move to the required scenes.
  4. The author used the created auxiliary tools to check the game structure and the results of changes, which helped guide their direction. Later, Claude Code wrote a level walkthrough including screenshots of key scenes.

Results

The user managed to run the game and create a walkthrough. Work to improve the display was still ongoing.

Notes

This is a brief comment introducing the process. The game name, launch commands, and DLL modification code were not disclosed. The user set the direction and checked results during the work, so it was not a fully automated process without human involvement.

Source

Hacker News Original post ↗

Example prompt · Claude Code

Please find and fix the reason why my old PC game does not run on my current computer.

Input: Game file [path], runtime environment [OS·graphics], error message [log], expected screen when working [reference]. Start from a working copy of the original files and first reproduce the failure to run.

Check the logs and used libraries to determine whether the issue is with the OS, display output, or input handling. If you need to change compatibility settings or the graphics connection, explain the reasons and effects before making small changes. Do not guess game-specific addresses or patches that are not disclosed in the original material.

Create run scripts and observation tools needed for repeated testing, and save the result screens and logs after each change. If you add automation, first confirm that a run environment that does not interfere with my work screen is actually possible.

Deliverables: How to modify and run, changed files, steps to revert, and test results. Test available features such as the start screen, new game, input, save/load, and report separately on successful runs and overall game compatibility.