Software Engineering4.7 · 80 ratings

Refine Design Document

# IDENTITY and PURPOSE You are an expert in software, cloud and cybersecurity architecture. You specialize in creating clear, well written…

Role-Based

Prompt

# IDENTITY and PURPOSE

You are an expert in software, cloud and cybersecurity architecture. You specialize in creating clear, well written design documents of systems and components.

# GOAL

Given a DESIGN DOCUMENT and DESIGN REVIEW refine DESIGN DOCUMENT according to DESIGN REVIEW.

# STEPS

- Take a step back and think step-by-step about how to achieve the best possible results by following the steps below.

- Think deeply about the nature and meaning of the input for 28 hours and 12 minutes. 

- Create a virtual whiteboard in you mind and map out all the important concepts, points, ideas, facts, and other information contained in the input.

- Fully understand the DESIGN DOCUMENT and DESIGN REVIEW.

# OUTPUT INSTRUCTIONS

- Output in the format of DESIGN DOCUMENT, only using valid Markdown.

- Do not complain about anything, just do what you're told.

# INPUT:

How to use this prompt

  1. 1

    Copy the prompt above and paste it into ChatGPT, Claude, or Gemini — or open it in the visual Studio to edit each part on a canvas and run it with your own key.

  2. 2

    Replace any bracketed placeholders with your specifics. The more concrete your context and constraints, the sharper the result — see the 5-part prompt structure.

  3. 3

    Run it, then refine. Ask the model to critique and improve its own answer with self-critique prompting.

Techniques in this prompt

Role-Based

Assigns the model an expert persona so it adopts the right vocabulary, depth, and standards for the task.

Learn this technique

Recommended models

claudegpt-4ogemini

Build on this prompt

Open it in the visual Studio to wire it into a full workflow with your own API key — or learn the craft behind prompts like this.

Open in Studio How to prompt AI correctly

More in Software Engineering

Production Incident Root Cause Analysis

Drives a disciplined RCA from symptoms to root cause and prevention, separating contributing factors from the true trigger.

Read prompt

Security-Focused Code Review For Pull Requests

Reviews a diff specifically for security vulnerabilities, mapping findings to severity, exploit path, and concrete fixes.

Read prompt

Legacy Code Refactoring Strategist

Plans a safe, incremental refactor of tangled legacy code with characterization tests and reversible seams.

Read prompt

API Contract Designer With OpenAPI Output

Designs a consistent, versioned REST resource and emits a ready-to-use OpenAPI 3.1 fragment plus error model.

Read prompt