dodox/PuGa
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

README: shorten the plans section to one sentence

Browse Source 
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
dodox
2026-09-19 00:39:32 +02:00
co-authored by Claude Sonnet 5
parent 1d98d9b2d9
commit 6e0554e10a
1 changed files with 1 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+1 -11
View File
@@ -13,17 +13,7 @@ Plutonium–gallium alloy (Pu–Ga) is a specialized metallic blend of plutonium
## How it is meant to be used ## How it is meant to be used
Open Claude Code in this folder. `CLAUDE.md` is loaded automatically: it tells Claude which tools exist, which numbers to trust, and how to answer. Claude also reads `empire/PROFILE.md` (who you are, how you want answers) if you have one. Then just ask, e.g. *"what should I build on Sunday?"*, *"is BHP still worth it?"*, *"how long until I can afford it?"*. Claude answers by running the tools against live market data and your own company data, instead of guessing. Every tool is also a normal command (`puga <tool>`), so you can run them yourself. Open Claude Code in this folder. `CLAUDE.md` is loaded automatically: it tells Claude which tools exist, which numbers to trust, and how to answer. Claude also reads `empire/PROFILE.md` (who you are, how you want answers) if you have one. Then just ask, e.g. *"what should I build on Sunday?"*, *"is BHP still worth it?"*, *"how long until I can afford it?"*. Claude answers by running the tools against live market data and your own company data, instead of guessing. Every tool is also a normal command (`puga <tool>`), so you can run them yourself. Claude can also read and write your plans in PRUNplanner (`puga plan`), so you can check and tweak them in the web UI and Claude picks up your saved changes.
### Plans: you and Claude work on the same plans
The PRUNplanner web UI is where you look at a plan and tweak it. Claude works on the very same plans through the PRUNplanner API, so either of you can pick up where the other stopped:
1. Claude works out a setup with the tools (`scan`, `chain`, `simulate`) and **writes it as a plan into your PRUNplanner account** (`puga plan`), named `[PuGa] ...`.
2. You **open it in PRUNplanner**, check the simulation, change buildings, recipes, housing, experts or COGC, and save.
3. Claude **reads your saved version back** (`puga plan pull <uuid>` gives an editable YAML file, `puga simulate --uuid <uuid>` re-simulates it with your edits) and carries on from there: re-pricing it, comparing variants, or adjusting it.
Only plans named `[PuGa] ...` are ever written or deleted; your other plans are only read. Writing is a dry run unless you (or Claude, after you ask) pass `--apply`.
Everything the tools print is an **estimate** from public and personal game data. Prices move; re-run before acting. Everything the tools print is an **estimate** from public and personal game data. Prices move; re-run before acting.