Skip to content

Master Claude

Claude Chat: Fundamentals Sample Lesson

How Claude thinks

How Claude thinks — Quick Check

Prompt anatomy — Quick Check

Controlling output format

Controlling output format — Quick Check

Iterating effectively

Iterating effectively — Quick Check

Prompt rewrite exercise

Prompt rewrite exercise — Quick Check

Claude Chat: Intermediate

System prompts & personas

System prompts & personas — Quick Check

Few-shot prompting

Few-shot prompting — Quick Check

Chain-of-thought prompting

Chain-of-thought prompting — Quick Check

XML tags for structured output

XML tags for structured output — Quick Check

Working with documents

Working with documents — Quick Check

Skills & custom instructions

Skills & custom instructions — Quick Check

Claude Chat: Applied Projects

Client email workflow

Client email workflow — Quick Check

Research & summarization

Research & summarization — Quick Check

SOPs & checklists system

SOPs & checklists system — Quick Check

Multi-perspective prompting

Multi-perspective prompting — Quick Check

Claude Code: Foundations

What Claude Code is

What Claude Code is — Quick Check

Project context & CLAUDE.md

Project context & CLAUDE.md — Quick Check

Writing code with Claude

Writing code with Claude — Quick Check

Debugging with Claude

Debugging with Claude — Quick Check

Working with git

Working with git — Quick Check

Claude Code: Building Projects

Scaffold a new app

Scaffold a new app — Quick Check

Data scripts & ETL

Data scripts & ETL — Quick Check

API integrations

API integrations — Quick Check

Front-end components

Front-end components — Quick Check

Code review & security

Code review & security — Quick Check

Claude Code: Advanced

CLAUDE.md mastery

CLAUDE.md mastery — Quick Check

MCP in Claude Code

MCP in Claude Code — Quick Check

Testing strategies

Testing strategies — Quick Check

Agents & Cowork: How Agents Work

What makes an agent

What makes an agent — Quick Check

Tools, actions & environment

Tools, actions & environment — Quick Check

MCP — the protocol

MCP — the protocol — Quick Check

Trust & human-in-the-loop

Trust & human-in-the-loop — Quick Check

Planning long tasks

Planning long tasks — Quick Check

Agents & Cowork: Connecting Tools

Gmail agent — Quick Check

Calendar agent — Quick Check

Google Drive agent

Google Drive agent — Quick Check

Web agent — Quick Check

Chaining tools — Quick Check

Build a custom MCP server

Build a custom MCP server — Quick Check

Agents & Cowork: Claude Cowork

What Cowork is — Quick Check

Delegating your first task

Delegating your first task — Quick Check

Automating recurring workflows

Automating recurring workflows — Quick Check

Capstone — build your agent workflow

Capstone — build your agent workflow — Quick Check

Multi-perspective prompting — Quick Check

Master Claude
Claude Chat: Applied Projects
Multi-perspective prompting
Multi-perspective prompting — Quick Check

Time limit: 0

Quiz Summary

0 of 3 Questions completed

Questions:

Information

You have already completed the quiz before. Hence you can not start it again.

Quiz is loading…

You must sign in or sign up to start the quiz.

You must first complete the following:

Results

Quiz complete. Results are being recorded.

Results

0 of 3 Questions answered correctly

Your time:

Time has elapsed

You have reached 0 of 0 point(s), (0)

Earned Point(s): 0 of 0, (0)
0 Essay(s) Pending (Possible Point(s): 0)

Categories

Not categorized 0%

Review
Answered
Correct
Incorrect

Question 1 of 3

1. Question

Why does assigning Claude a role (‘devil’s advocate’) produce better critical feedback than ‘what are the downsides?’

It's longer
Correct Incorrect Correct answer

The role gives Claude permission to be more extreme and direct rather than balanced
Correct Incorrect Correct answer

Claude can only criticize when given a role
Correct Incorrect Correct answer

It's a trick to bypass Claude's guidelines
Correct Incorrect Correct answer

Correct

Incorrect
Question 2 of 3

2. Question

The client perspective prompt is most useful before:

Starting a project
Correct Incorrect Correct answer

Sending a proposal or major client communication
Correct Incorrect Correct answer

Writing an SOP
Correct Incorrect Correct answer

Doing a site audit
Correct Incorrect Correct answer

Correct

Incorrect
Question 3 of 3

3. Question

Running three perspectives in sequence (supporter, skeptic, pragmatist) is useful because:

It gives Claude more to work with
Correct Incorrect Correct answer

It surfaces both the best case and worst case, then a grounded recommendation — covering the full decision space
Correct Incorrect Correct answer

It's faster than one prompt
Correct Incorrect Correct answer

Claude performs better in threes
Correct Incorrect Correct answer

Correct

Incorrect