Module 7: Prompt Engineering for Architecture

Lesson 1: Role-based Prompting

In a "Zero-shot" world, you might ask Claude: "Write a function." But as an Architect, you know that a "Senior Staff Engineer at Netflix" writes code differently than a "Bootcamp Student." By defining a Role, you narrow the probability space of the model's response toward a specific professional standard.

In this lesson, we master the "Identity Layer" of prompting and learn why the "Who" is just as important as the "What."

---

1. Why Roles Work: The "Probability Anchor"

When you say "You are a Senior Security Architect," you are telling Claude to prioritize certain tokens (e.g., encryption, validation, idempotency) and penalize others (e.g., hardcoded keys, 'dirty' quick-fixes).

Role-based prompting creates:

• Tone Consistency: Professional, terse, and analytical.
• Priority Alignment: Focusing on maintenance and scale rather than just "Getting it to run."
• Constraint Salience: A security architect "remembers" to check for SQL injection without being explicitly told every time.

---

2. Anatomy of a Professional Role

A high-quality role definition has three parts:

A. The Identity

"You are a Senior Solutions Architect specialized in high-frequency trading systems."

B. The Standard

"Your work follows the principles of Clean Architecture and Domain-Driven Design (DDD). You value low-latency and strict type safety."

C. The Anti-Identity (What you are NOT)

"You avoid verbose explanations and marketing hype. You do not suggest third-party libraries unless native solutions are impossible."

---

3. Comparison: Generic vs. Role-Based

• Generic Prompt: "Explain how RAG works."
• Role-Based Prompt: "You are a Cloud Data Architect. Explain RAG in terms of indexing latency, retrieval precision, and cost-per-token vs. long-context models."

The second response will be vastly more useful for an engineering document.

---

4. Visualizing the Role Filter

graph TD
    A[Universal Model Knowledge] --> B{Role Filter}
    B -->|Security Architect| C[Secure, Typed, Defensive Code]
    B -->|Prototyping dev| D[Fast, Scripty, Loose Code]
    B -->|Tech Writer| E[Documentation + Examples]

---

5. Summary

A role is a Constraint. It sets the "Professional Floor" for the interaction. By defining the Architect's persona, you ensure that the outputs align with the constraints of high-stakes production systems.

In the next lesson, we look at the core of the prompt: Instruction Clarity and Specificity.

---

Interactive Quiz

1. How does a "Role" change the mathematical probability of a model output?
2. What are the three parts of a professional role definition?
3. Why should you include an "Anti-Identity" in your role-based prompt?
4. Scenario: You want Claude to audit your codebase for performance bottlenecks. Write a 3-sentence role definition for this task.

---

Reference Video: