Splat Sim
C 61 completed
Other
unknown / javascript · small
54
Files
5,370
LOC
0
Frameworks
4
Languages
Pipeline State
completedRun ID
#1541320Phase
doneProgress
0%Started
2026-04-16 20:39:13Finished
2026-04-16 20:39:13LLM tokens
0Pipeline Metadata
Stage
CatalogedDecision
proceedNovelty
30.12Framework unique
—Isolation
—Last stage change
2026-05-10 03:34:51Deduplication group #47274
Member of a group with 3,548 similar repo(s) — canonical #1545452 view group →
Repobility · severity-and-effort ranking · https://repobility.com
🧪 Code Distillation
Browse all specs →AI Prompt
Create a browser-based 3D arcade flight simulator. I need it to feature force-based aerodynamics, a spherical planet called Terra with mesh terrain, and an orbiting moon named Nox. The simulator should support space flight with RCS thrusters and weapons. Key features to include are the flight physics model (handling lift, drag, and torque), an ISA atmosphere model, and a Flight Data Recorder (FDR) that automatically collects and uploads telemetry data every 60 seconds to a `/api/fdr` endpoint. The core functionality should be built using Three.js and loaded via a single `index.html`.
javascript three.js flight-simulator 3d web-app physics aerodynamics game
Generated by gemma4:latest
Catalog Information
Create a browser-based 3D arcade flight simulator. I need it to feature force-based aerodynamics, a spherical planet called Terra with mesh terrain, and an orbiting moon named Nox. The simulator should support space flight with RCS thrusters and weapons. Key features to include are the flight physics model (handling lift, drag, and torque), an ISA atmosphere model, and a Flight Data Recorder (FDR) that automatically collects and uploads telemetry data every 60 seconds to a /api/fdr endpoint. T
Tags
javascript three.js flight-simulator 3d web-app physics aerodynamics game
Quality Score
C
61.1/100
Structure
46
Code Quality
90
Documentation
62
Testing
0
Practices
67
Security
100
Dependencies
70
Strengths
- Consistent naming conventions (snake_case)
- Good security practices — no major issues detected
Weaknesses
- No LICENSE file — legal ambiguity for contributors
- No tests found — high risk of regressions
- No CI/CD configuration — manual testing and deployment
- 111 duplicate lines detected — consider DRY refactoring
Recommendations
- Add a test suite — start with critical path integration tests
- Set up CI/CD (GitHub Actions recommended) to automate testing and deployment
- Add a linter configuration to enforce code style consistency
- Add a LICENSE file (MIT recommended for open source)
Languages
Frameworks
None detected
Symbols
variable480
function61
constant24
method9
class3
Embed Badge
Add to your README:
