The reason you re-explain is you've never separated the two kinds of
context. Fix that and it's write-once.

INGREDIENTS vs RECIPE — the distinction that solves this
  MASTER PROMPT = ingredients = WHO you are
    Your role, team, tools, brand, preferences, how you work. Stable.
    Written once.
  SYSTEM PROMPT = recipe = the PROCESS for a specific workflow
    How to do one task. One per workflow.

You've been mixing them, which is why every project feels like starting
over — you're re-supplying the ingredients each time instead of loading
them once.

HOW IT BUILDS THE MASTER PROMPT — by interviewing you
Rather than you writing a context doc from scratch, Claude interviews you
about your role and pulls out what belongs in the master prompt. For a
marketer that's: your niche, your team, your brand voice, your tools,
your recurring workflows. The interview surfaces things you'd forget to
write down.

THE SETUP THAT MAKES IT PERSISTENT
  1. Interview → master prompt file (your ingredients)
  2. Upload it into a Claude PROJECT as a knowledge file
  3. Add team docs, brand docs, process docs alongside it
  4. Every conversation in that project now inherits the full context

  New project chat = full context already loaded. No re-explaining,
  because the ingredients live in the project, not in your memory of
  what you told it last time.

PER-WORKFLOW RECIPES
For each repeated task, a system prompt file (the recipe) sits alongside
the master prompt. Master prompt says who you are; the recipe says how to
do this specific thing. Together they mean a task starts with both who
AND how already known.

Want to start the interview now? I'll build your master prompt from it.