# Recommended Tech Stack

Select technology after the project outcome, platform, data, security, offline, budget, and team constraints are understood. “AI can write it” does not remove maintenance or operating responsibility.

[Kit README](README.md) · [Project Overview](Project%20Overview.md) · [PRD](Full%20PRD%20Template.md) · [Master Build Prompt](Master%20Build%20Prompt.md) · [Completion Checklist](Project%20Completion%20Checklist.md)

## Decision Table

| Approach | Candidate Stack | Choose When | Team Evidence | Cost Boundary |
| --- | --- | --- | --- | --- |
| Static | HTML, CSS, JavaScript | Fast, small brochure or portfolio | [TEAM FIT] | [MONTHLY COST ESTIMATE] |
| Component site | Astro or React | Reusable sections and partial interactivity | [TEAM FIT] | [MONTHLY COST ESTIMATE] |
| Full web app | Next.js | Authentication, server rendering, or dynamic data | [TEAM FIT] | [MONTHLY COST ESTIMATE] |

## Default Recommendation

Start with the least complex option in the table that supports every P0 requirement. For **[PROJECT NAME]**, record:

- **Chosen approach:** [APPROACH]
- **Why it fits:** [REQUIREMENTS AND TEAM EXPERIENCE]
- **Rejected alternative:** [OPTION + SPECIFIC TRADE-OFF]
- **Runtime and package versions:** [PINNED OR SUPPORTED RANGE]
- **Hosting/deployment:** [DEPLOYMENT PLATFORM]
- **Expected monthly cost:** [ESTIMATE + ASSUMPTIONS]
- **Exit plan:** [EXPORT, MIGRATION, OR REPLACEMENT PATH]

## Stack Layers

| Layer | Choice | Responsibility | Avoid |
| --- | --- | --- | --- |
| Interface | [CHOICE] | User interaction and presentation | Business rules hidden only in UI |
| Application | [CHOICE] | Validation, authorization, orchestration | Framework-specific domain leakage |
| Data | [CHOICE] | Durable records and queries | Schema-less ambiguity without reason |
| Identity | [CHOICE OR NONE] | Sessions and user identity | Custom password storage without expertise |
| Testing | [CHOICE] | Unit, integration, and end-to-end confidence | Only manual happy-path tests |
| Delivery | [CHOICE] | Builds, environments, deploy, rollback | Manual production edits |
| Observability | [CHOICE] | Logs, metrics, traces, crash reports | Sensitive data in logs |

## Selection Gates

- [ ] The stack supports the primary platform and accessibility requirements.
- [ ] The team can run, test, update, and debug it locally.
- [ ] Authentication, payment, AI, file, or notification services are server-side where secrets require it.
- [ ] Data export, backup, restore, and vendor exit are possible.
- [ ] Package licenses and support status are acceptable.
- [ ] The budget includes usage, storage, bandwidth, build, monitoring, and support—not only hosting.
- [ ] A short technical spike has tested the riskiest integration.

## Common Mistakes

- Adding a database, queue, vector store, or microservice before a requirement needs it.
- Choosing several UI frameworks for one product.
- Depending on an unverified package or imaginary API.
- Mixing sample and production configuration.
- Ignoring update and migration ownership.