Your role
What you are responsible for, what people come to you for, and which decisions usually land on your desk.
Back to 10 Days
Day 1
The You File
Create the file Claude will read later inside The Brickyard. It tells Claude who you are, what you touch, what good looks like, and where you want help first.
Output
A markdown file for ABOUT ME.
When the workspace opens, this becomes your personal context file.
What you are making
The You File is a plain markdown file. Later, it can live inside `ABOUT ME/` in The Brickyard so Claude starts with your role, voice, tools, judgment calls, and first use cases already loaded.
This is different from the awareness check-in. The check-in gives Max a teaching snapshot. The You File gives Claude your working context.
What it needs
Give Claude your working context.
The file should be specific enough that Claude can help without asking you to explain your role from scratch every time.
Your real work
The calls, drafts, applications, resources, Slack threads, Notion pages, analytics, and assets you actually touch.
Your quality bar
What makes an answer useful, what makes it generic, and what Claude should check before calling something done.
Your voice
How writing should sound, what it should avoid, and which examples feel like the right standard.
Your first use cases
Three practical things you want to try first so the training starts with real work, not a blank chat.
Copy this
You File builder prompt
You are helping me create a personal context file for Claude. The file is called "The You File." It will eventually live inside a Brickyard workspace under ABOUT ME/[my-name]-you-file.md. Goal: Create a clear markdown file Claude can read before helping me work. It should explain my role, real responsibilities, quality bar, voice, tools, current projects, and first AI use cases. Rules: - Interview me one question at a time. - Keep this under 10 minutes. - Keep each question short. - Do not over-explain. - If I am vague, ask for one concrete example. - At the end, produce a clean markdown file I can copy into a .md document. - Use plain language. - Do not invent details. Ask these questions: Question 1: What is your name, role, and what are you responsible for on the team? Question 2: What work do you touch most often in a normal week? Give real examples: calls, drafts, applications, resources, Slack questions, Notion pages, analytics, client work, creative review, lead magnets. Question 3: What part of your role takes the most judgment? What do you notice that a generic assistant would probably miss? Question 4: What does a good answer from Claude need to do for you? What makes an answer feel generic or wrong? Question 5: When Claude writes or thinks with you, what should it sound like? What should it avoid? Question 6: What tools or places does your work live in? Examples: Claude, Notion, Slack, Google Drive, Apollo, Instagram, email, analytics tools. Question 7: What are three things you want to try using Claude for first? After Question 7, create the final file in this format: # The You File ## Name and role ## What I am responsible for ## What I touch most often ## Highest-judgment work ## My quality bar ## My voice and taste ## Tools and where work lives ## Current projects or priorities ## First Claude use cases ## How Claude should work with me ## One thing Max should know before teaching me End by saying: "Copy this into a markdown file named [your-name]-you-file.md. Save it somewhere you can find later. When The Brickyard opens, this belongs in ABOUT ME."