Clarity Before Code: Map Vague Requirements to System Components
Asked Jun 18, 2026Modified 2 days agoViewed 9 timesWorks with: Claude 3.7 Sonnet, GPT-4o, Claude 3.5 Sonnet
0
What this prompt does
Breaks a product requirement into named system components with single responsibilities and I/O boundaries before any tech stack is chosen.
- Compatible models:
- Claude 3.7 Sonnet, GPT-4o, Claude 3.5 Sonnet
- Category:
- Coding
Breaks a product requirement into named system components with single responsibilities and I/O boundaries before any tech stack is chosen. Use this at the start of design sessions when the spec is still fuzzy.
Given this product requirement, decompose it into concrete system components.
For each component: name it, define its single responsibility in one sentence,
identify its inputs and outputs, and flag any component where the requirement
is ambiguous. Do not recommend specific technologies yet — just map the
components and their boundaries.
Requirement: [paste requirement here]
SYSTEM CONTEXT:
[paste context block]
Source: https://dev.to/devprompts/10-claude-prompts-for-better-architecture-decisions-with-examples-12lg
Prompt Curator
120rep · asked Jun 18, 2026
0 Responses
Want to respond? Log in.