Part 3 — Technical Design Document Generator

Part 3 — Technical Design Document Generator

I'll help you create a Technical Design Document for your MVP. This document will define HOW to build what you outlined in your PRD using modern tools and best practices.

Before We Start — Required Documents

Required Files:

1. PRD Document (from Part 2) — Required
2. Research Findings (from Part 1) — Optional but helpful

Please attach these as:

• .txt, .pdf, .docx, or .md files
• Or paste the content directly if short

These documents ensure the technical design perfectly aligns with your product requirements.

Once you've attached the file(s), please confirm your technical level:

• A) Vibe-coder — Limited coding, using AI to build everything
• B) Developer — Experienced programmer
• C) Somewhere in between — Some basics, still learning

Please attach your PRD (and optionally your research) and type A, B, or C:

---

Instructions for AI Assistant

Best AI Platforms for Technical Design

Recommended Platforms

• Claude — Strong architecture reasoning and consistent technical documentation
• Gemini — Handles complex trade-off analysis with large context
• ChatGPT — Fast technical iteration with good reasoning capabilities

Choosing the Right Platform

Need	Best Choice	Why
Architecture design	Claude	Strong at system thinking
Trade-off analysis	Gemini	Large context for comparisons
Quick iteration	ChatGPT	Fast responses

**Stability note:** Prefer stacks and tools the team can realistically maintain. If a tool is new or uncertain, present it as an optional alternative and point to official docs for verification.

**Continuity note:** Keep technical design in the same project conversation where possible. If the session gets too long, summarize/compact instead of opening an empty thread.

Wait for the user to attach their PRD document. Read it thoroughly to understand:

• Product name and core purpose
• Must-have features
• Target users and their technical level
• UI/UX requirements
• Budget and timeline constraints
• Any technical preferences mentioned

If research is also provided, scan for:

• Competitor tech stacks
• Recommended tools from research
• Cost considerations
• Technical complexity insights

Then ask these questions ONE AT A TIME based on their technical level:

Path A — Vibe-Coder Questions:

**Q1:** "Based on your PRD for [App Name], where should people use it?

• Web (works in any browser)
• Mobile app (download from app store)
• Desktop app (download to computer)
• Not sure — help me decide based on my users"

**Q2:** "What's your coding situation?

• No-code only (visual builders, zero code)
• AI writes all code (I guide and test)
• Learning basics (simple code with AI help)
• I want to understand what's built"

**Q3:** "Budget for tools and services?

• Free only (using free ti