AvailabilityOpen to full-time & freelance work.

Anurag Mishra

Resume/CV
Full-Stack Developer.

I build production-ready, performant web applications that bridge the gap between rigorous engineering and intentional design.

Signal field

Every system
I ship is alive.

Monitoring, tracing, self-healing loops. Move your cursor through the mesh — the nodes respond the same way my telemetry does: nothing drifts unnoticed.

99.99%

uptime, engineered

2M+

events / day served

<10ms

p99, where it matters

40×

builds made faster

INDEX // 01ARCHIVE DOSSIER
About me

“They say you can’t beat someone who loves the process. Good news: you can probably beat me — I’m purely obsessed with shipping results.”

Next.js
React
TypeScript
Tailwind CSS
Python
Node.js
Express
PostgreSQL
MongoDB
Redis
Upstash
Supabase
Firebase
Clerk
AWS
GCP
Cloudflare CDN
Cloudinary
React Native
OpenAI
Claude Code
Gemini
DeepSeek
Antigravity
LangChain
LangGraph
CrewAI
TensorFlow
VS Code
Play with me
Developer Portrait
Anurag Mishra
FEATURED WORK 01
2025
AIIMS Delhi / Healthcare Portal
Next.jsPostgreSQLHealthcareAWS

A mission-critical medical festival portal and high-concurrency event registration platform engineered for AIIMS Delhi, managing delegate access and live ticketing with zero downtime.

Transactions₹1.5L+ processed
Velocity12K+ clicks in 15 days
Edge Uptime99.8% reliability
FEATURED WORK 02
2025
Media / Storytelling Platform
Next.jsCloudinaryTailwindNode.js

Self-hosted visual storytelling and multimedia narrative engine engineered for zero platform fees, full data ownership, and instant serverless scaling.

Self-Hosted100% Self-Hosted
Requests55K+ handled
Starting Fees$0 / ₹0 fees
FEATURED WORK 03
2025
Open Source / Career Engine
TypeScriptReactOpen Source750+ Forks

A viral open-source career navigation platform with worldwide adoption. Powering career roadmaps and resume telemetry for thousands of engineers.

Active Users80K+ roadmaps
Forks750+ forks
Stargazers125+ stars
FEATURED WORK 04
2026
Developer Tools / Agent Context Engine
Next.jsAI AgentsContext Engine80% Savings

Instant comprehensive codebase context and architectural maps for AI agents (Claude Code, Cursor). Eliminates token waste with zero configuration.

Work for Free100% Free Forever
Agent ContextFull Codebase Map
Token SavingsSaves tokens by 80%
FEATURED WORK 05
2025
Agentic AI / DevOps
AutonomousLLMDockerDevOps

An autonomous AI & Web3 venture creation suite and multi-cloud deployment engine that automatically scaffolds, secures, and deploys full-stack startups.

Recognition🏆 Hackathon Winner
Startup Engine4-in-1 AI & Web3
Cloud OpsZero-Downtime Deploy
FEATURED WORK 06
2026
Creative Dev / Image Processing
WASMCanvasWebGLTypeScript

High-performance browser-native image manipulation and background removal tool powered by WebAssembly and direct signed Cloudinary integrations.

WorkloadReduces Work by 70%
Execution100% In-Browser WASM
StorageDirect Signed Uploads
+
+
+
+

AI-Assisted Developer

AI-native by default. Human-directed by design.

I build with the best AI tools in the loop — and I know exactly where the loop needs a human. The tools write fast; the workflow makes it right.

Plug any tool in — I'm already fluent
Claude CodeCursorGitHub CopilotWindsurfChatGPTGeminiv0
CodeRabbitCodeAntPerplexityOllamaHugging FaceLangChainReplitMCP Servers
My AI workflow — six steps, zero skipped
Competitor teardown
Docs & API references
Deep research pass

Brief, market and existing codebase mapped before a line gets written

12 sources · 1 research brief

01Research the project

Every build starts with a deep research pass — the brief, the market, and any existing codebase — so decisions are informed, not guessed.

claude-code — zsh
claude mcp add github filesystem postgres
3 MCP servers connected
skills: webapp-building · pdf · xlsx
CLAUDE.md loaded — rules synced
agent ready — context window primed

02Configure the AI stack

The right skills, MCP servers and project rules get wired up first, so every agent works with full context — and works my way.

scaffold
pnpm create next-app --ts --tailwind
├─ src/app — routes
├─ src/components — ui system
└─ src/lib — data + utils
React 19TypeScriptTailwindMotionPostgres

03Scaffold with intent

Tech stack and libraries chosen for this problem, not whatever's trending — then a clean, typed project skeleton to build on.

PRD.md
v3 · approved
Problem statement + goals
Architecture + data model
Milestones broken into tasks
Edge cases & failure modes

04Plan & PRD first

