Skip to main content
← Back to templates

Website Architecture Planner

Programming

Plan a full site architecture, including caching strategy, before writing code.

Role: You are a principal software architect.

Context: Website type: a marketplace for local service providers
Audience: homeowners and independent contractors
Features: search/filter, booking, reviews, messaging
Requirements: must handle regional traffic spikes, mobile-first

Task: Site map, 3 user flows, data models, API requirements, component inventory, page templates, tech stack recommendation, caching strategy, SEO structure.

Constraints: Recommendations justified by stated requirements; flag scale assumptions.

Output Format: Site map -> flows -> data models -> API -> components -> stack -> caching -> SEO.

Expected output

A full architecture: site map, 3 user flows, data models, API requirements, component inventory, page templates, a justified tech stack, a caching strategy, and SEO structure — with scale assumptions flagged where the requirements didn't specify them.

Usage tips

  • State real requirements, not just features — the caching strategy and stack recommendation depend heavily on actual scale/traffic expectations.
  • Follow up on the flagged scale assumptions specifically — they're the parts most likely to need your own real numbers.

Try it

Fill in the placeholders below and see the compiled prompt update live.

The type of website.

The intended audience.

The relevant features.

The requirements to satisfy.

66
Words
508
Characters
0/4
Placeholders filled
1 min
Reading time
Quality score11
  • Completeness0
  • Clarity0
  • Context0
  • Specificity0
  • Constraints0
  • Format0
  • Output0
  • Constraints note100
  • Success criteria0
  • Scope focus100
  • Verification step0
  • Negative example0
  • Confidence0
  • Placeholder syntax100
  • Markdown structure0
Suggestions
  • Fill in the remaining placeholders.
  • Expand your answers — a few words each isn't enough detail for the model to work with.
  • Add background context so the model understands the situation.
Role: You are a principal software architect. Context: Website type: {{WEBSITE_TYPE}} Audience: {{AUDIENCE}} Features: {{FEATURES}} Requirements: {{REQUIREMENTS}} Task: Site map, 3 user flows, data models, API requirements, component inventory, page templates, tech stack recommendation, caching strategy, SEO structure. Constraints: Recommendations justified by stated requirements; flag scale assumptions. Output Format: Site map -> flows -> data models -> API -> components -> stack -> caching -> SEO.
AI Assistant

Jump to a page…

Navigation