Good questions.
Start here.
From your first conversation to a real problem solved. Clear steps and hands-on practice to make Claude a helpful part of your day.
“Help me write an email.”
Write a friendly meeting invitation to my teammates. We’ll discuss the project on Friday afternoon. Keep it under 100 words.
Audience + goal + constraintsEveryone starts somewhere.
Start with what you want to do. Build one useful skill at a time.
Getting started
Meet Claude and get your first useful answer.
Work & creativity
An email, an outline, a little more room in your day.
Claude Code
Install, plan, edit, test, and connect external services.
API development
Call Claude, use external APIs, and run on Workers.
Claude Desktop
Install the app, work with files, and connect your tools.
Understand the task. Then build together.
Install Claude Code and sign in
Choose an installer, connect your account, and open a practice project.
Before changing code, make the task clear
Understand the project, agree on scope, and define success.
Give your project lasting instructions
Keep build commands, conventions, and task context close to the code.
Plan, edit, test, and review a change
Turn a small bug report into a change you can verify and keep.
Connect Claude Code to an external service
Add a real MCP endpoint, authenticate, and verify one read-only tool.
A handbook that keeps its sources close.
Explore the official timeline and the guides it changes.
Explore the changelog ↗Sources for the facts. Practice for the steps.
Official announcements, release notes, Code releases and service status are checked every six hours. Detected changes are deduplicated and reviewed for tutorial impact before English, Chinese and Japanese publication. Failed sources retry with backoff. X is not connected.