What Would A Dev Do?

Choose the tool. Make the move.Build the stack.

A practical developer field guide for choosing tools, solving the problems you re‑Google every week, and knowing what fits together — and when it doesn’t.

⌘K

Browse tools Explore moves Stack playbooks Pick a stack

Tool directory

All tools

Languages & runtimes

Programming languages and the runtimes that execute application code.

8 tools

Web & mobile frameworks

UI and application frameworks for browser, server-rendered, and mobile apps.

9 tools

Desktop app shells

Package web interfaces as desktop applications and connect them to native capabilities.

2 tools

API frameworks

Build HTTP services, server APIs, and request handlers.

4 tools

Databases & backends

Relational, document, embedded, and vector stores, plus the backends and ORMs around them.

20 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.

11 tools

Dev tooling & AI

Build tools, package management, containers, API styles, and AI coding assistants.

10 tools

Testing & accessibility

Unit, component, browser, and automated accessibility checks.

4 tools

Hosting & content platforms

Where sites get deployed and published: frontend clouds, edge platforms, and the CMS behind content-heavy sites.

7 tools

Game development

From browser-first renderers and 2D frameworks to full engines, plus physics, level editors, and free assets.

24 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 categories

Featured stack playbooks

All stacks