You've got the foundation. Here's what to do next.

Thanks for attending the Claude Foundations Workshop. These resources will help you build on what we covered.

From the workshop

1

Know the fundamentals

2

Plan what you want to build

3

Iterate

Quick Wins — Do These This Week

Small habits that compound fast. Start here.

Connect your tools

Settings → Customize → Connectors. Start with Google Calendar or Gmail. Test it: “What's on my calendar this week?” Add Notion, Asana, Slack — whatever you actually use.

Turn on memory

Settings → toggle on “Generate memory from chat history.” Claude builds memory per project after a few chats — and you can edit it yourself. One catch: new chats still don't search previous threads by default. If you want that, ask explicitly: “search previous threads in this project.”

Curate your project knowledge files

Claude reads file names first to decide what's relevant — so name them clearly, not document3.pdf. Skip 100-page PDFs (extract the key parts first), no sensitive data, no screenshots. Good fits: brand voice, OKRs, pricing, SOPs, active client list, business overview.

Build a daily check-in skill

Once your tools are connected, ask Claude: “Give me my morning brief — calendar, urgent emails, top priorities.” Tweak the prompt until the format feels right, then save it as a skill so you can run it every morning in one sentence.

Talk instead of type

I use Wispr Flow for voice-to-text everywhere on my computer — Claude, Slack, email, Docs. You'll move much faster.

When to use Cowork

Cowork (Claude's desktop agent mode) is Claude with hands on your actual computer. Use it when you want Claude to take action on local files, open apps, or automate things on your desktop — not just answer questions.

Your context window is real

If a long conversation starts producing fuzzy output, start a fresh chat. Your Project instructions reload every time. You lose nothing.

Correct like a colleague, not a stranger

When output is off, don't start over. Just say what's wrong: “That's close but the tone is too formal — try again.” Claude adjusts fast.

Ask Claude about Claude

“Are my project instructions clear? What's missing?” Meta-prompting your own setup is one of the highest-leverage things you can do.

Save the good stuff

When Claude gives you output worth keeping, you've got two options. Copy and paste it into Word, OneNote, or wherever you work in MS365 — formatting comes through clean. Or save it to your Project's knowledge files and Claude stores it as a Markdown file future chats can read. Heads up: those saved files are read-only — if you need to edit, copy it somewhere else first.

Free Skills — Download & Install

Skills extend what Claude can do. Download the .zip, then in Claude go to Settings → Customize → Skills and upload it.

What's inside a skill?

A skill is just a folder with a few files. When you unzip one of the downloads above, here's what you'll see — and what each piece does.

skill-name/
├── SKILL.md          ← required
├── assets/           ← optional (files Claude includes verbatim)
├── references/       ← optional (background context)
└── scripts/          ← optional (code Claude can run)
SKILL.mdRequired

The brain of the skill. Has YAML frontmatter at the top with name and description (Claude reads this to decide when to trigger the skill), then your instructions in Markdown.

assets/Optional

Files Claude pulls in verbatim — like brand-voice.md from the Brand Voice Generator, templates, or sample outputs. Drop these in to personalize a skill.

references/Optional

Background docs Claude can read for context — frameworks, source material, examples — without including them word-for-word in every response.

scripts/Optional

Optional code (Python, JS) Claude can run. Skip this for most non-technical use cases — it's for when you want the skill to actually execute something.

Free Tools

Two web-based tools that generate files you can plug into any Claude Project or skill.

Reminder from the workshop

The BRIEF framework

The five things every Claude Project (and every skill) needs in its instructions. Strategic Advisor uses it — so does any project you build from scratch.

B

Behavior How Claude should act and communicate

R

Role What expert identity Claude should take on

I

Intel Background context Claude needs about you and your work

E

Edges What Claude should never do

F

Format How output should be structured

Want to keep going?

If there's a topic you want to go deeper on — or you'd be interested in a follow-up session for your team — I'd love to hear from you.

These resources are from the Claude for Everyone course. Learn more at claudeforeveryone.com.

Not affiliated with Anthropic PBC.

© 2026 Elevate Online. Independent training company. Not affiliated with, endorsed by, or sponsored by Anthropic, PBC. “Claude” is a trademark of Anthropic, PBC.