Lesson Content

Custom Instructions are your standing brief to Claude.

Every time you start a new Claude conversation, Claude reads your Custom Instructions before your first message. They tell Claude who you are, how you work, and how you want it to respond by default. They apply in Chat, Code, and Cowork modes. They are the single most impactful memory setup step with the lowest effort to implement.

Where to find Custom Instructions.

In the Claude desktop app or browser version, go to Settings (your profile icon or the three-dot menu) and look for Custom Instructions or Profile. The exact label may vary by version – look for a section where you can write standing instructions about yourself and your preferences.

What to include in Custom Instructions.

Effective Custom Instructions have four components:

About me: Your name, professional role, industry, and relevant background. What you do and why it matters to how Claude should interact with you. Example: "My name is Chris. I am an independent course developer building an LMS platform. I have 30+ years in software QA. I work primarily in educational content and web development."

How I work: Your working style, communication preferences, and approach. Example: "I prefer concise, direct responses. I like bullet points for lists. I often switch between planning mode and execution mode – when I say 'think this out,' I want a structured plan before any action."

What I am currently working on: High-level context about your primary project or focus. This is the one component to update regularly as your work evolves. Example: "I am currently building Dabongo LMS, a WordPress-based learning management system. My main focus is course content development."

Response preferences: How you want Claude to format and deliver responses. Example: "Do not add summaries at the end of responses unless I ask. Use markdown formatting. When I ask for code, include comments for non-obvious logic only."

Writing effective Custom Instructions – practical guidelines.

• Be specific, not abstract. "I prefer short responses" is less useful than "Keep responses under 200 words unless I ask for detail."
• Write in first person. "I am a…" reads more naturally than "The user is a…"
• Update them when your situation changes. Stale Custom Instructions that describe a project you finished six months ago are worse than no instructions.
• Keep a backup copy in a notes app. This takes thirty seconds and matters the one time Custom Instructions get reset unexpectedly.
• Do not include sensitive data. Custom Instructions are stored in your cloud account and should not contain passwords, client-confidential details, or regulated personal information.

What Custom Instructions do not do.

Custom Instructions apply to every new conversation but do not give Claude project-specific context. For that, use Projects (Lesson 3). Think of Custom Instructions as who you are and how you work; Projects as what you are working on.