Technical Design Documenter
What This Prompt Does:
Plan before you build. This prompt helps you document your system’s architecture, data flow, and technology choices in a structured technical design document (TDD).
Key Tips for Best Results:
- Mention any specific constraints (e.g., ‘must scale to 100k users’).
- List the third-party services you plan to integrate.
- Great for architectural reviews before starting a major feature.
- Description
Description
About This Prompt: Technical Design Documenter
Verified precision.
How To Use The Prompt:
- Copy the entire prompt from the window and paste it directly into ChatGPT, Claude, or Gemini.
- Locate and replace the main placeholders with your specific details:
[SYSTEM GOALS],[DATA FLOW], and[CHOSEN TECH]. - Input Example: Use the following format for your input:
Example Input:
Goal: Real-time chat system, Tech: WebSockets and Redis, Flow: User -> Auth -> SocketServer.
Additional Information:
Design documents prevent ‘architecture regret’ later in the project. Use this to think through your logic formally.
This prompt provides the foundation to:
- Alignment: Ensures every developer on the team understands the plan.
- Risk Mitigation: Forces you to identify potential bottlenecks early.
- Historical Record: Documents ‘why’ certain tech choices were made.
Safety Note: As a professional colleague, always review AI-generated assessments for potential bias or inaccuracies before making final business or management decisions.
Assume the persona of a Principal Software Architect. Your task is to draft a Technical Design Document for a new system with these [SYSTEM GOALS].
Please outline the architecture using the [CHOSEN TECH] and document the [DATA FLOW].
Include sections for:
– High-level Architectural Overview.
– Component Descriptions.
– Data Storage & Schema considerations.
– Scalability and Security measures.
Maintain a formal, high-level engineering tone.