Tech Stack Decision Doc

Before writing any code, to lock all technology decisions in writing so your AI coding agent never has to guess or make stack decisions independently.

Submitted by @dotsystemsdevs

Prompt

```
Generate a TechDesign.md document for my project. Every decision must be made — no TBD, no "we'll decide later." This document will be committed to the repo and read by the AI coding agent at the start of every session. Ambiguous decisions create inconsistent code.

Project name: [PROJECT NAME]
What it does: [ONE SENTENCE]
Target users: [WHO USES IT]
Expected scale at launch: [e.g. <1000 users, <100 requests/minute]
My constraints: [e.g. must use Vercel free tier, must use Postgres, no paid auth services]

Generate TechDesign.md with these exact sections. For each decision, state the choice AND the reason it was chosen over the main alternative: