Welcome to the Claude Bible

A practical AI Con Todo guide for non-technical people who want to understand Claude as a full work platform: chat, files, projects, artifacts, memory, skills, connectors, Chrome, Cowork, Code, and Design.

Follow the course

Learn by making.

Art

Artifacts

Create useful outputs.

Skills

Reuse workflows.

App

Connectors

Bring in context safely.

The Claude loop

AskDescribe the outcome and audience.

Add contextUse files, projects, memory, search, or connectors only when needed.

CreateMake a memo, artifact, spreadsheet, presentation, or plan.

ReviewVerify facts, privacy, brand, and approval points.

What this guide teaches

Everyday work

Chat, write, analyze files, search, create artifacts.

Organization

Projects, memory, reusable prompts, and context hygiene.

Power features

Skills, connectors, Chrome, Cowork, Code, and Design.

Safety

Least context, explicit approvals, verification, team rules.

Claude Safety Checklist

I know the outcome and audience.I choose the smallest useful context.I review sensitive data before upload or connector use.I verify important outputs before acting.

Ask Claude This

prompt

I am non-technical. Help me choose the right Claude workflow.

Goal:
[what I need]

Inputs:
[files, notes, links, tools]

Output:
[document / artifact / spreadsheet / code / design / plan]

Before working, tell me:
1. Which Claude surface to use
2. What context you need
3. Whether a Skill, connector, or artifact would help
4. What I should verify before using the result

Fast Mental Model

Feature	Plain English
Projects	Organized context for ongoing work.
Artifacts	Standalone visual, document, code, or interactive outputs.
Skills	Reusable workflows Claude can apply automatically.
Connectors	External context and tools, including remote MCP patterns.

Course Path

10-Day Claude Power User Path

This is the general Claude course for non-technical people: chat, files, projects, memory, skills, connectors, Chrome, Cowork, artifacts, research, and safe delegation.

The promise

Day 1: learn Claude chat, plans, files, web search, and safe prompting.Day 2: create a useful deliverable: memo, deck, spreadsheet, artifact, or research plan.Day 3: organize work with Projects, memory, and reusable prompts.Days 4-10: add Skills, connectors, Chrome, Cowork, Design, Code, and governance.

10-day path

Day	Level	Module	Outcome
1	Beginner	Claude Basics	Understand chat, files, web search, models, and plans.
2	Beginner	First Deliverable	Create a memo, document, deck outline, spreadsheet, or artifact.
3	Beginner	Projects + Memory	Keep context organized across workstreams.
4	Builder	Artifacts	Create interactive, visual, or document-style outputs.
5	Builder	Skills	Use reusable procedures and company standards.
6	Builder	Connectors	Bring Google Workspace, Slack, Microsoft, and remote MCP context in.
7	Power	Claude for Chrome	Use Claude alongside browser work.
8	Power	Cowork	Delegate knowledge work through a workspace assistant.
9	Advanced	Code + Design	Move from idea to design and build workflows.
10	Advanced	Team Playbook	Create safe rules for skills, connectors, artifacts, and delegation.

Part 1

What Claude Is in 2026

Claude is Anthropic's AI assistant for writing, analysis, coding help, files, web search, artifacts, data visualization, skills, connectors, and increasingly agentic work through products like Cowork, Code, and Design.

Use it for

Brainstorming, writing, editing, research, data analysis, document work, artifacts, coding, and planning.

Do not use it as

A replacement for professional review, admin approvals, security rules, or final factual verification.

Plan mental model

Plan	Plain meaning	Notable access
Free	Basic Claude access.	Chat, files, search, code/data, desktop extensions, Slack/Google Workspace, connectors.
Pro	Everyday productivity.	More usage, Claude Code, Cowork, projects, research, memory, more models, Excel, Chrome.
Max	Higher usage.	5x-20x Pro usage and early access.
Team/Enterprise	Managed work.	Admin controls, shared workflows, governance, and workspace features.

I know whether my task is chat, artifact, skill, connector, Cowork, Code, or Design work.

Part 2

Projects, Memory, Files, and Search

Claude becomes more useful when you give it the right context and organize that context. Projects keep related work together, memory helps across conversations, files let Claude analyze your materials, and search brings in current information.

Context ladder

Context	Use when	Rule
Prompt	Small one-off task.	Keep it short and specific.
File upload	Claude needs a document, image, sheet, or PDF.	Remove sensitive data first.
Project	Ongoing workstream.	Store instructions and related materials together.
Memory	Preference or durable context.	Review and correct it.
Search/connectors	Current or private information.	Ask for sources and limits.

Context prompt

prompt

Before answering, tell me what context you need.

Classify each input as:
- Required
- Helpful
- Not needed
- Sensitive, do not upload

Then give me the smallest safe input list for this task.

I give Claude the smallest useful context, not everything I have.

Part 3

First Useful Claude Deliverable

A beginner should create something useful by day 2: an executive memo, training plan, spreadsheet, artifact, research brief, or polished document.

Starter deliverables

Executive memo

Decision, options, risks, recommendation.

Document edit

Improve tone, clarity, structure, and next steps.

Data analysis

Summarize spreadsheet or CSV findings.

Artifact

Turn a concept into a visual, checklist, simulator, or prototype.

First task prompt

prompt

I am non-technical. Help me create one useful deliverable in Claude.

Goal:
[what I need]

Audience:
[who will use it]

Inputs:
[files, notes, links, context]

Output format:
[memo / checklist / table / artifact / deck outline / spreadsheet]

Make it practical, clear, and ready for review. End with what I should verify before using it.

I created one useful Claude deliverable before studying advanced features.

Part 4

Artifacts and Visual Work

Artifacts are Claude outputs that are easier to inspect, edit, and reuse: documents, code, visual prototypes, dashboards, diagrams, checklists, and interactive tools.

Artifact chooser

Need	Artifact type	Example
Explain a process	Checklist or guide	Course module, SOP, onboarding plan.
Show a concept	Visual mockup	Landing page, dashboard, diagram.
Let user interact	Prototype	Calculator, quiz, simulator.
Organize analysis	Table or dashboard	Research matrix, project tracker.

Artifact prompt

prompt

Create an artifact for this task.

Purpose:
[what it should help me do]

Audience:
[who will use it]

Artifact type:
[document / visual / checklist / prototype / dashboard]

Keep it simple, readable, and useful for a non-technical person. After creating it, explain how I should review it.

I know when to ask for an artifact instead of a normal answer.

Part 5

Skills: Reusable Claude Workflows

Skills let Claude apply reusable procedures, standards, examples, and resources automatically across Claude.ai, Claude Code, and the API.

Skill ideas

Brand writer

Use your voice, formatting, and examples for every content request.

Finance workflow

Follow a modeling, reporting, or comps-analysis process.

Meeting notes

Turn transcripts into decisions, tasks, and follow-ups.

Course creator

Make lessons, prompts, SOPs, and quizzes.

Skill prompt

prompt

Help me design a Claude Skill for a repeated workflow.

Workflow:
[describe repeated task]

Include:
1. When Claude should use it
2. Step-by-step instructions
3. Required examples or reference files
4. Output format
5. Quality checklist
6. What Claude should avoid

I can identify repeated work that should become a Skill.

Part 6

Connectors, Chrome, Slack, and Microsoft 365

Claude connectors let Claude bring in external context and tools. Claude also has product surfaces for Chrome, Slack, Microsoft 365, Google Workspace, remote MCP connectors, and desktop extensions.

Connector map

Connection	Use when	Safety rule
Google Workspace	Docs, Drive, Gmail, Calendar context.	Connect only what the task needs.
Slack	Team context and collaboration.	Summarize before acting.
Microsoft 365	Docs, email, calendar, Excel workflows.	Respect workspace policy.
Chrome	Help with active web browsing.	Do not expose passwords or sensitive pages.
Remote MCP	Custom internal tools and context.	Advanced: admin/security review first.

Connector prompt

prompt

Before using any connected tool, explain:
1. Which connector you need
2. What information you will read
3. Whether you will take any action
4. What permission or approval is required
5. What privacy risk I should consider

I know connectors are powerful context, not magic permission to act.

Part 7

Cowork, Code, and Design

Claude now has several product surfaces: Claude chat for general work, Claude Cowork for knowledge work delegation, Claude Code for building software, and Claude Design for visual work.

Surface chooser

Surface	Best for	Beginner advice
Claude chat	Thinking, writing, files, artifacts, research.	Start here.
Cowork	Delegating office workflows and file-based work.	Use when a task has multiple steps.
Claude Code	Repos, apps, tests, GitHub, code review.	Use when files live in a project.
Claude Design	Visual concepts, decks, prototypes, brand work.	Use when the output must be seen.

Delegation prompt

prompt

Tell me which Claude surface fits this task best: chat, Cowork, Code, or Design.

Task:
[describe task]

Consider:
1. Does it need files?
2. Does it need code?
3. Does it need visual design?
4. Does it need connected apps?
5. Does it need multi-step delegation?

Then give me the safest beginner workflow.

I know which Claude surface to use for each type of work.

Part 8

Research, Spreadsheets, Documents, and Presentations

Claude can help with research, documents, data visualization, spreadsheets, presentations, and file transformations. Skills and connectors make these more consistent.

Business workflows

Workflow	Output	Review habit
Research brief	Summary, sources, options, risks.	Verify citations and dates.
Spreadsheet analysis	Findings, formulas, charts.	Check formulas and assumptions.
Presentation	Slides, story, speaker notes.	Check brand and data.
Document rewrite	Clearer version with structure.	Review tone and meaning.

Research prompt

prompt

Create a research brief for a non-technical decision maker.

Topic:
[topic]

Output:
1. Executive summary
2. Key findings
3. Source table
4. Options
5. Risks and assumptions
6. Recommendation
7. What to verify before acting

I always ask Claude what to verify before relying on the output.

Part 9

Safety, Privacy, and Team Governance

Claude gets more useful as you add context, Skills, connectors, and product surfaces. The safety habit is simple: least context, clear approvals, and review before acting.

Governance map

Area	Rule	Owner
Projects	Keep only relevant files and instructions.	Project owner.
Memory	Review and correct stale assumptions.	User.
Skills	Test before team use.	Skill owner.
Connectors	Use minimum access needed.	User/admin.
Cowork/agents	Define approval points before work starts.	User/team lead.

Audit prompt

prompt

Audit my Claude workflow for safety and usefulness.

Review:
1. Context I provide
2. Projects and files
3. Memory risks
4. Skills I use
5. Connectors and permissions
6. Artifacts or outputs that need review
7. Where a human approval should be required

I have a safety checklist for Claude workflows.

Reference

Official Sources and Research Notes

This Bible is based on current Claude and Anthropic product pages checked on June 19, 2026.

Source	What it supports
Claude product page	Plans, core use cases, free/pro/max features, projects, memory, search, code/data, connectors, Cowork, Code, Design, Excel, Chrome.
Claude Skills	Reusable procedures, built-in workflows, company-specific and individual skills, SKILL.md concept, cross-surface use.
Claude Connectors	External tools and context, connector mental model, remote MCP reference.
Claude for Chrome	Browser-side Claude usage and web workflow positioning.
Claude Cowork	Knowledge-work delegation surface and relationship to general Claude use.

Course stance: Claude chat first, then Projects, Artifacts, Skills, Connectors, Cowork, Code, and Design as leverage layers.