0 XP
0
G

Ready to practice this for real?

The full reading for this lesson is below, free to anyone. Think of it as the map. A free account adds the guided path: hands-on exercises, saved progress, and each lesson picking up where the last left off. No credit card needed.

Next up: Claude Code: Build With Words

Sign up with email

Already have an account? Sign in

Claude Code: Build With Words

Automate recurring work and build tools from plain-language descriptions. No coding experience required.

Claude Code is where you stop doing the work and start describing it. You say what should happen, in plain language, and it builds the thing that makes it happen. You never write code yourself.

If you can explain a process to a new hire, step by step with inputs, outputs, and edge cases, you can explain it to Claude Code.

The signal is repetition. Real examples: a weekly status report from three spreadsheets that runs every Friday at 8 AM. Client onboarding emails personalized from a spreadsheet whenever a new row appears. Monthly budget consolidation from four department files, done in seconds instead of half a day.

Your first session, step by step:

1. Type claude in your terminal. It looks like chat, but with access to your files and the ability to run code.

2. Describe the task: "Every Monday at 8 AM, read Sales/data.xlsx, calculate revenue by region, save a summary to Reports/weekly-[date].docx."

3. Claude asks clarifying questions. "Include regions with zero revenue?" Answer them.

4. Claude proposes a plan before writing anything. Review it. This is your chance to redirect.

5. Claude writes the code, tests it on a sample, and shows the output. Point out anything off.

6. You get a working automation, plus instructions for running, scheduling, and fixing it.

Desktop proves the process. Code automates it. You process client emails on the desktop app weekly, 10 minutes instead of 45. Four identical weeks later, you move it to Claude Code and it runs without you.

Template: "Every [time period], I need to [task]. Input: [source]. Output: [format and location]. Steps: [each step]. Edge cases: [what might go wrong]. Run [how often] starting [when]."

Every automation request needs three things:

Trigger: a schedule, an event, or a manual run

Inputs: which files, folders, columns, and formats

Output: what file, what name, saved where

Answer those three and Claude Code can build it.

Claude Code also builds real tools: dashboards, custom apps, things your whole team can use. You describe, it builds.

One session, one working digest:

You say: "I read five websites for industry news. Build a weekly digest that pulls headlines from the past 7 days from all five and formats them into one email for my team every Monday morning."

Claude asks: Which sites? What time? Plain text or HTML? Who receives it?

You answer. Claude proposes a plan: fetch the feeds, filter to 7 days, format by site, send. You approve, it builds, you test.

Forty-five minutes of describing replaces the build, and Monday runs itself from then on.

Claude Code automates recurring work from plain-language descriptions. You do not need to code, you need to describe clearly. The six-step session shows what to expect; trigger, inputs, and output are the three things every request needs. Prove the workflow in the Desktop app, then automate it in Code. Next: a three-question framework for choosing the right level.

Nightschool AI is an independent learning platform and is not affiliated with, endorsed by, or sponsored by Anthropic. Claude is a trademark of Anthropic, PBC. Looking for Anthropic's official Claude Academy? It's at academy.claude.com.

Claude Code: Build With Words: The Three Modes | Nightschool AI