Give Claude context
Start with the You File prompt so Claude knows your work, audience, voice, offers, and preferences.
Bonus resource hub
Prompts, Skills, and polish passes
Make Claude actually useful after class
A working library for the things people actually ask Claude to do: clean up notes, write in your voice, make decisions, shape pages, and make messy work look professional.
Start here
Use this hub like a bench, not a bookshelf.
Pick the job you need done, copy the prompt, and run it on real material. Claude gets better fastest when it has your examples, your corrections, and your taste.
Run one real task
Use a prompt from the library on an actual email, note, page, or decision. Generic examples teach generic behavior.
Correct the output
Tell Claude what is off, what is close, and what should become a rule. Then save those rules into your project.
Prompt library
Copy, paste, then replace the brackets.
Foundation
You File interview
Use this when Claude still sounds like it has never met you.
I want you to interview me and build a reusable You File for future Claude work.
Ask me one question at a time. Cover:
- what I do
- who I serve
- my offers
- my voice
- my standards
- what I hate in generic AI output
- examples of work I like
- examples of work I dislike
- recurring projects and decisions
After the interview, create:
1. A concise You File
2. A voice and taste profile
3. A list of rules Claude should follow
4. Five questions Claude should ask before helping me with important work
Writing
Make this sound like me
Use after Claude writes something that is technically fine and spiritually beige.
Rewrite this so it sounds like me.
Before rewriting, infer my voice from the examples below. Tell me the 5 voice rules you are using.
My examples:
[paste 2-4 examples]
Draft to rewrite:
[paste draft]
Constraints:
- keep the meaning
- remove generic AI phrasing
- keep it direct and human
- do not make it more formal unless the audience requires it
- preserve any specific facts or dates
Notes
Digest messy notes
Turn raw notes, transcripts, and voice dumps into something you can act on.
Digest these messy notes into a clean working brief.
Use this structure:
1. What happened
2. Decisions made
3. Open questions
4. Action items with owners
5. Risks or things to watch
6. Follow-up message I can send
Rules:
- do not invent details
- mark uncertainty clearly
- keep the action items concrete
- preserve exact dates, names, and numbers
Raw material:
[paste notes/transcript]
Decision
Decision brief
Use when you are circling the same decision and need the fog reduced.
Help me make this decision.
Decision:
[state the decision]
Context:
[paste relevant context]
Options I am considering:
[list options]
Create:
1. The real tradeoff
2. The best case for each option
3. The hidden cost of each option
4. What I would choose if speed mattered most
5. What I would choose if quality mattered most
6. A recommendation with confidence level
7. The smallest next step that creates clarity
Email
Email that does not sound corporate
For follow-ups, launches, client messages, and slightly awkward nudges.
Write this email in a clear, warm, non-corporate voice.
Goal:
[what the email needs to accomplish]
Audience:
[who is receiving it]
Context:
[what they need to know]
Tone:
[direct / warm / excited / firm / calm]
Draft or bullets:
[paste]
Give me:
1. A short subject line
2. The email
3. A more concise version
4. A slightly warmer version
Landing Page
Sales page clarity pass
Use before screenshots, checkout links, or sending a page to traffic.
Review this sales page copy for clarity and conversion.
Audience:
[who this is for]
Offer:
[what is being sold]
Page copy:
[paste copy or screenshots]
Find:
1. Where the promise is clear
2. Where the reader may hesitate
3. Where the page sounds generic
4. Missing proof, risk reversal, or logistics
5. The top 10 edits I should make first
Then rewrite the weakest section.
Creative
Ten angles without mush
Use when you need options but do not want vague brainstorm soup.
Give me 10 sharp angles for this idea.
Topic:
[topic]
Audience:
[audience]
What they already believe:
[beliefs]
What I want them to understand:
[new belief]
For each angle, include:
- headline
- emotional hook
- specific proof or example needed
- why this angle might work
- why it might fail
Avoid generic productivity, unlock, transform, and game-changer language.
QA
Final send check
Run this before an important doc, page, email, or proposal leaves your desk.
Act as my final quality check before I send this.
Material:
[paste]
Check for:
1. Anything unclear
2. Anything that sounds inflated or generic
3. Missing context
4. Claims that need proof
5. Tone issues
6. Typos or formatting problems
7. The one thing most likely to cause confusion
Give me a prioritized fix list, then a cleaned-up version.
Polish
Make it look professional
The quick design-and-clarity pass for screenshots, docs, decks, pages, and handoffs.
Run a professional polish pass on this.
My goal:
[what this is supposed to do]
Audience:
[who will see it]
Material:
[paste copy, screenshot notes, layout description, or doc]
Evaluate it across:
1. First impression
2. Visual hierarchy
3. Clarity of headings
4. Spacing and density
5. Tone and credibility
6. What feels amateur
7. What feels unnecessary
8. What to change first
Then give me:
- a high-priority fix list
- revised copy where needed
- layout recommendations
- a final version that feels clean, professional, and easy to scan
Setup
Build project instructions
Use this when you want a Claude Project to behave consistently.
Help me create instructions for a Claude Project.
Project purpose:
[what this project is for]
Typical inputs:
[what I will paste into it]
Typical outputs:
[what I want back]
My standards:
[what good looks like]
Create:
1. Project instructions I can paste into Claude
2. A list of files or examples I should upload
3. Rules Claude should follow
4. Questions Claude should ask when context is missing
5. A first test prompt for this project
Offer
Sharpen the offer
Use when your idea is good but the buyer promise is still fuzzy.
Help me sharpen this offer.
Audience:
[who this is for]
Current offer:
[paste]
What they want:
[desired outcome]
What they are worried about:
[risks, objections, constraints]
Give me:
1. The plain-English promise
2. The strongest buyer reason to care
3. The confusing parts
4. The missing proof
5. A clearer offer description
6. Five headline options
7. The most important objection to answer
Support
Support reply
For student, client, or customer replies that need to be clear and kind.
Write a helpful support reply.
Situation:
[what happened]
What I can offer:
[what is possible]
What I cannot promise:
[limits]
Tone:
clear, kind, direct, no corporate padding
Give me:
1. Recommended reply
2. Shorter reply
3. Version with more warmth
4. Any internal note I should remember before sending
Starter Skills
Small Skills that make Claude reusable.
Paste these into a Claude Project as instructions, or keep them in a doc and reuse them as needed. Each one gives Claude a defined job.
Skill 01
Digest Builder
For notes, transcripts, calls, and long messy docs.
Skill: Digest Builder
Purpose:
Turn messy source material into a clear brief someone can act on.
When used:
Use this for notes, call transcripts, voice memos, meeting recaps, long emails, or raw documents.
Instructions:
- Identify the core situation first.
- Separate facts from interpretation.
- Preserve names, dates, numbers, decisions, and commitments.
- Do not invent missing details.
- Call out uncertainty plainly.
- End with the next actions.
Output:
1. Situation summary
2. Decisions
3. Action items
4. Open questions
5. Risks
6. Suggested follow-up message
Skill 02
Voice Keeper
For keeping drafts human, direct, and recognizable.
Skill: Voice Keeper
Purpose:
Rewrite drafts so they sound like the user, not like default AI.
Instructions:
- Preserve meaning before improving style.
- Remove filler, inflated claims, and generic phrases.
- Keep sentences clear and human.
- Prefer concrete examples over abstract language.
- Match the user's existing level of warmth, humor, directness, and specificity.
- If examples are available, infer voice rules before rewriting.
Output:
1. Voice rules used
2. Rewritten draft
3. Shorter version
4. Notes on what changed
Skill 03
Decision Partner
For tradeoffs, options, and next moves.
Skill: Decision Partner
Purpose:
Help the user make a decision by clarifying tradeoffs and reducing ambiguity.
Instructions:
- Define the decision in one sentence.
- Identify what matters most: speed, quality, cost, risk, relationship, or learning.
- Compare options without pretending certainty.
- Name second-order consequences.
- Recommend the smallest next action that would create useful evidence.
Output:
1. Decision frame
2. Options table
3. Tradeoffs
4. Recommendation
5. Confidence level
6. Next action
Skill 04
Page Polish
For sales pages, landing pages, docs, and screenshots.
Skill: Page Polish
Purpose:
Make pages and documents feel clearer, more professional, and easier to scan.
Instructions:
- Start with the reader's first impression.
- Evaluate hierarchy, spacing, density, headings, proof, and visual confidence.
- Point out anything that feels amateur, crowded, vague, or overexplained.
- Keep the user's intended style, but raise the execution quality.
- Recommend the smallest set of changes that will create the biggest lift.
Output:
1. First impression
2. Top 5 problems
3. Top 5 fixes
4. Revised copy
5. Layout suggestions
6. Final polish checklist
Skill 05
Follow-Up Writer
For client notes, student support, reminders, and recaps.
Skill: Follow-Up Writer
Purpose:
Turn context into clear follow-up messages.
Instructions:
- Identify the relationship and desired outcome.
- Keep the message short unless more context is needed.
- Be warm without sounding performative.
- Make the next step obvious.
- Avoid guilt, pressure, and vague checking-in language.
Output:
1. Recommended message
2. Shorter version
3. Warmer version
4. Direct version
5. Subject line if useful
Design reference shelf
Places to point Claude when taste matters.
Use these when you want Claude to help with layout direction, visual language, examples, polish passes, or design critique.
Mobbin
App screens and product UI patterns
Landingfolio
Landing page sections and page inspiration
Godly
Modern web design references
Awwwards
High-end visual design and interaction ideas
Screenlane
Mobile and web UI examples
Refero
Product design and web inspiration
Typewolf
Typography pairings and font taste
Fontpair
Free font pairing ideas
Coolors
Palette exploration and color systems
Color Hunt
Simple palette inspiration
Lucide
Clean icons for buttons and interfaces
Figma Community
UI kits, templates, and reference files
Page Flows
User flows, onboarding, and app interaction examples
Nicelydone
SaaS pages, product screens, and marketing references
Really Good Emails
Email design, launch emails, and lifecycle examples
Dribbble
Visual directions, layout fragments, and UI exploration
Behance
Campaigns, brand systems, decks, and polished case studies
Pinterest
Moodboards, visual references, and fast taste gathering
Before you share
Run the polish pass once.
The biggest unlock is not a clever prompt. It is teaching Claude your standards, then asking it to check the work against those standards before anyone else sees it.