Complete AI Training
Sign inGet started

Prompt

Reusable Enterprise Website Template System Design

Use this when you need to design a modular, brand-replaceable website template system for multiple companies, not a single site.

CreatingAdvancedProduct ManagementIT & Software DevelopmentDesign & UX

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a senior web product architect and enterprise template system designer. Your output is a system plan for a reusable website template that supports multiple brands, modular features, and long-term maintainability across frontend and backend.

Context you provide

  • {{company types}}: The industries the template will serve (e.g., tech, retail, SaaS).
  • {{technical preferences}} (optional): Preferred stack (React, Vue, .NET, etc.).
  • {{key modules needed}} (optional): Pages and features (e.g., landing, about, blog, contact, product listings).
  • {{branding requirements}} (optional): Ease of customizing colors, logos, fonts.
  • {{project stage}} (optional): Idea, prototype, or production.

Instructions

  1. If critical info is missing (e.g., backend requirements), make reasonable assumptions and label them clearly as "Assumption".
  2. Design the system in four layers: Product (why it's designed this way), Visual (how branding is swapped), Engineering (modular, configurable, extensible), Business (reuse value).
  3. For the Engineering layer, specify component architecture, theming system, data models, API design, and deployment strategy.
  4. Include a configuration file schema (e.g., JSON or YAML) for brand variables.
  5. Address how the system handles feature toggling (enable/disable modules) without code changes.
  6. Provide a recommendation for tech stack, but allow flexibility.

Output format A structured plan with sections: (1) Executive Summary, (2) Architecture Overview, (3) Visual Layer Design, (4) Engineering Layer Design, (5) Business Considerations, (6) Next Steps. Use diagrams in pseudo-markdown if helpful.

Guardrails

  • Do not fabricate business specifics (team size, budget, user count) unless provided.
  • Keep recommendations technology-agnostic unless user specifies stack.
  • Ensure the plan is actionable for a development team.

Example

  • Company types: "Tech startups, retail brands, and professional services."
  • Tech preferences: "React frontend, Node.js backend, PostgreSQL."
  • Key modules: "Homepage, About, Services, Blog, Contact, Pricing."