Skip to main content
Back to Your First Prompts: Getting Started with Claude
Lesson 1 of 10

Setting up your Claude account

~15 min read

Claude is Anthropic's AI assistant, available at claude.ai. Getting your account configured correctly in the first session saves hours of friction later. This reference guide covers every setup decision you'll face — plan selection, interface options, organization features, and the settings that actually affect how Claude responds to you. Bookmark this page. You'll return to it when you upgrade your plan, add a team member, or wonder why Claude's response style shifted. Everything here is current as of Claude's 2024-2025 product lineup, including the claude.ai web app, iOS and Android apps, and API access.

7 Things to Know Before You Click 'Sign Up'

  1. Claude is made by Anthropic, not OpenAI — it is a direct competitor to ChatGPT, not a version of it.
  2. The free tier gives you access to Claude 3.5 Haiku (a fast, capable model) with daily message limits that reset every 24 hours.
  3. Claude Pro costs $20/month — identical pricing to ChatGPT Plus — and unlocks Claude 3.5 Sonnet and Claude 3 Opus with significantly higher usage limits.
  4. You sign up with a Google account or email address. No credit card required for the free tier.
  5. Claude has no persistent memory by default — it forgets everything when you close a conversation, unless you use the Projects feature (Pro only).
  6. The API is separate from claude.ai — developers pay per token through console.anthropic.com, while this lesson focuses on the consumer web app.
  7. Claude is available in most countries, but Anthropic restricts access in a small number of jurisdictions due to legal and compliance requirements.

Creating Your Account

Go to claude.ai and click 'Sign up'. You can authenticate with Google (fastest), or use any email address with a password. Anthropic sends a verification email — check your spam folder if it doesn't arrive within two minutes. Once verified, you land directly in the chat interface. There's no onboarding wizard, no profile questionnaire. Claude is ready to use immediately. The interface is intentionally minimal: a text input at the bottom, your conversation history on the left sidebar, and a model selector at the top of each new conversation.

Your account settings live behind the icon in the bottom-left corner of the sidebar. This is where you'll find billing, notification preferences, and the option to set a display name. Claude uses your display name in conversations if you introduce yourself, though it doesn't automatically pull it into every response. The settings panel is sparse by design — Anthropic deliberately limits the number of toggles and configuration options compared to competitors like ChatGPT, which has a more complex settings architecture including custom instructions, memory management, and plugin configuration.

  • Account verification takes under 2 minutes via email link
  • Google OAuth login skips the email verification step entirely
  • Display name is optional but useful if you want Claude to address you by name
  • You can change your email address in account settings post-signup
  • Two-factor authentication (2FA) is available and recommended for Pro accounts
  • Deleting your account permanently removes all conversation history — no recovery option

Use Google Login If You Can

Authenticating with Google takes 15 seconds and skips email verification entirely. It also means one fewer password to manage. If your organization uses Google Workspace, your work email works perfectly — and you can later connect Claude to a Team workspace under the same login.

Plan Comparison: Free vs. Pro vs. Team

FeatureFreePro ($20/mo)Team ($25/user/mo)
Primary model accessClaude 3.5 HaikuClaude 3.5 Sonnet + OpusClaude 3.5 Sonnet + Opus
Daily message limit~30-40 messages~5x free tier limitHigher than Pro
Projects featureNoYesYes
File uploadsLimitedUp to 10 files/conversationUp to 10 files/conversation
Context window200K tokens200K tokens200K tokens
Priority access during high trafficNoYesYes
Shared team workspacesNoNoYes
Admin controlsNoNoYes
Minimum seatsN/AN/A5 users
BillingFreeMonthly or annualPer seat, annual available
Claude plan comparison as of early 2025. Message limits are approximate — Anthropic adjusts them based on server load.

Understanding Claude's Models

Every conversation you start with Claude runs on a specific model — and which model you're using has a direct impact on response quality, speed, and capability. The model selector appears at the top of each new conversation window. Free users see Claude 3.5 Haiku as their primary option. Pro users can switch between Haiku, Sonnet, and Opus. Think of these as a speed-to-power spectrum: Haiku is fast and efficient, Sonnet balances speed and intelligence, and Opus is the most capable but slowest model Anthropic offers.

