Roguelite starship survival ยท squad tactics

Space Game

A public design project combining the route pressure and ship management of Faster Than Light with the persistent crew, research, and lethal tactical missions of the original X-COM.

FTL decides where disaster happens. X-COM decides who survives it.

Strategic Layer

Choose jumps, manage fuel and hull, repair systems, research alien tech, and keep ahead of a spreading galactic threat.

Tactical Layer

Board enemy ships, defend your own corridors, rescue civilians, retrieve artifacts, and survive turn-based firefights under fog of war.

MVP Target

  • One player ship
  • One enemy ship
  • Four persistent crew
  • Three enemies
  • Salvage, wounds, and repairs

New Developer Setup

If you are joining the project from a fresh computer, follow these steps to get the repo locally and let an agent such as Codex or Claude Code interview you, plan the prototype, and start implementing safely.

1. Create the basic accounts

Make sure you can sign into these before installing tools:

  • GitHub account โ€” accept the Space Game collaborator invite.
  • Codex access, if you want to use OpenAI Codex.
  • Claude Code access, if you want to use Anthropic Claude Code.

3. Log into GitHub from the terminal

Open Terminal, PowerShell, or VS Code's integrated terminal and run:

gh auth login

Choose GitHub.com, HTTPS, and browser login. Then verify:

gh auth status

4. Clone the project

Put the repo somewhere easy to find:

mkdir -p ~/projects
cd ~/projects
gh repo clone TsilenT/Space-Game
cd Space-Game
code .

If code . does not work yet, open VS Code manually and choose File โ†’ Open Folder.

5. Start with Codex

Open Codex in the project folder and give it this exact prompt:

You are helping me develop Space Game, a public repo at TsilenT/Space-Game.
First, read README.md and SPEC.md. Do not write code yet.
Ask me 8 to 12 focused questions about what kind of first playable prototype I want.
Group the questions by: engine, tactical combat, art style, ship management, and first milestone.
After I answer, summarize my decisions and propose a small implementation plan with bite-sized tasks.

After Codex asks questions and you answer, use this follow-up:

Based on my answers, create a first prototype plan.
Prefer the smallest playable loop: one player ship, one enemy ship, four crew, three enemies, movement, shooting, win/loss, salvage, and repair.
Do not overbuild. Add exact files to create, exact commands to run, and how I should test each step.

6. Or start with Claude Code

Open Claude Code in the cloned repo and use this exact prompt:

Read README.md and SPEC.md for Space Game.
Act as a careful game-development partner.
Before changing files, interview me about the prototype I want.
Ask concise questions one section at a time, then wait for my answers.
Your goal is to turn the spec into a Godot 4 prototype plan that a beginner collaborator can follow.

When you are ready for Claude to write the plan:

Now write docs/prototype-plan.md.
The plan should target Godot 4 and a tiny vertical slice.
Include setup steps, scene structure, scripts, data files, testing/playtest steps, and a checklist for the first pull request.
Do not implement yet; make the plan easy to review.

7. First safe implementation prompt

Once the plan looks good, ask the agent to implement only the first slice:

Implement only Task 1 from docs/prototype-plan.md.
Keep the change small.
After editing, show me the files changed, commands run, and how to manually verify it.
Do not start Task 2 until I approve.

8. Save work and open a pull request

When a small task is working, commit and push it:

git status
git add .
git commit -m "feat: start Space Game prototype"
git push

Then open a pull request:

gh pr create --title "Start Space Game prototype" --body "Adds the first small prototype slice for review."
Agent rule of thumb: ask it to interview you first, plan second, implement third. If it tries to build the whole game at once, tell it to stop and shrink the task.