Singh, Shivansh — System Spec

00 · Shivansh Singh · Full-stack + AI engineer · B.Tech ’26

Straight out of college.
Straight into production.

open to work

I'm Shivansh, a ’26 batch engineer from NIT Hamirpur. Instead of a resume full of adjectives, here are three products I built and run myself — and a page that checks on them live while you read it.

live check · this page → my servers

These three products are mine, running in production. Don't take the page's word for it:

  • establishing uplink…

every check is a real request from this page's server to the domain — open the network tab and watch it happen. auto-refreshes every 30s over SSE.

01 · Production systems

Three products, shipped solo

Each one lives on its own domain and pays its own server bills. The status in every panel is checked while you read.

SYS-01

GitDocs

Any GitHub repo → a polished, PR-ready README in about a minute.

Sign in with GitHub, point it at a repo, and a three-stage LLM pipeline reads the actual source, writes the README, hands you a split-pane editor, and ships the result as a single-commit pull request.

  • SSE job stream, not polling

    Worker stage transitions travel Redis pub/sub → one EventSource per tab → pixels in ~50 ms. Refresh-safe and multi-tab safe.

  • One atomic commit via the Git Data API

    blob → tree → commit → branch → PR. No "add file 1/2/3" commit spam — a clean diff a maintainer would actually merge.

  • Images validated twice, stored nowhere

    MIME sniff client-side, magic-byte sniff server-side; screenshots travel browser → Node RAM → the repo itself. No S3, no orphans.

  • Three storage layers, deliberately split

    Redis holds in-flight jobs, Postgres holds terminal state, GitHub holds the artifact. Each layer does the one thing it's best at.

React 19 · TypeScript · Express 5 · BullMQ · Upstash Redis · Neon Postgres · Drizzle · DeepSeek · GitHub API

gitdocs.onlineCHECKING…

SYS-02

SquadWars

A real-time 1v1 football auction against an AI manager that schemes.

Bid live on real footballers in 20-second lots against Micah Richards, Jamie Carragher or Thierry Henry — LLM-driven personas with budgets, lookahead and grudges. Build your XI, and the better squad takes the night.

  • One Durable Object per match

    Every match is its own isolate with a promise-chain mutex — two bids in the same millisecond resolve deterministically, and matches self-delete via storage alarm after 24h.

  • The clock lives in the browser; the server trusts nothing

    425 Too Early on early lot-closes, anti-snipe extensions, and a reconciliation bid at close — suppressing the AI's network call gains a cheater nothing.

  • The AI's max bid is a server secret

    Computed and stored inside the DO, never serialized to the client. You can't read the opponent's wallet out of the network tab.

  • LLM with a deterministic floor

    DeepSeek plans budgets with difficulty-scaled lookahead (~78% warm prompt cache); a heuristic floor sits underneath, so an outage degrades flavour — never a match.

Next.js 16 · React 19 · TypeScript · Hono · Cloudflare Workers · Durable Objects · Cloudflare KV · DeepSeek · @dnd-kit

squadwars.onlineCHECKING…

SYS-03

PriceAlert

Market alerts you write in plain English.

"Ping me if BTC drops 5% in the next hour" — parsed into a validated condition object, watched every minute, delivered to Telegram and in-app with a grounded AI explanation of why it fired.

  • NL → Zod-validated condition objects

    Relative moves, volatility windows, indicator crosses, compound conditions — things painful in a form, trivial in a sentence. The LLM parses; Zod is the law.

  • Asset-agnostic engine

    BTC, gold, AAPL, USD/INR are just adapters. The watcher and evaluator never know what they're pricing — adding an asset class is one file.

  • The watcher reads Redis, never Postgres

    Active alerts live in a Redis hot set; Neon is only written on create and fire, so it sleeps — the whole system runs on one ~$5 VM.

  • Three trust boundaries on a public VM

    BFF calls carry user JWT + internal secret, Telegram's webhook carries its own secret, and nothing browser-facing touches Express directly.

Next.js · TypeScript · Express · BullMQ · Redis · Neon Postgres · Drizzle · Telegram Bot API · DeepSeek

pricealert.storeCHECKING…

02 · Telemetry

Coding heartbeat

Pulled from my public GitHub and LeetCode while the page is open. No screenshots, no self-reported numbers.

@shivanshsin0203verify on github ↗

syncing with github…

github's free API is throttling this page — it recovers on its own. the profile link above always works.

how the status dot works

  • pushed code within the last 45 min
  • active in the last 8 hours
  • otherwise: shows when I was last seen

activity · last 14 days

0 public GitHub events in 14 days · one bar per day

the numbers

leetcode solved

public repositories

live readers on this page (SSE connections, including you)

03 · Currently

Running processes

What's actually open on my machine this month, straight from a data file I keep honest.

process monitorupdated 2026-07-11 · edits live in data/now.ts
  1. 01pricealertv1 polish + shooting the demo filmrunning
  2. 02portfoliothis page — it monitors my own productsrunning
  3. 03squadwars_multiplayer1v1 vs a human, same Durable Object roomexploring
  4. 04agentic_workflowsmulti-step LLM pipelines beyond single promptsexploring
  5. 05next_rolefull-stack / AI product engineering · available nowget in touch →hiring?

04 · Contact

Like what you've seen? Let's talk.

I'm open to full-time engineering roles — full-stack, AI products, or anywhere in between. The products above are the best introduction I can give; everything else I'm happy to answer directly. X is the fastest way to reach me, email works just as well.