For most professional tasks — writing, analysis, summarization, brainstorming — Claude 3.5 Sonnet is the right choice. It's what Anthropic positions as their flagship for everyday use. Opus is worth switching to for genuinely complex reasoning tasks: multi-step analysis, code architecture decisions, or processing a 150-page document where you need deep comprehension. Haiku shines when you need fast, repeated outputs — running the same prompt against multiple inputs, quick rewrites, or simple Q&A. Choosing the wrong model wastes either time (Opus for simple tasks) or quality (Haiku for complex ones).

  1. Open a new conversation by clicking the pencil/compose icon in the sidebar
  2. Look for the model name displayed at the top center of the chat window
  3. Click the model name to open the selector dropdown
  4. Choose your model based on task complexity — Sonnet for most work, Opus for deep analysis
  5. Your model choice applies only to that conversation — each new conversation defaults to your last selection
ModelBest ForSpeedAvailable On
Claude 3.5 HaikuQuick tasks, high-volume use, simple Q&AFastestFree + Pro
Claude 3.5 SonnetWriting, analysis, coding, most professional workFastPro + Team
Claude 3 OpusComplex reasoning, long document analysis, difficult problemsSlowestPro + Team
Claude model quick-reference. Sonnet is the default for Pro users and the right starting point for most tasks.

The 200K Token Context Window

Every Claude model offers a 200,000 token context window — roughly 150,000 words, or about 500 pages of text. This is one of Claude's genuine advantages over ChatGPT's standard models. You can paste an entire business report, a full codebase, or months of email threads into a single conversation. Most users never hit this limit in normal use.

The Projects Feature (Pro and Team Only)

Setting up a Project for a recurring work task

Prompt

I'm a marketing manager. I'll be using this project to draft and refine LinkedIn content for our B2B software company. Our tone is confident but never salesy. We target CTOs and VPs of Engineering. Posts should be under 200 words and end with a question to drive comments.

AI Response

Got it. For this project I'll treat every piece of LinkedIn content with these constraints by default: B2B software audience (CTOs, VPs of Engineering), confident and non-promotional tone, under 200 words, closing question included. Drop in your raw ideas or topics and I'll shape them to fit. What's the first post you want to work on?

How Projects Work

Projects solve Claude's biggest limitation for professional users: the lack of persistent memory. Without Projects, every conversation starts from zero — Claude has no idea who you are, what your company does, or what style you prefer. Projects let you store a set of instructions and uploaded documents that Claude reads at the start of every conversation within that project. This is the closest Claude currently gets to 'remembering' you. A Project functions like a persistent briefing document that travels with every conversation you have inside it.

Create a Project by clicking 'New Project' in the sidebar. Give it a name (e.g., 'Q1 Marketing Copy' or 'Client Analysis — Acme Corp'), then add your project instructions in the text field provided. These instructions can include your role, your company context, preferred output formats, tone guidelines, and any recurring constraints. You can also upload reference files — brand guidelines, style guides, product specs, org charts — up to the file size limits. Every conversation you start inside that Project inherits this context automatically, without you re-typing it.

Projects Are Not a Memory System

Projects store instructions and files you manually add — Claude does not automatically learn from your conversations and update the project. If a conversation produces something important (a key decision, a finalized document), you need to manually copy it back into the project instructions or files. Treat Projects as a briefing folder you maintain, not a brain that grows on its own.

Quick Setup Task: Your First Project

Create a Working Project in Claude

Goal: Have a functioning Project with custom instructions and at least one conversation started inside it, ready for real work.

1. Log into claude.ai and confirm you're on a Pro or Team plan (Projects require paid access). 2. Click 'New Project' in the left sidebar — it appears below your conversation list. 3. Name the project after a real recurring task you have: e.g., 'Weekly Report Drafts' or 'Client Email Templates'. 4. In the Project Instructions field, write 2-3 sentences describing your role, your audience, and your preferred output style — be specific (job title, industry, company size if relevant). 5. Upload one reference document if you have one ready: a style guide, a past report you liked, or a product one-pager. Accepted formats include PDF, DOCX, and TXT. 6. Start a new conversation inside the project by clicking the compose icon while inside the Project view. 7. Send your first message — notice you don't need to re-explain your context. Verify Claude's response reflects the instructions you set.

