Skip to content

Projects

NailsByGabs

A booking and portfolio site for a solo GelX nail artist.

Role
Full-Stack Developer
Dates
Jun 2026 – ongoing
Stack
Next.js, React, TypeScript, Tailwind CSS, Supabase, PostgreSQL, Resend, Google Calendar API, Cloudflare Turnstile, GitHub Actions, Vercel
Nails by Gabs logo: “NAILS” in large pink outlined letters, “By Gabs” in white script across them, and a pink bow
NailsByGabs · Logo

The problem

A solo nail artist needed one place to show her work and let clients book appointments on a schedule she controls. A third-party booking embed was more than the business needed, so booking had to be built in.

What I built

NailsByGabs started as a marketing site with a third-party booking embed and grew into a custom appointment platform with a loyalty program, owner tools, and seasonal themes. It is built on the Next.js App Router, mostly server-rendered with Server Components and Server Actions, with Supabase for accounts and data.

  • Booking: clients sign in with a verified email and book open slots on a week and month calendar, always shown in the salon’s time zone. PostgreSQL functions run every booking, so two clients can never take the same slot, each client holds at most three upcoming bookings, and members-only times stay reserved for loyalty members until 24 hours before.
  • Owner tools: the owner manages slots and loyalty members, books clients who have no account, edits the services, cuticle oil, and gallery pages in place, and follows bookings on an analytics dashboard built on an event log. Every appointment change syncs to the owner’s Google Calendar.
  • Email: confirmations, cancellations, change notices, loyalty welcomes, and reminders 48 hours ahead, sent through Resend in the site’s active theme colors, with reminders run by a daily Vercel cron job. A failed email never undoes a booking.
  • Security: row-level security limits each client to their own profile and bookings, Cloudflare Turnstile guards sign-up and sign-in, and a local attack script probes the API as a visitor, a client, and a member. GitHub Actions lints, type-checks, builds, and audits dependencies on every push.
  • Portfolio and themes: a gallery filtered by style tags, with a lightbox and a featured carousel, served as WebP from an image pipeline that cut 238 MB of photos to 9.4 MB and strips their metadata. The owner switches between three color themes and seasonal Halloween and Thanksgiving themes that switch back on a schedule.

BingMCP

An AI campus assistant that answers Binghamton students' questions with live campus data.

Event
HackBU 2026
Role
Campus API Research and Backend
Dates
Mar 2026
Stack
Python, FastMCP, Model Context Protocol, httpx, asyncio, Next.js, React, TypeScript, Tailwind CSS, Vercel AI SDK, Gemini

The problem

Everyday campus questions, like whether a washer is free, when the next bus comes, what's for dinner, or how busy the gym is, have answers spread across six university systems with no public APIs, none of which an AI assistant can reach.

What I built

BingMCP was built by a team at HackBU 2026 over one weekend in March 2026. It is a Python server that exposes live Binghamton data as seven tools an AI model can call through the Model Context Protocol, plus a Next.js chat app where an assistant named Baxter uses them. My part was the data: I found and reverse-engineered every campus API it reads by tracing each site’s network traffic in Chrome DevTools, helped scaffold the backend’s architecture, and created the Baxter mascot images.

  • Six undocumented sources: live bus positions and arrival times, washer and dryer counts for 31 residence hall laundry rooms, dining hall hours and menus, gym occupancy, open library study rooms, and upcoming campus events, all read from the same private endpoints the university’s own sites use.
  • Messy formats, one clean shape: dining hours come out of a nested page-layout payload with seasonal overrides and overnight hours, library rooms need a page scrape for room names plus a form request for the availability grid, and events arrive as positional rows keyed by a field list. Each tool turns its source into predictable JSON an AI model can use.
  • Plug-in tools: the server picks up any new tool folder at startup, with optional startup and shutdown hooks, and runs over stdio for desktop AI clients or Streamable HTTP for the web app.
  • Fast and fault-tolerant: per-source caches (20 seconds for buses up to 5 minutes for dining), concurrent requests, and a background poller that refreshes events every 15 minutes and keeps serving the last good copy if a refresh fails. A source that is down returns “unavailable” instead of breaking the chat.
  • Baxter: a Gemini chat built on the Vercel AI SDK that calls the tools, shows each result as a live card, and tailors answers to the student’s laundry room, dining hall, dietary needs, and the current weather, alongside a live campus dashboard.

IdleShapes

A physics idle game for Windows where bouncing shapes shatter procedurally generated glass.

Role
Solo Developer
Dates
Feb 2026 – ongoing
Stack
TypeScript, React, Matter.js, d3-delaunay, Electron, Vite, Tailwind CSS, Vitest, GitHub Actions

Placeholder: screenshot coming

IdleShapes · Screenshot

The problem

An idle game lives on endless levels and on progress that keeps building while you're away. IdleShapes needed levels that never run out, a game that keeps playing in the background, and updates that reach players without running a server.

What I built

