Engineering Role Prompt Architecture

Software Architect Role Prompt

Make AI act as a software architect — system design, scalability, service boundaries, and trade-offs — instead of jumping straight to code.

Overview

Ask an AI to design a system and it tends to start typing code; ask it to act as a software architect and you get the decisions that come first — the boundaries, the non-functional requirements, and the trade-off behind each call. This generates a role prompt that fixes the AI as a principal software architect: expensive-to-reverse decisions get the judgment, every quality attribute is weighed against another, and each design states its assumptions and the failure mode it guards against. Open it in the Role Prompt Generator to adjust the seniority level, industry, and focus areas.

How to use this resource

  1. Open the example in the tool

    It loads with realistic inputs already filled in.

  2. Swap in your own details

    Adjust the inputs and options to match your case.

  3. Generate and copy

    Produce the output and paste it where you need it.

Why This Works

  • A role fixes the AI's reasoning framework, so it weighs reversibility and trade-offs, not just whether the code runs
  • Principal seniority changes behavior — the architect answers at systems level and flags second-order effects a junior would miss
  • Focus areas concentrate the model where it matters: system design and explicit trade-off analysis

Best for

  • Pressure-testing a system design before you build it
  • Choosing between architectural options with the trade-offs named
  • Setting service and module boundaries that hold up as you scale

Not for

  • Writing the implementation itself — use the Software Engineer role prompt
  • Defining behavior rules and output format — use the System Prompt Generator

FAQ

What does the software architect role prompt produce?

It makes the AI answer like a principal software architect, presenting each design as the forces at play, the options, the chosen structure, and the trade-off that choice accepts. It states its assumptions about scale and team and names the failure mode each decision guards against, weighting attention toward system design and explicit trade-off analysis rather than jumping straight to code.

What context should I give the software architect prompt before using it?

Give it the actual system or decision you are weighing, plus the real load and growth curve, the team that will run it, and the constraints that bind you. It judges fitness for your actual load, reversibility, and whether your team can build and operate the design — vague inputs get vague trade-offs. Open it in the Role Prompt Generator to set seniority, industry, and focus areas first.

Does this prompt decide the architecture for me?

No — it gives you an architect's critique and the trade-offs behind each option, but you make the call and you build it. Run the role prompt in your own AI tool to pressure-test a design; it names the forces, the alternatives, and the accepted trade-off, and it won't write the implementation itself. The final architecture decision, and the code, stay yours.

More resources from Role Prompt Generator

Resources that pair well

Related tools

Projects that use this resource

Workflows that use this resource

Guides for this resource

Tip: Save time by exploring related resources and tools that integrate with this resource.