Account Setup Cheat Sheet

  • Sign up at claude.ai — Google login is fastest, no credit card needed for free tier
  • Free plan: Claude 3.5 Haiku, ~30-40 messages/day, no Projects
  • Pro plan: $20/month, Claude 3.5 Sonnet + Opus, Projects, priority access
  • Team plan: $25/user/month, minimum 5 seats, adds shared workspaces and admin controls
  • Model selector is per-conversation — choose Sonnet for most work, Opus for complex analysis
  • Context window is 200K tokens (≈150K words) across all models and plans
  • Projects store persistent instructions + files — Pro and Team only
  • Projects do NOT auto-update from conversations — maintain them manually
  • Enable 2FA in account settings for security, especially on Pro accounts
  • Account deletion is permanent — export anything important before deleting

Key Takeaways

  1. Claude and ChatGPT are direct competitors with identical Pro pricing ($20/month) — Claude's main differentiator at this tier is the 200K token context window and the Projects feature.
  2. Model choice matters: Haiku for speed, Sonnet for most professional tasks, Opus for complex reasoning. The wrong choice costs you either time or quality.
  3. The free tier is genuinely usable for occasional tasks, but the lack of Projects makes it inefficient for any recurring professional workflow.
  4. Projects are the most important setup decision for professional users — configure one correctly and you eliminate the need to re-explain your context in every conversation.
  5. Claude's interface is intentionally minimal — don't look for extensive settings menus. The power is in how you prompt, not in configuration toggles.

Navigating the Claude Interface

With your account created and your plan chosen, you're looking at the Claude interface for the first time. It's deliberately minimal — a text input, a conversation thread, and a sidebar. That simplicity is intentional. Unlike some AI tools that bury you in buttons and modes, Claude is designed around conversation. But minimal doesn't mean featureless. Knowing where everything lives and what it actually does saves you from wasting time clicking around when you should be prompting.

The Sidebar: Projects and Conversation History

The left sidebar holds two things: your conversation history and Projects. Every chat you start is saved automatically and searchable by keyword. Claude Pro users can also create Projects — persistent workspaces where Claude retains context across multiple sessions. A Project for "Q3 Marketing Campaign" remembers your brand voice guidelines, your target audience notes, and your previous outputs every time you return. Free users get conversation history but no Projects, which means each new chat starts from scratch without any carry-over memory.

  • Conversation history is searchable — use keywords from your original prompt to find old chats
  • Projects (Pro only) maintain persistent memory and custom instructions across sessions
  • Each new conversation outside a Project starts with zero memory of previous chats
  • You can rename conversations manually — do this for anything you'll want to find later
  • Archived chats are not deleted; they're hidden from the main sidebar view
  • Projects support uploaded files that stay available for the lifetime of the project

Name Your Conversations Immediately

Claude auto-generates conversation names, and they're often generic. Click the name in the sidebar and rename it to something meaningful — "Website Copy Draft v1" beats "Help with writing" when you're searching three weeks later. Takes five seconds; saves five minutes of scrolling.

Claude Plans at a Glance

FeatureFreePro ($20/mo)Team ($25/user/mo)
Model accessClaude (limited)Claude 3.5 Sonnet + OpusClaude 3.5 Sonnet + Opus
Usage limitsLow daily cap5x more than FreeHigher shared pool
ProjectsNoYesYes (shared)
File uploadsLimitedUp to 10 files/chatUp to 10 files/chat
Priority accessNoYes (peak hours)Yes
Admin controlsNoNoYes
Context windowShorter200,000 tokens200,000 tokens
API accessNoNo (separate)No (separate)
Claude plan comparison — accurate as of mid-2025. Check anthropic.com/pricing for current figures.

Understanding Context Windows

The 200,000-token context window on Claude Pro is one of its biggest practical advantages. A token is roughly 0.75 words in English, so 200,000 tokens handles approximately 150,000 words — a full novel, or an entire company's quarterly report. This matters because Claude can hold your entire conversation, plus any uploaded documents, in working memory simultaneously. You can paste in a 50-page contract and ask questions about specific clauses without Claude losing track of the beginning by the time it reaches the end.

Context windows reset with every new conversation. Whatever you built up across a long chat — the background you provided, the decisions made, the style Claude adopted — disappears when you click "New Chat." This is why Projects matter for ongoing work. Think of a Project as a persistent context container. Think of a standard conversation as a whiteboard that gets erased when you leave the room. Choosing the wrong one for a task costs you significant setup time.

What Counts Toward Your Context Window

Every token in the conversation counts — your prompts, Claude's responses, uploaded file contents, and system instructions in Projects. A long conversation with a large uploaded document can approach the limit. Claude will warn you when you're getting close. If you hit the limit, start a new conversation and paste in only the essential context.

