What Would A Dev Do?
Moves. Stacks. Judgment calls.
What each tool is for, the moves you re-google weekly, and stack playbooks that say when to use a combination, why the pieces fit, and when to walk away.
Tool directory
All toolsLanguages & runtimes
The foundation layer: languages, runtimes, and the core app frameworks built on them.
11 tools
Databases & backends
Relational, document, embedded, and vector stores, plus the backends and ORMs around them.
11 tools
Dashboards & UI kits
Pre-assembled admin panels and templates for internal tools and client portals.
6 tools
CSS & component libraries
Utility-first CSS, headless primitives, and full component design systems.
9 tools
Dev tooling & AI
Build tools, API styles, containers, and AI coding assistants.
6 tools
Game development
From browser-first renderers and 2D frameworks to full engines, plus physics, level editors, and free assets.
13 tools
AI agent skills
Installable skill folders that teach a coding agent one specific job — design direction, polish, accessibility, design systems.
7 tools
Move categories
All categoriesCSS
Layout, centering, and the snippets you re-google every week.
5 entries
JavaScript
Array methods, fetch, promises, and browser storage.
5 entries
Git / HTTP
Everyday git commands, status codes, and REST conventions.
5 entries
Game dev
Game loops, input, collision, and sprites in plain TypeScript and Canvas.
6 entries
Featured stack playbooks
All stacksVite + React + Supabase + Vercel
A short path from idea to a real product with auth, a database, and a public URL.
Read playbook →
Next.js + Postgres + Prisma + Vercel
The default choice when you need SEO, server rendering, and typed database access in one codebase.
Read playbook →
Astro + Markdown + CDN
Content sites that stay fast because there is almost no JavaScript to ship.
Read playbook →