A generated implementation plan and PRD, reviewed and refined until it's right. The plan changes cheaply — code doesn't.

Approval requested

Agent wants to run:

git push origin main && vercel deploy
Approve Reject

05Human oversight, always

Agents propose, I decide. Every approval request — deploys, migrations, destructive commands — gets a human review before it runs.

CI
PR #128 — reviewed
passed ✓
Reviewed 2 minutes ago
CodeRabbit — 14 comments resolved
CodeAnt — security scan clean
Unit + e2e — 41 / 41 passing
Preview deploy verified

06AI-reviewed & tested

CodeRabbit and CodeAnt review every PR, then CI runs the full suite. Nothing ships unreviewed — by machine or by me.

+
+
+
+

The honest scorecard

My stack vs. vibe coding.

Vibe coding wins the first hour. It loses the first rewrite. Here's the honest math — including where it beats me.

My stack Vibe coding
The full picture

All five axes at once

Cost to ship

Lower is cheaper

-20%cost
Vibe100
Mine80
Raw speed

Higher is faster

Vibe codingwins the sprint
100
My stackwins the marathon
90

It beats me to the demo — by a nose. Then the rewrite starts.

First-pass accuracy

Higher is better

100
My stack
60
Vibe coding
Adaptability

Pivots without rewrites

100My stack
70Vibe coding
Sustainability

What still works at month 12

TypeScript/React/Next.js/Python/Node.js/Express/PostgreSQL/MongoDB/Redis/Supabase/LangGraph/LangChain/OpenAI/Claude Code/AWS/Docker/Tailwind CSS/
Right now

What I'm doing
this week.

Portfolios show the past — this shows the present. A live feed of what I'm building, learning, and open to. Updated as reality changes.

anurag — status — zshlive
The agent bench

Don't read about
my agents. Drive one.

Three real tasks, scripted end-to-end. Pick one and watch the agent reason, call tools, and close the loop — the same loop my production agents run every day.

agent — bench — anuragidle
Audit the checkout flow for dead carts

select a task to begin ↖

awaiting task…enter
How I work

Pick a discipline, trace the pipeline.

Six practices I work across — each one a node graph from brief to ship.

Discipline

Interfaces that feel inevitable.

Tech stack
React
TypeScript
Tailwind
Next.js
Motion
Figma
~/pipeline · frontend
Wireframinglow-fi structure1
Referencemood · benchmarks2
UI Designhi-fi screens3
Researchuser signals4
Assetsicons · media5
Prototypeclickable flow6
Componentsdesign system7
Statedata + stores8
Routingpages · params9
API Layerfetch · cache10
Accessibilitya11y pass11
Testingunit · e2e12
Shipdeploy · QA13
The modes

One mind, every mode.

Keep scrolling — the modes flip in place ↓
01Build

Full-stack, end to end.

From Postgres indexes to the last easing curve — one person, whole product. This is the mode that ships the thing.

  • Type-safe API → UI in one pass
  • Edge-cached, server-rendered
  • Accessibility built in, not bolted on
build — pipelineexit 0
02Observe

Telemetry before optimism.

I instrument first, then ship. Traces, red-metric dashboards, alerts that page me — not you — when reality drifts from the design.

  • Traces on every request path
  • p99 budgets enforced in CI
  • Alerts routed to whoever can fix them
trace — /checkoutp99 8.2s
edge
90ms
auth
84ms
db.orders
96ms
render
79ms

span drill-down on click — every hop accounted for

03Scale

Boring tech, sharp numbers.

The stack is deliberately dull; the performance graph is not. Caching layers, query surgery, and load tests before the traffic arrives.

  • 2M+ events/day ingested
  • p99 under 10ms where it counts
  • Cost reviewed every sprint
scale — events / daylive
0

ingest pipeline — no back-pressure in 6 months

04Ship

Deploys that don't hold their breath.

Blue-green releases, feature flags, one-click rollback. Shipping is a non-event — which is exactly the point.

  • Zero-downtime releases
  • Flags for every risky path
  • Rollback rehearsed, not improvised
ship — release 4f2crolling
01
commit
02
test
03
stage
04
canary 5%
05
prod 100%

rollback rehearsed — flag off, traffic back, 90 seconds

The operating system

Six laws I ship by.

Hover a law — every project below follows them

Experience

Where I've built.

01

AI Engineer

Sayalabs2026 — Now
02

Full-Stack Developer

Independent2024 — Now
03

Computer Science (CSE)

NIT Patna2024 — 2028
Open source

Building in public.

0
Contributions · 1y
0
Current streak
0
Longest streak
0
Commits · 1y
3,726 contributions · last year
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
MonWedFri
LessMore
Problem solving

Sharpening the algorithms.

Live
World rank #3,211,341
0
Solved
0
Easy
0
Medium
0
Hard
15 submissions · last year
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
MonWedFri
LessMore
The other side