File Uploads: What Claude Can Actually Read

Claude accepts more file types than most users realize. You can upload PDFs, Word documents, spreadsheets, plain text files, code files, and images. For images, Claude performs genuine visual analysis — it reads charts, interprets diagrams, and extracts text from screenshots. This isn't decorative multimodal capability; it's practically useful for analyzing competitor screenshots, reviewing presentation slides, or pulling data from a chart someone sent as a PNG instead of a proper dataset.

File TypeWhat Claude Does With ItBest Use Case
PDFExtracts and reads all text contentContracts, reports, research papers
DOCXReads text and basic formattingDraft review, editing, rewriting
XLSX / CSVReads data as structured tableData summaries, anomaly spotting, formula explanation
PNG / JPGVisual analysis + text extraction (OCR)Screenshots, charts, diagrams, slide decks
TXT / MDDirect text readingNotes, transcripts, raw content
Code files (.py, .js, etc.)Reads and understands code structureCode review, debugging, documentation
Claude file upload capabilities by format — practical reference for deciding how to share information.

Your First Real Prompt

Practical First Prompt — Summarizing an Uploaded Document

Prompt

I've uploaded our Q2 sales report (PDF). Please give me: 1. A 3-sentence executive summary 2. The top 3 performing product lines by revenue 3. Any figures that look anomalous or worth investigating Write for a non-technical executive audience. Be direct — no filler.

AI Response

**Executive Summary** Q2 revenue reached $4.2M, up 11% quarter-over-quarter, driven primarily by Enterprise SaaS subscriptions. Gross margin improved to 68% despite higher customer acquisition costs in the SMB segment. The quarter ended with a healthy pipeline of $12M, though two large deals slipped into Q3. **Top 3 Product Lines by Revenue** 1. Enterprise SaaS — $2.1M (50% of total) 2. Professional Services — $890K (21%) 3. Starter Plans — $640K (15%) **Anomalies Worth Investigating** - SMB churn spiked to 8.3% in June vs. 4.1% average for H1 — no explanation given in the report - Professional Services margin dropped 12 points vs. Q1; likely tied to the two delayed implementations mentioned on p.14 - Hardware accessory revenue is missing from the P&L breakdown but appears in the appendix totals

Custom Instructions and System Prompts

Inside a Project, you can set custom instructions — a block of text Claude reads before every conversation in that Project. This is where you define standing context: your role, your company, your preferred output format, your audience. Done well, custom instructions eliminate the repetitive setup text you'd otherwise paste at the start of every prompt. A consultant might set instructions that define their client's industry, the engagement's goals, and the required deliverable format. Every prompt in that Project inherits that context automatically.

Custom instructions work best when they're specific and behavioral, not vague and aspirational. "Be helpful and professional" does almost nothing — Claude already behaves that way. "Always respond in bullet points unless I ask for prose. Use British English. When reviewing documents, flag legal and financial risks separately from operational risks" — that's actionable. Instructions that specify format, audience, vocabulary, and scope produce consistent, on-brand outputs without extra prompting effort every session.

Custom Instructions Don't Replace Good Prompting

Custom instructions set defaults — they don't guarantee quality. If your prompt is vague, Claude will still produce vague output, just formatted the way your instructions specify. Instructions handle the 'how to respond' layer. Your actual prompt still needs to handle the 'what to do' layer clearly. Treat them as two separate levers, not a substitute for each other.

Quick Setup Task: Create Your First Project

Build a Working Project with Custom Instructions

Goal: A configured Project with custom instructions that produces correctly formatted, contextually appropriate output without manual setup prompts.

1. From the Claude sidebar, click 'New Project' and name it after a real recurring work area (e.g., 'Client Reports', 'Weekly Comms', 'Product Analysis'). 2. Open the Project settings and locate the 'Custom Instructions' field. 3. Write 3-5 sentences covering: your role, your primary audience for outputs, and one specific formatting preference (e.g., 'always use numbered lists for recommendations'). 4. Save the instructions and start a new conversation inside the Project. 5. Type a simple test prompt relevant to your work area — ask Claude to produce something you'd actually use. 6. Review the output: does it reflect your instructions without you having to repeat them? 7. Refine one instruction based on what the output got wrong or missed, then re-run the same prompt to confirm the change worked.

Interface Quick-Reference Cheat Sheet

  • New Chat button — starts a blank conversation with no memory of previous chats
  • New Project — creates a persistent workspace with custom instructions and file storage
  • Paperclip icon — attach files (PDF, images, spreadsheets, code, text)
  • Rename conversation — click the chat title in the sidebar to edit
  • Retry button — regenerates Claude's last response with a different output
  • Copy response — copies Claude's full reply as plain text to your clipboard
  • Thumbs up / down — sends feedback to Anthropic; doesn't affect your conversation
  • Model selector (Pro) — switch between Claude 3.5 Sonnet and Claude 3 Opus mid-conversation
  • Project settings — access custom instructions, uploaded project files, and sharing options (Team plan)

Making Claude Work for You: Settings, Habits, and First Wins

Your account is live. Now the difference between casual users and power users comes down to three things: knowing which settings actually matter, building a consistent prompting habit, and understanding Claude's guardrails so you never waste a conversation hitting a wall. This section covers the practical configuration layer most users skip entirely — and shows you how to get a real, keeper output from Claude in your first session.

Profile and Memory Settings That Actually Matter

Claude.ai's profile settings let you tell Claude who you are before you type a single prompt. Fill in your role, your industry, and how you prefer responses formatted. Claude uses this context in every conversation — a marketing director who sets her profile gets tighter, business-oriented answers than someone with a blank profile asking the identical question. This isn't cosmetic. It compresses the setup work you'd otherwise do manually at the start of each chat.

  • Profile name and role: Claude uses this to calibrate formality and assumed knowledge level
  • Response style preference: choose concise, balanced, or detailed as your default
  • Projects (Claude.ai Pro): persistent memory spaces that retain context across sessions
  • Custom instructions: plain-English rules Claude applies to every response you receive
  • Language preference: set your working language once, not per conversation

Write Your Custom Instructions Like an Onboarding Doc

Treat the custom instructions field as a briefing for a new assistant. Include: your job title, your industry, your preferred output format (bullets vs. prose), any jargon to avoid, and your typical audience. Sixty words here saves you 10 minutes of context-setting per week.
SettingWhere to Find ItWhat It DoesPriority
Profile / RoleProfile menu → Edit ProfileShapes tone and assumed expertiseHigh
Custom InstructionsProfile menu → Custom InstructionsApplies rules to every conversationHigh
Response StyleProfile menu → PreferencesSets default length and formatMedium
ProjectsLeft sidebar (Pro only)Retains context across sessionsHigh (Pro)
Conversation HistorySettings → Data ControlsToggle saving chat history on/offMedium
Key Claude.ai settings and where to find them

Understanding Claude's Boundaries

Claude will decline certain requests — not randomly, but according to Anthropic's published usage policies. Knowing the pattern saves frustration. Claude won't generate content that facilitates real harm, produce deceptive material designed to mislead specific people, or write detailed instructions for dangerous activities. These refusals are consistent and intentional. What surprises new users is that Claude will push back on ambiguous requests too, often asking a clarifying question rather than guessing wrong.

When Claude declines, it tells you why — briefly. That explanation is useful. It usually signals how to reframe the prompt legitimately. Asking Claude to 'write a phishing email' fails. Asking Claude to 'write a security awareness training example showing phishing tactics employees should recognize' works, because the intent is defensive, not deceptive. Context and stated purpose change outcomes significantly.

Prompt PatternLikely OutcomeFix
Vague harmful intentDecline with explanationAdd legitimate context and purpose
Ambiguous requestClarifying question from ClaudeSpecify your actual goal upfront
Sensitive topic, no contextCautious or hedged responseState your role and why you need it
Requesting real personal dataDeclineUse anonymized or fictional examples
Clear, benign professional taskFull, direct responseNo fix needed — proceed
Common friction points and how to resolve them

Claude's Refusals Are Not Errors

A declined prompt isn't a bug or a failure of your account setup. It's Claude's policy layer functioning as designed. Anthropic publishes its usage guidelines at anthropic.com/usage-policy — worth a 5-minute read so you know the actual boundaries, not the rumored ones.

Your First Real Prompt Session

The fastest way to calibrate Claude to your work is to give it a task you'd normally spend 30-45 minutes on. Not a test. Not 'write me a poem.' Give it a real deliverable — a draft email to a difficult stakeholder, a summary of a document you paste in, a structured agenda for a meeting next week. Real inputs produce outputs you can actually evaluate and keep. That feedback loop, repeated over your first five sessions, builds your prompting instincts faster than any tutorial.

First Real Work Prompt — Meeting Agenda

Prompt

I'm a [your role] at a [your industry] company. I need a structured 60-minute agenda for a project kickoff meeting with 8 stakeholders. The project goal is [your project]. Attendees include the project sponsor, two engineers, a designer, and three business stakeholders. Format as a table with time blocks, agenda item, owner, and desired outcome columns.

AI Response

| Time | Agenda Item | Owner | Desired Outcome | |------|-------------|-------|-----------------| | 0:00–0:05 | Welcome & introductions | Project Sponsor | Everyone knows each other's role | | 0:05–0:15 | Project overview & business case | Project Manager | Shared understanding of the 'why' | | 0:15–0:25 | Scope and deliverables walkthrough | Lead Engineer | Agreement on what's in/out of scope | | 0:25–0:35 | Roles and responsibilities | Project Manager | Clear ownership for each workstream | | 0:35–0:45 | Timeline, milestones, and risks | Designer + Engineers | Realistic schedule with flagged risks | | 0:45–0:55 | Open questions and decisions needed | All | Blockers surfaced and assigned | | 0:55–1:00 | Next steps and follow-up actions | Project Manager | Everyone leaves with a clear action |

Never Paste Sensitive or Confidential Data Into Claude.ai (Free/Pro)

Claude.ai's consumer tiers are not approved for confidential business data, personal health information, or anything under NDA. If your organization needs Claude for sensitive work, that requires Anthropic's Claude for Enterprise or API access with a signed data processing agreement. When in doubt, anonymize before you paste.
Build Your Claude Starter Kit

Goal: Leave this task with a completed custom instructions profile, one real work output you can use, and a personalized list of Claude use cases for your role.

1. Log into Claude.ai and open Profile Settings. Fill in your job title, industry, and one sentence about your typical work tasks. 2. Navigate to Custom Instructions. Write 3–5 rules for how Claude should respond to you — include preferred format, tone, and one thing Claude should always or never do. 3. Start a new conversation. Paste a real work document (a report, an email thread, meeting notes) and ask Claude to summarize it in five bullet points for a busy executive. 4. Review the summary. Ask Claude to regenerate it with one specific change — shorter, more formal, or with a recommendation added. 5. Copy the final output into a doc, note, or email draft you'll actually use. This is your first Claude-assisted deliverable. 6. Start a second conversation. Ask Claude: 'What are three ways I could use you to save time in my specific role?' — filling in your actual role. Save the response.

Quick-Reference Cheat Sheet

  • Free tier: claude.ai, no credit card, limited to Claude 3.5 Haiku with usage caps
  • Pro tier: $20/month, full Claude 3.5 Sonnet and Opus access, Projects, higher limits
  • Custom Instructions: set once in profile, apply to every conversation automatically
  • Projects (Pro): persistent memory spaces — use one per major client or workstream
  • Claude won't save conversation history if you disable it in Data Controls
  • Refusals come with explanations — use that explanation to reframe your prompt
  • Never paste confidential or regulated data into consumer Claude tiers
  • Paste real work into Claude from session one — fake prompts produce fake calibration
  • Claude API (separate from claude.ai) is available at console.anthropic.com for developers

Key Takeaways

  1. Your profile and custom instructions are the highest-leverage settings in your account — fill them in before your first real session
  2. Claude's refusals follow a consistent policy logic; reframing with context and purpose resolves most friction
  3. The Free tier is a fully functional starting point; upgrade to Pro when you hit usage limits or need Projects
  4. Your first five real-work sessions with Claude calibrate your prompting instincts faster than any passive learning
  5. Data hygiene matters from day one — anonymize sensitive content before it enters any consumer AI tool
Knowledge Check

Where in Claude.ai do you write rules that apply automatically to every conversation you have?

A colleague pastes a client's confidential contract into Claude.ai Pro and asks Claude to summarize it. What is the core problem with this approach?

You ask Claude to 'write a deceptive sales email that hides the product's limitations.' Claude declines. What is the most effective next step?

Which Claude.ai feature, available on the Pro plan, retains context and files across multiple sessions for a specific project or client?

A new user sets up their Claude profile but leaves Custom Instructions blank, then wonders why Claude's responses feel generic. What is the most likely cause?

Sign in to track your progress.