Browse / General-purpose / claude-space-thing
claude-space-thing
migujorg
The script checks the machine (pipeline doctor), installs the app's packages, builds the data with the standard profile and opens the app at http://localhost:5173.
Open migujorg/claude-space-thing → Does not match the four rules.
Built for Claude Code
ships .claude and nothing for other agents.
In its own words
A data-backed solar system simulator: what you would actually see if you were magically placed anywhere in the solar system, with every number traceable to a real measurement. Start with NORTH_STAR.md; engineering conventions are in docs/architecture.md; progress is in docs/milestones.md.
Running it
You need uv (it fetches Python 3.11, the version the pipeline is tested with, if needed), Node.js 22.12+ LTS (or 20.19+), a current Chrome or Edge (WebGPU), and the disk space of your build profile. Then, from the repository root:
The script checks the machine (pipeline doctor), installs the app's packages, builds the data with the standard profile and opens the app at The rendering scripts start their own server on 127.0.0.1 at a free port and never use 5173 unless explicitly pointed at the app with --base (why). Pass minimal or full to choose another profile, e.g. ./run.sh full. Raw downloads and built universe products are not committed: the first build downloads everything from the data archives and takes hours (table below). It can be interrupted at any time. Run the same command again and it resumes: finished stages are kept and interrupted downloads continue where they stopped. If a stage fails (a host is down, say), the others still build, the app starts with what exists, and the next run retries only what is missing. When everything is up to date, a later run starts the app within a minute.
Quoting 13% of the README. Read the rest on GitHub ↗
Read from the repository's git tree on 2026-08-17.