Mastering Claude’s Features and Power-User Commands Log in and enroll to track lesson completion. By the end of this lesson, students should be able to: The problem Custom Instructions solve. Every time you start a new Claude conversation without context, Claude knows nothing about you – not your profession, your communication preferences, your regular use cases, or what kind of responses work best for your workflow. You either re-explain this every time (tedious and repetitive) or accept generic responses that do not fit your situation. Custom Instructions is the feature that solves this. It lets you tell Claude things about yourself and your preferences once – and Claude applies that context to every conversation automatically. What Custom Instructions typically cover. Most effective Custom Instructions include two types of information: Type 1 – About you (background context): Type 2 – How you want Claude to respond: How to access Custom Instructions. Custom Instructions are typically found in your account settings or profile menu. Look for "Custom Instructions," "Preferences," or "Personalization" – the label may vary by interface version. If you cannot find it, search Claude's help documentation for "custom instructions" to find the current location in your interface. Writing effective Custom Instructions. Be specific. Vague instructions produce vague results. Weak example: I like short answers and I work in business. Strong example: I am a project manager at a mid-size manufacturing company. My team manages production scheduling and vendor relationships. I typically use Claude for: drafting communications (internal and vendor-facing), building project plans, analyzing tradeoffs, and preparing for difficult conversations. Preferred responses: direct and concise. Skip preambles – start with the answer. Use bullet points for lists, prose for explanations. Assume I have intermediate professional knowledge of operations and project management. Do not include excessive caveats or qualifications unless accuracy genuinely requires them. What Custom Instructions do NOT do. Updating your Custom Instructions. Your needs change. Your Custom Instructions should too. Review them monthly, or any time you notice Claude is consistently responding in a way that does not fit your current work. Custom Instructions are not a "set and forget" feature – they are a living configuration you maintain. Overriding Custom Instructions for a specific conversation. If your Custom Instructions set a default that does not fit a specific task, override it directly in the prompt: "For this conversation, ignore my usual preference for brief responses – I need a comprehensive, detailed answer." Your default settings remain; you just override them for this context. A freelance writer uses Claude frequently for research synthesis, drafting, and editing. Without Custom Instructions, every conversation starts with Claude writing in a generic voice, using academic hedging language she does not want, and adding long preambles before answers. Her Custom Instructions: **About me**: I am a freelance writer and content strategist. I write for B2B technology and business audiences. My work ranges from long-form thought leadership to short-form blog posts and email campaigns. **How I work with Claude**: I use Claude for research synthesis (I will paste sources), first draft generation (I will give briefs), editing and refining my own drafts, and headline/title generation. **Response preferences**: With these instructions in place, every conversation starts closer to what she needs – saving setup time on every single session. Write your Custom Instructions in the first person and in natural language – do not try to write them as formal rules or commands. "I usually write for non-technical audiences, so keep explanations accessible" works better than "RULE: All responses shall use accessible language." Natural language reads more like a colleague briefing Claude, which produces more natural, well-calibrated responses. Do not put sensitive personal information, financial account details, passwords, or private identification information in Custom Instructions. While Custom Instructions are stored in your account settings rather than shared in conversations, they represent a persistent data record. Include professional context, not personal data. Write your own Custom Instructions today. Include: (1) your professional or personal context, (2) what you most frequently use Claude for, (3) at least three specific response preferences. Save them in your Claude settings (or write them in a note to apply when the feature is available in your interface). Use Claude for your next three tasks after setting them and evaluate whether the responses feel more appropriate to your context. You should be able to write effective Custom Instructions that include your background context and response preferences, locate the Custom Instructions feature in your interface, and explain what Custom Instructions do and do not affect. Log in and enroll to take this lesson quiz.
Lesson 2: Custom Instructions – Shaping Claude’s Default Behavior
Lesson Objectives
Lesson Content
Practical Example
– Skip preambles. Start directly with the output.
– Match the voice register of whatever I'm writing – I'll specify if it should be formal, conversational, or technical.
– Do not add academic hedging phrases ("it's worth noting that," "it's important to consider"). Be direct.
– When editing my drafts: preserve my voice. Don't rewrite to sound like Claude.
– Flag uncertainty with a brief note rather than hedging throughout the response.Lesser-Known Tip
Safety Notes
Practice Task
Completion Check
Lesson Quiz