Software Engineer • AI Workflow Architect • Amateur Astrophysicist
"Research first. Test first. Evidence before claims."
Disciplined AI-assisted development. Most AI coding tools ship slop — context exhaustion, stale knowledge, no verification. I build workflows that force research before design, tests before code, and evidence before claims. No shortcuts.
Space games with physics that feel right. Eve Online's flight model, WoW's structured content, but PvE-first. Ships that have mass. A universe where the galaxy is the antagonist, not other players.
Astronomy tools for stargazers. Real-time sky data, observation logging, meteor showers, ISS passes. From CLI to progressive web app. Because sometimes you need to know what's visible at 2am from your backyard.
"If you're not occasionally computing twilight times for fun, are you even relaxing?"
A space sandbox MMO built with Bevy 0.17 (Rust). Eve Online's depth meets WoW's accessibility — but PvE-first.
The vision: A living galaxy where every item is crafted, not spawned. NPC factions with territorial ambitions. Environmental hazards. Hostile space fauna. Bio-ships grown from harvested creatures. The void is alive and hungry.
The implementation:
- Eve Online-style flight physics (exponential acceleration curves, verified by tests)
- Navigation commands: Approach, Orbit, Keep at Range, Align, Warp
- Click-to-target with lock timers and QWEASD hotkey system
- 64-bit coordinates via
big_spacefor massive universe support - 36+ passing tests verifying physics formulas
Current status: Pre-production. Flight prototype complete. Click-to-target system in progress. The ships fly exactly like Eve ships should.
void-sector/
├── crates/void_core/ # Shared physics & commands
├── crates/void_client/ # Bevy client application
├── GDD.md # 1,661-line game design document
└── .harness/ # Structured development workflow
A full-stack astronomy application — CLI, API, and progressive web app. Your window to the cosmos.
What it does:
- Real-time visibility: planets, moon phase, ISS passes, meteor showers, deep sky objects
- Observing conditions scoring based on weather, cloud cover, moon brightness
- Observation logging with equipment tracking and Messier Marathon progress
- Achievements, weekly challenges, and a gamified progression system
- Smart "What should I observe tonight?" recommendations (Premium)
The stack:
- CLI: Python + Skyfield + Click (
pip install astrosky) - API: FastAPI, deployed on Railway
- Web: React 19 + Vite + Tailwind, deployed on Vercel (PWA with offline support)
Current status: Production. Live at astrosky-beryl.vercel.app. 95+ tests. 59 React components. Premium tier with subscription infrastructure.
# CLI
pip install astrosky
astrosky tonight --location "Austin, TX"
# Or without installing
uvx astrosky tonightA Claude Code plugin that enforces disciplined AI-assisted development. Merges the best of ace-workflows and harness into one command-driven system.
Five iron rules:
- Research first — never design without verifying current APIs
- TDD mandatory — failing tests before production code
- Evidence before claims — run verification commands fresh
- Systematic debugging — root cause analysis before fixes
- Context compaction — handoff documents preserve knowledge across sessions
12 commands, 5 skills, 6 specialized agents:
/superharness:research → Explore codebase + verify external APIs
/superharness:create-plan → Design with 3 architecture options
/superharness:implement → Execute with TDD and human gates
/superharness:validate → Evidence-based verification
/superharness:debug → 4-phase systematic debugging
/superharness:gamedev → Playtesting gates for game development
/superharness:handoff → Create context checkpoint
/superharness:resume → Resume from handoff with state verification
The result: AI that researches before it designs, tests before it codes, and proves before it claims. No slop. No shortcuts.
claude plugin marketplace add astrosteveo/claude-code-plugins
claude plugin install superharness@astrosteveo-plugins- Research first. Training data is stale. Verify everything.
- Tests before code. No exceptions unless explicitly requested.
- Evidence before claims. "Should work" is not acceptable.
- The AI keeps making the same mistake? The process is wrong.
- Tools should amplify, not interrupt. Workflows beat willpower.
- Astrophysics is relaxing. Fight me.
AI Tooling: Claude Code plugins, SUPERHARNESS workflow, context management
Game Dev: Rust, Bevy 0.17, ECS patterns, big_space coordinates
Astronomy: Python, Skyfield, FastAPI, React, Tailwind, Vercel/Railway
Infrastructure: Arch Linux, tmux always, Nix when it makes sense
| Motto | "Worlds aren't hosted. They're cultivated." |
| Superpower | Turning fuzzy intent into verified, tested systems. |
| Current Rabbit Hole | Bio-horror space ships grown from alien creatures. |
| Late Night Hobby | Checking what's visible in tonight's sky. |
| Hot Take | Most "AI coding tools" skip research, skip tests, and call it productivity. |
Interested in:
- AI workflows that enforce discipline, not just suggest it
- Space sims, orbital mechanics, and Eve Online flight physics
- Astronomy tools and real-time celestial calculations
- Anything where the math is satisfying and the tests prove it works
Open an issue or start a discussion. I don't bite. The code might.
README = living document. Updated when reality changes.





