Who the model becomes. Specific expert, not vague personality.
Engineer Prompts.Don’t Collect Them.
A complete, interactive XML framework for turning intent into clear, reusable AI instructions.
Prompt Architect helps people design prompts from first principles: define identity, scope, behaviour, boundaries, structure, failure handling, and quality checks. It works across ChatGPT, Claude, Gemini, open models, and enterprise AI systems.
Design the prompt while you learn the architecture.
Choose a starting point, activate only the tags you need, edit the instructions, and copy the generated XML prompt. Your content stays in this browser.
<role> You are a [specific expert identity] with [X years] of experience in [narrow domain]. You specialize in [precise capability]. </role> <mission> Your task is to [precise directive]. You must: - [primary objective] - [secondary objective] - Do NOT [what to exclude] </mission> <output_format> Return: SECTION 1: [Name] (max X words/sentences) SECTION 2: [Name] (format: bullet list / table / JSON) SECTION 3: [Name] (numbered steps) </output_format>
Start with the core. Add precision only when the task needs it.
Core tags handle most prompts. Advanced tags solve specific failure modes: missing context, inconsistent voice, shallow reasoning, hallucination, workflow leakage, or absent quality control.
What the model does. A directive, not a description.
Exactly what the output looks like. Format is intelligence.
Behavioural guardrails. How the model acts, not what it produces.
Hard limits on the output: length, language, scope, or timeframe.
One strong example often teaches more than a paragraph of instructions.
Background the model needs before acting.
Personality and voice. Role is expertise; persona is character.
The emotional register: confident, candid, warm, or analytical.
Who the output is for and what knowledge can be assumed.
Domain facts and source material injected as reference.
A sequenced process where order and dependencies matter.
Bad-output examples that help the model avoid unwanted patterns.
What to do when the task cannot be completed safely or accurately.
A quality checklist the model applies before delivering.
Questions the model asks before acting to recover missing context.
An input-output contract that links one prompt to the next.
Rules control behaviour. Constraints control output.
Shape how the model acts and reasons.
- Never assume
- State a fatal flaw directly
- Avoid vague filler
Shape what the model is allowed to produce.
- Maximum 200 words
- Use US English
- Do not discuss restricted topics
Swap components. Don’t rebuild from scratch.
Fix the tag that causes the failure.
When output disappoints, adding more words everywhere usually makes the prompt harder to follow. Diagnose the symptom and strengthen the responsible component.
Make the expert identity narrower: domain, experience, and specialization.
One architecture, many high-value workflows.
Leadership Memos
Turn scattered thinking into concise, decision-ready executive documents.
Board Updates
Structure AI, security, scale, economics, and risk narratives clearly.
Research Synthesis
Separate evidence, inference, disagreement, and unanswered questions.
Product Requirements
Move from ambiguous intent to scope, risks, and testable acceptance criteria.
Architecture Reviews
Evaluate trade-offs across security, reliability, data, cost, and scale.
Multi-Step AI Workflows
Define stable contracts between research, decision, generation, and review stages.
Prompts are not magic spells. They are system design.
You do not need fifty saved prompts. You need one composable framework that can be understood, tested, debugged, and reused.