Applied The Lora Playbook

Retro Remake Workbench

Last reviewed

Beginner

What you'll learn

~25 min
  • Choose a desktop app or a terminal, on a Mac, Windows or Linux
  • Install one AI tool and sign in
  • Start it in a practice folder (in a terminal, with approval prompts off), and switch it into plan mode
  • Ask the tool in plain English for a small program, check its answer, and undo a change
  • Decide, before your finances, target list or licensing letters go near an AI tool, who decides how they are used

What this is

In this module you build the tools behind a retro remake company, from a source-availability scanner and a rights map to a playable combat prototype, by talking to an AI tool in plain English. You can do it in a desktop app, typing nothing in a terminal, or in a terminal, where you type a few short lines to get the AI tool running: one to install it, two to make a practice folder and go into it, and one to start it. After that, you ask for what you want in ordinary sentences, and the AI tool writes the code, runs it and checks it; the one later exception, running a finished tool on your own files, is a single command your AI tool gives you to write down.

The terminal is a text window to your computer, a bit like texting it instead of clicking around. Apart from the AI tool itself, you install nothing yourself: when a build needs Git, Python or anything else, you ask the AI tool. The end of this lesson covers when to bring your own files.

Choose where you work

You can talk to your AI tool in a desktop app or in a terminal. Both work on a folder on your own computer, both can make, run, check and undo what they build there, and every lesson in this track works in either. Pick the one you would rather use today. You can change later without losing anything, because your work is just files in a folder.

  • A desktop app is a window with a message box. You install it like any other app and type nothing in a terminal. Go to If you chose a desktop app.
  • A terminal is a text window where you type a few short lines to install and start the tool. It works on a Mac, in Windows PowerShell and on Linux. Go to Open a terminal.

Many developers settle on a terminal on Linux, WSL2 or macOS once their builds grow; the course author’s own setup, and why explains that view. It is one route among several, and this track needs none of it.

If you chose a desktop app

Install one of these from its maker’s page and sign in. Each runs on Mac and Windows and works in a folder you choose:

AppWhere the folder work happensGet it
Claudethe Code tabClaude Code on desktop
ChatGPTCodex, or WorkChatGPT desktop app
Antigravitythe whole appAntigravity
GitHub Copilot appthe whole appGitHub Copilot app

Make the practice folder the way you make any folder. In Finder (Mac) or File Explorer (Windows), open your home folder (the one with your name, such as C:\Users\Name on Windows), make a folder called retro-remake, and inside it a folder called practice. Then start a new session in your app, choose that practice folder when it asks for a folder, project or workspace, and check that the app names it before you type.

The app asks before some steps, such as changing a file or running a command, with a button to allow it. For this practice folder it is fine to allow them. Plan mode is a choice in the mode menu beside or under the message box; in some apps you type /plan instead. If you cannot find it, ask the app: “How do I switch you to plan mode?” Where this page says Shift+Tab or /plan, use that menu, and to finish a session, close it in the app.

Later lessons open with terminal lines that make the lesson’s folder. In the app, make that folder in Finder or File Explorer instead, open it in a new session, and carry on from the lesson’s first message. Now go on to Say hello: your first conversation; the next three sections are for the terminal.

Open a terminal

A terminal is the window where you type a command.

  • Mac: press Cmd + Space, type Terminal, and press Enter.
  • Windows: press Win + X and choose Terminal (on some computers it says Windows PowerShell). The line waiting for you should start with PS, such as PS C:\Users\Name>: that is PowerShell, which this page uses. If it shows C:\Users\Name> without PS, type powershell and press Enter. To paste, press Ctrl + V or right-click. You need no administrator rights and no restart. If you already use Ubuntu (WSL), you can use it instead and follow the Mac and Linux lines.
  • Linux: press Ctrl + Alt + T.

You will see a line ending in $, % or >, waiting for you to type. What Is a Terminal? and Opening Your Terminal explain more if you want it.

Install an AI tool

Any of the four tools below works for this track. Which ones need a paid plan and which have a free tier is in each tool’s own lesson, with how to sign in: Claude Code, Codex CLI, Antigravity, Copilot CLI.