IdleShapes is a Windows idle game built on a real 2D physics engine. Triangles, squares, and every shape up to decagons ricochet around an arena and chip away at a field of glass shards; every hit earns money for more shapes, more power, and auras. It was prototyped and shipped over two days in February 2026, then hardened and open-sourced as v1.2.7 in October 2026. The game engine is plain TypeScript on Matter.js, with React drawing the interface on top.

  • Endless levels: each level is a seeded Voronoi diagram (d3-delaunay) smoothed with a pass of Lloyd’s relaxation, so the shards come out evenly sized and a given level always looks the same.
  • Physics that never naps: a fixed 144-steps-per-second loop runs on its own timer, separate from the screen’s frame rate, so the game keeps playing at full speed while minimized, and shapes never lose energy or get stuck on walls.
  • Auras, lasers, and a Star Map: an aura links every pair of a shape with a damaging laser, checked 20 times a second against every shard edge it crosses, and 2×2 clusters on a 10×10 Star Map stack global damage bonuses.
  • Updates itself, keeps your saves: an Electron installer pulls new versions from GitHub Releases in the background (12 releases so far), and versioned save data is migrated on load so no update wipes anyone’s progress.
  • Hardened for release: split a 1,000-line engine into 10 focused modules, turned on TypeScript strict mode, added 38 unit tests and a GitHub Actions pipeline, and took npm audit from 32 findings to 0.

yumyum.io

A browser action RPG: three classes, an 18,000-unit world, crafting, and a boss in every corner.

Role
Full-Stack Developer
Dates
Nov 2025 – ongoing
Stack
TypeScript, React, Canvas 2D, Vite, Tailwind CSS, Supabase, PostgreSQL, Vercel, Playwright

Placeholder: screenshot coming

yumyum.io · Screenshot

The problem

I wanted to build a prototype based on one of my favorite games. I tried scaling it up with a multiplayer server, then went back to single-player because of the cost. Now it plays straight from a link: no account needed, no paid server, and the same speed at any refresh rate.

What I built

yumyum.io is a single-player action RPG that runs right in the browser. Pick one of three classes and fight outward from a safe village across an 18,000 × 18,000 world with up to 1,750 enemies, collecting and crafting gear across six rarity tiers on the way to the bosses in the four corners. It started in November 2025, grew a multiplayer server, went back to single-player in January 2026, and got a full overhaul for its public release in October 2026.

  • Same speed on every screen: movement used to advance once per animation frame, so on a 144 Hz monitor the whole game ran 2.4 times faster. A fixed-timestep loop now simulates in 1/60-second steps and draws once per frame.
  • Lost features, found: the single-player pivot had silently dropped six features (the safe zone, bosses, waypoints, fast travel, enemy projectile hits, and items from an unequipped bag). They’re back, along with about 25 bug fixes, all checked by 75 Playwright tests.
  • Accounts, guests, and safe saves: Google sign-in through Supabase with row-level security, or play as a guest saved in the browser. Saves queue instead of being skipped, and a token refresh no longer kicks anyone back to the menu.
  • Fast with 1,750 enemies: React runs the menus while a canvas engine owns the world, kept out of React state. Only what’s on screen is drawn, and idle enemies far from the player are skipped.
  • No server to pay for: the old Express and Socket.IO server is gone. The game is a static Vercel deploy with one small daily job that keeps the free Supabase project awake.

Personal Site

This site: a dark lab-notebook portfolio built with Astro.

Role
Full-Stack Developer
Dates
Sep 2026 – ongoing
Stack
Astro, TypeScript, Tailwind CSS, View Transitions, Canvas 2D, Vercel

Placeholder: logo coming

Personal Site · Logo

The problem

A single home for school and personal projects, experience, and contact details that stays fast, reads well on any screen, and is easy to update as new work arrives.

What I built

A static Astro site in strict TypeScript, deployed on Vercel with a custom domain on Cloudflare DNS. Everything it says lives in Markdown and YAML content collections checked by a schema, so a half-filled entry fails the build instead of shipping.

  • Design system: a warm-black “lab notebook” palette with one oxide accent, set as Tailwind CSS v4 tokens, and three self-hosted typefaces (Instrument Serif, Newsreader, IBM Plex Mono).
  • Motion: client-side page transitions where the header and footer hold still while the content rises out and in; a shared-element morph that carries a project’s title from its row into its page; a running section index with progress that follows the scroll through CSS scroll-driven animations; and one-time reveals as sections enter the view.
  • Graphite dust: a hand-written canvas background of fine specks that the cursor or a finger brushes aside and scrolling stirs, about 0.2ms of script per frame, with a watchdog that switches it off on devices that can’t keep up.
  • Accessibility: WCAG 2.2 AA contrast, a skip link, visible keyboard focus, and full support for reduced motion, checked with axe on every page.
  • Delivery: responsive AVIF and WebP images, a sitemap, social preview cards, and cookie-free analytics.