GitHubProduct interfaces
VISIBLE LAYERModern web experiences with deliberate details.
.zox @zoxile Syncing / Checking public activity FULL-STACK DEVELOPER // BUILDER Full-stack / FiveM / tooling
I build the whole path.
I design the interface, wire the API, automate the release, and stay for the maintenance. Mostly Svelte, TypeScript, Lua, C#, and whatever the system actually needs.
- Experience
- 5+ years
- Public repos
- 11
- Current status
- Building
IDENTITY NODE
Zox / zoxile
Full-stack developer with a bias toward understandable systems.
INTERFACESvelte 5
→ SERVICESTypeScript
→ RUNTIMELua / C#
- CO-FOUNDER
- Orbit Studios
- CONTRIBUTOR
- ESX
- LEARNING
- Docker / Godot
- TOUCHED_GRASS
- false
WORKBENCH / LIVE Currently exploring Docker, Godot, and lower-level systems.
DESIGN / ENGINEERING / DELIVERY
I build the parts people use and the systems that keep them running.
I'm Zox, a developer who works comfortably across the stack. I like taking an idea from a rough problem to a dependable product without losing sight of how it feels to use or maintain.
At Orbit Studios, that means balancing technical quality with real delivery: clear interfaces, resilient runtime code, useful tooling, and support that earns trust after release day.
Runtime systems
CORE LAYERFiveM resources and services built to stay stable.
Developer leverage
FORCE MULTIPLIERAutomation, APIs, bots, and internal tooling.
DEFAULT BEHAVIOR
Understand the whole path, simplify the moving parts, then polish what remains.
Selected work
Things I’ve shipped.
01 View on store 02 View on store 03 View repository 04 View repository
orbit-dynamichud
Featured Orbit releaseA configurable FiveM HUD built around readable player state, responsive UI, and clean framework integration.
orbit-craftingsystem
Orbit releaseA server-ready crafting system designed for configurable recipes, stations, and project-specific integrations.
fxserver-installer
Public sourceA focused installer and management toolkit for running FXServer environments with less operational friction.
CS2Economy
Public sourceA feature-rich economy plugin for Counter-Strike 2, built around a small and dependable C# core.
Toolkit
A toolchain with interchangeable parts.
The system decides the stack. These are the tools I can reach for without slowing down to relearn the basics.
04 lanes 27 modules adaptable by design
Languages
701 
TypeScript 02 
JavaScript 03 
Lua 04 
C# 05 
Python 06 
HTML 07 
CSS
TypeScript 02 JavaScript 03 Lua 04 C# 05 Python 06 HTML 07 CSS Frontend
601 
Svelte 02 SvelteKit 03 
React 04 
Next.js 05 
Vite 06 
Tailwind CSS
Svelte 02 SvelteKit 03 React 04 Next.js 05 Vite 06 Tailwind CSS Backend
601 
Node.js 02 
Express 03 
MySQL 04 
MariaDB 05 
SQLite 06 
Discord.js
Node.js 02 Express 03 MySQL 04 MariaDB 05 SQLite 06 Discord.js Environment
801 
Linux 02 
Docker 03 
Git 04 
Cloudflare 05 
PM2 06 
Zed 07 
Figma 08 
Godot
Linux 02 Docker 03 Git 04 Cloudflare 05 PM2 06 Zed 07 Figma 08 Godot GitHub signal
The work leaves a trace.
Public repositories, fixes upstream, and the ordinary maintenance between releases. This is the last twelve months, not a decorative screenshot.
520contributionslast 12 months
3pull requestspublic + authored
11day streaklongest run
11repositoriespublic systems
PUBLIC CODE MIX
Calculated from owned, non-fork repositoriesSvelte51.2%Rust25.5%TypeScript13.6%C#8.2%JavaScript0.9%Other0.6%
365 DAY CONTRIBUTION TRACE
Live GitHub dataSyncing activity Hover or focus a cell for the exact count
UTC / GITHUB.COM / ZOXILEJun
Jul
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
How I work
A few non-negotiables.
// boring code is often the code that survives.
01
Debuggable over clever
Systems should be easy to understand when something goes wrong.
02
Architecture with intent
Modular boundaries, predictable behavior, and no abstractions without a reason.
03
Quality is user-facing
Performance, communication, UX, and reliability all belong to the same product.
Field notes
Questions before the first message.
What I ship, where private work lives, and how I approach an existing system.
Start with context
Bring the problem.
We’ll map the system.
A useful first message is simple: what exists, what is failing, and what a good result should look like.
01 Current context 02 Main constraint 03 Desired outcome