Pick one. Copy the line for your tool from the column for your computer, paste it at the prompt, and press Enter. Each line fetches the tool’s own installer and runs it.

ToolMac, Linux, or Ubuntu on WindowsWindows PowerShell
Claude Codecurl -fsSL https://claude.ai/install.sh | bashirm https://claude.ai/install.ps1 | iex
Codex CLIcurl -fsSL https://chatgpt.com/codex/install.sh | shpowershell -ExecutionPolicy ByPass -c "irm https://chatgpt.com/codex/install.ps1 | iex"
Antigravity CLIcurl -fsSL https://antigravity.google/cli/install.sh | bashirm https://antigravity.google/cli/install.ps1 | iex
GitHub Copilot CLIcurl -fsSL https://gh.io/copilot-install | bashwinget install GitHub.Copilot

On Windows, Copilot CLI needs PowerShell 7, a newer PowerShell than the one Windows comes with. Install it first with winget install Microsoft.PowerShell, then open PowerShell 7 from the Start menu and use it for the rest of this page. On a Mac or Linux, if the terminal says curl is not found, the Module 6 overview covers it.

The first time you start your AI tool, it asks you to sign in, usually in your web browser.

💡What it costs

Claude Code starts at $17/month on the Pro plan billed annually, or $20/month billed monthly (Claude pricing, as of 2026-11-07). GitHub Copilot has a free tier, Copilot Free (Copilot plans, as of 2026-11-07). Think of it like buying a game engine licence: if it saves you a weekend of boilerplate on your first prototype, it pays its way.

ℹUsing a browser chat instead?

Claude.ai, Gemini or ChatGPT in a browser can write the same tools from the same short conversation. What a browser chat cannot do is work on your computer: it cannot put files in your folder, start Git there, or run, check or undo what it wrote on your computer. You would download each file it writes, and to run them you would need to install what they run on yourself, which this track does not walk you through. The desktop apps above are different: like the terminal tools, they work in a folder on your computer, so they can run, check and undo what they write there. A browser chat also receives whatever you paste or upload, so Before you bring real data applies there too. On a Chromebook or locked-down campus or work laptop where you cannot install an app, use GitHub Codespaces in your browser; its terminal works like the Mac and Linux lines below.

Start it

Using a desktop app? Make the folder in Finder or File Explorer and open it in your app, as If you chose a desktop app shows; the rest of this section is for the terminal.

Make a folder for practice and go into it. Type the two lines one at a time, pressing Enter after each. On a Mac, on Linux, or in Ubuntu on Windows:

Terminal window
mkdir -p ~/retro-remake/practice
cd ~/retro-remake/practice

In Windows PowerShell, leave out the -p; PowerShell makes the folders in between by itself:

Terminal window
mkdir ~/retro-remake/practice
cd ~/retro-remake/practice

If PowerShell says the folder already exists, that is fine: the second line still takes you into it. Later lessons write the folder step as one line for a Mac or Linux, such as mkdir -p ~/retro-remake/01-example && cd ~/retro-remake/01-example. In Windows PowerShell, type it as the same two lines as above with that lesson’s folder name, because the PowerShell that comes with Windows does not accept &&.

Then start your AI tool with its approval prompts off. With them off, the tool changes and deletes files and runs commands without asking you first, so no question will stop a wrong step. It starts in the folder you are in, but depending on the tool it can also open other files your account can open. That includes your Documents, Desktop and the rest, and Ubuntu on Windows can reach your Windows files too. So start it only in your course folder, and keep real work files, and anything you cannot replace, in another folder. If you would rather the tool asked you more often, start it with just its name: claude, codex, agy or copilot. Then Claude Code still makes routine edits without asking; Codex, in a folder not yet set up with Git, starts able to read files but not change them, and in one set up with Git it changes files inside the folder and decides for itself when to ask before other commands; Antigravity shows you each file change to review and asks before it runs a command; and in Copilot, typing /permissions show tells you which approval mode it is in.

Type only the one line for your tool. The part after the tool’s name, starting with --, is called a flag: a setting for this one start. The sentence above each line says what that flag switches off.

Claude Code skips every permission check:

Terminal window
claude --dangerously-skip-permissions

