Role Interview and Master Prompt Builder
Turn a focused interview into reusable role context and separate workflow prompts, with clear scope and update rules.
Before & after
Same prompt, same agent — the only difference is the skill.
Re-explaining context every time is inefficient. Here are some ways to give Claude persistent context: - Create a document with your background, role, and preferences - Upload it as a knowledge file in a Claude project - Include key information in your custom instructions - Reference the same context document across conversations Projects let you attach knowledge files that persist across conversations, so you don't have to repeat yourself. Would you like help drafting a context document?
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.About this skill
Tired of explaining your role, team, tools, and preferences every time you start a conversation? This skill interviews you for the details that actually change Claude's answers, then turns them into reusable role context and separate workflow prompts. It also identifies where that context belongs without promising automatic inheritance across projects.
What it does
- Interviews one topic at a time, using your existing answers instead of repeating a questionnaire.
- Turns vague responsibilities into concrete deliverables, decision rights, and success criteria.
- Separates durable background, working preferences, workflow procedures, and temporary project facts.
- Converts examples of good and bad responses into specific, scoped instructions.
- Builds workflow prompts with required inputs, decision rules, output requirements, and completion checks.
- Finds conflicting preferences, unsupported assumptions, stale details, and sensitive information before they become persistent context.
What you get
A copyable Markdown master prompt containing your reusable role context, with assumptions and unresolved details clearly marked. For workflows you describe, you also get separate task instructions and a practical placement and maintenance note.
Best for
Professionals setting up Claude Projects or reusable working context, especially people whose recurring work involves several stakeholders, distinct communication styles, or processes they repeatedly have to explain.
SKILL.md preview
---
name: role-interview-and-master-prompt-builder
description: Build reusable role context through an adaptive interview, separating durable facts and scoped preferences from temporary project details and executable workflow instructions. Use when the user says "interview me for a master prompt", "Claude keeps forgetting what I do", "I keep explaining my team and tools", "make an about-me context file", "set up context for my Claude Project", "turn these notes into my working context", or "my master prompt keeps going stale".
---
# Role Interview and Master Prompt Builder
… (sign up to view the full skill)More ai & agents skills
View all AI & Agents skills →Autonomous /goal Prompt Builder
Turn rough ideas into one paste-ready /goal prompt with clear scope, constraints, acceptance checks, and autonomy rules.
Autonomous Creative Build Goal Prompts
Turn a rough game, 3D site, or video idea into one build prompt with scoped autonomy, acceptance tests, and delivery criteria.
Claude Power-User Coaching: One Tip Per Turn
Spots the Claude features and prompt habits you're missing in your actual work and coaches one concrete, copyable fix at a time.
Claude Skill Build and Launch
Turn an idea into a complete Claude skill with scoped triggers, acceptance tests, installation steps, and an agent launch plan.