PlaybookPrompts

Create a domain-primer for someone starting a new role

Education & Learning onboardingdomain-knowledgecareer-transition

When you move into an unfamiliar function—say, from engineering to product, or into a new industry—you need a fast map of the domain before you can ask smart questions. This prompt builds that map.

Prompt
You are an experienced practitioner in {{TARGET_DOMAIN}}. I am a professional coming from {{BACKGROUND}} who needs to get functional in {{TARGET_DOMAIN}} within {{TIMELINE}}.

Build me a domain primer using these steps:
1. List the 8–12 core concepts I must understand to follow a conversation with domain experts. For each, write a one-sentence definition in plain language.
2. Identify the 3 most common mistakes outsiders make when first reasoning about {{TARGET_DOMAIN}}.
3. Name the 3–5 key mental models or frameworks practitioners in this domain rely on most. Describe each in 2–3 sentences.
4. List 3 questions I should be able to answer fluently before I could claim basic competence. Do not answer them yet—I should use them as self-tests.
5. Recommend the single most efficient resource (book, paper, course, or person-type) for each of the 3 mental models.

Constraint: Do not suggest I 'do my own research broadly.' Be specific and opinionated. If {{TARGET_DOMAIN}} is highly technical and requires hands-on practice to understand (e.g., surgery, electrical work), note that this primer covers conceptual literacy only, not practical competence.
Variables to fill in
  • {{TARGET_DOMAIN}}
  • {{BACKGROUND}}
  • {{TIMELINE}}

How to use this prompt

  1. Copy the prompt above (Copy button on the top-right).
  2. Replace each {{VAR}} with your own value. Variables: {{TARGET_DOMAIN}}{{BACKGROUND}}{{TIMELINE}}.
  3. Paste it into one of the recommended tools below.
  4. Iterate: tighten constraints in the prompt if the output is generic.

Why this prompt is structured this way

The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.

Heads up: some of the links on this page are affiliate links — meaning we may earn a commission if you sign up after clicking, at no extra cost to you. We only recommend tools we'd put on our own stack. You can see our full affiliate disclosure here.

Pair this prompt with a tool

The PlaybookPrompts weekly

One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.

Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.