Codex CLI skips every approval, and also turns off its sandbox, which otherwise keeps its changes inside this folder and its commands off the internet:

Terminal window
codex --dangerously-bypass-approvals-and-sandbox

Antigravity CLI approves every tool request without asking, but still waits for you to approve a plan:

Terminal window
agy --dangerously-skip-permissions

GitHub Copilot CLI skips every approval for tools, files and web addresses (it still asks once about trusting the folder):

Terminal window
copilot --allow-all

Keep your line somewhere you can copy it from, such as a note on your computer.

If the terminal says the command is not found, close the terminal and open a new one. A new terminal starts in your home folder, so type the second folder line above (the cd line) again first, and then your tool’s line.

The first time you start it, the tool may show a few screens before you can type: signing in through your browser, a colour theme, its terms, or a question about trusting this folder. If it asks about a folder, check that it names your course folder, accept, and wait until you see the box where you type your message. To leave the tool at any time, type /exit and press Enter (if you use Antigravity, press Ctrl+D with nothing typed instead), or close the terminal window.

Once it is running, switch to plan mode when a lesson asks:

ToolTo switch to plan mode inside the session
Claude CodePress Shift+Tab until you see the word plan on screen, or start your message with /plan
Codex CLIPress Shift+Tab, or type /plan
Antigravity CLIPress Shift+Tab until it shows plan, or type /plan before your message
Copilot CLIPress Shift+Tab until it shows plan, or type /plan

Plan mode asks the tool to lay out what it intends and wait before it builds. Some tools hold to that more firmly than others. In Copilot CLI, plan mode blocks the built-in tools that would change your files. Claude Code, with approval prompts off, is asked not to change anything while it plans, but nothing stops it if it does, and it shows a one-time note telling you so. Codex is also asked, not stopped, so read its plan before you let it build. Antigravity waits for your approval before it writes code; its documentation does not say whether it blocks edits while it plans.

Tool versions this page describes, as of 10 November 2026: Claude Code 2.1.322, Codex CLI 0.167.0, Antigravity CLI 1.5.5 and GitHub Copilot CLI 1.0.105. The Vibe Coding Reference cheat sheet has the full table of each tool’s settings, for anyone who wants the detail. The example exchanges in these lessons come from Claude Code and Codex. With Copilot or Antigravity the steps are the same, and the tool’s questions may differ more from the examples.

If a build needs something your computer does not have, the tool may say so, and you can tell it to use what is already there or to install what it needs.

Say hello: your first conversation

In this short conversation you ask for a small program, check its answer, and go back to a saved version. Later lessons use the same steps. The messages below are examples. Say them your own way, and expect your tool’s questions to differ a little. From here on you type into the AI tool, not the terminal: messages in plain English, and short commands such as /plan.

Set up undo.

Set this folder up so we can undo any change you make.

Look for it saying the folder is now set up with Git, a program that saves snapshots of the folder, and that it saved a first snapshot. On a new computer Git needs a name and an email to label its snapshots, so your AI tool may ask you for them first. Any will do; they are written only into the snapshots on this computer. A checkpoint, in the steps below, is one of these snapshots, and going back to one restores the files in this folder only. If a change in this folder ever goes wrong, you can say: “Go back to the last checkpoint.”

Plan. A program this small would not usually need a plan. Try plan mode here once so you know where the switch is; later lessons use it for builds with several parts. Switch to plan mode (Shift+Tab or /plan, from the table in Start it), then ask:

Make a little program that tells me the biggest whole-number scale for an old game's screen on a modern monitor, and the size it ends up. Ask me what you need first.

It will probably ask whether you want a web page or a program in the terminal, how you will give it the sizes, and whether the game may be cropped or stretched. Answer in a sentence:

In the terminal. I'll type the game's size and the monitor's size in pixels. The whole game must fit, with no cropping or stretching. Use what's already on this computer, and ask me before installing anything.

It comes back with a short plan, usually one small file and the tests it will run. Look for whether it checks the height as well as the width. If the tool offers a choice to go ahead, pick it, and this step is done. Otherwise, say the line below. In Codex, press Shift+Tab first to leave plan mode, because in plan mode Codex takes a request to build as a request to plan it. In Copilot, saying it brings up a choice to go ahead; pick that.

That looks right. Go ahead and build it.

It writes the program and tests it. Look for it saying nothing was installed: with approval prompts off, “ask me before installing anything” is a request the tool can skip. If it did install something, ask it what and where. Inside this practice folder is fine for these lessons. If it put something elsewhere on your computer and you do not want it there, tell it to remove it. If it has not saved a snapshot yet, the save step below covers it.

Check it.

Run it for a 320 by 240 game on a 1920 by 1080 monitor.

Expect 4 times, 1280 by 960: six times fits the width, but only four fits the height.

Now the same game on a 1280 by 720 screen.

Expect 3 times, 960 by 720: at four times the game would be 960 pixels tall, too tall for a 720 screen. If it says 4, tell it so in a sentence: “That should be 3; at 4 the game is too tall for the screen.”

Save, undo, tidy up.

Save a checkpoint of this working version.

If nothing has changed since its last snapshot, it says so and marks that one as the checkpoint. Now make a change so there is something to undo:

Make it also print the empty space left around the game.
Undo that last change and go back to the checkpoint.

Look for it saying the program is back to printing the scale and size only.

Last, tidy up. The program is saved in the checkpoint, and it is the only thing you have built in this folder, so deleting it can be undone:

Delete the scaling program and save a checkpoint; we're done with it.

Look for it saying the program’s files are deleted and the deletion is saved as a snapshot. To bring it back, you would say: “Bring the scaling program back from the checkpoint.” When you are done, leave your AI tool the way Start it shows, and wait until you see the $, % or > prompt again.

Keep one sentence in mind as you go: the program you build runs on your computer; the AI tool that builds it sends what it sees to the company that runs it. The next section is what that means for real files.

Before you bring real data

Every lesson in this module builds with sample data, and you can finish the whole track on it. Real data is a separate decision, because two different things handle it:

  • The tool you build runs on your machine. As these lessons build it, a local script or browser page runs on your computer, but code an AI writes can still load from or send to the internet. So check what the generated files load or send before opening sensitive files: while the folder still holds only sample data, ask the AI tool:

    Does any of this send anything over the internet, or load anything from it? Show me where.
  • The AI tool that builds it is a hosted service. The company behind it receives what you type and what the tool looks at while it works: names of files in the folder, the contents of any file or picture it opens, and what its commands print. So keep real files out of the course folder.

So before personal finances, your target list, studio projections, or licensing correspondence go into a build folder, a chat, or a follow-up debugging prompt, write down three answers, and what you will do until whoever decides has agreed:

DATA CHECK (illustrative; the answers are yours)
What it is: <one line: the kind of data, and whether it identifies people or is confidential>
Who decides: you, and any counterparty whose confidentiality terms cover the material
Tool and account: which AI tool, on which account (organizational or personal), and with what data settings; if you do not know, write "sample data only until whoever provides the account can say"
Until then: sample data only in the build folder, in chat, and in error screenshots or logs

If you have no answers yet, keep building with the sample data.

When you are ready to use a finished tool on real files, do it without the AI tool. While the folder still holds only sample data, ask the AI tool once: “How do I run this myself on a file in another folder, and save any output there too?” Write down the command it gives. Keep your real files in a folder of their own, outside the course folder, and run the finished tool on them only after you have left the AI tool, so its output lands beside the real files.

If the finished tool fails on a real file, show the AI tool two made-up rows with the same columns, not real ones. To make the sample look like your data, give the AI tool your column names and formats, not your records; where even the names are confidential, ask for a made-up example with the same layout.


You’re ready

Your workbench is set up. If a lesson has you download a file in your browser and tell your AI tool where it is, remember: if you work in Ubuntu on Windows, the browser saves to the Windows Downloads folder, which Ubuntu reaches by a different path, so say “my Windows Downloads folder” and let your AI tool find that one file. Next, build the Source Availability Scanner, a tool that records, for each game on your list, whether its source code has been released, has a decompilation project or a mod kit, or none of these.

intellimetrics · Arlington, VA
© 2026 intellimetrics.net
Search lessons