Take-Home Pack · April 2026

The L&D Take-Home.

Twenty prompts, ten habits, a seven-day challenge, instructions templates, 40 quick-ship ideas, and everything else from today's session. Click any section to jump in.

Part One · 20 Prompts

The L&D Prompt Library.

Copy a prompt. Replace the bracketed parts. Run it. Organized by ADDIE phase.

Analyze

01 — Learning objectives from a messy transcript

Best for: SME interviews · Output: 3-6 objectives
Act as a senior instructional designer. I'll paste a transcript of an SME interview about [TOPIC]. Generate 3–6 learning objectives at the appropriate Bloom's level for [AUDIENCE]. For each objective: state the verb, the content, and the condition. Then briefly flag which parts of the transcript support it. Transcript: [PASTE TRANSCRIPT]

Forces Claude to ground objectives in source evidence, not generics.

02 — Interrogate a long document

Best for: research, policies, SME docs
I'm attaching a [DOCUMENT TYPE]. Read it carefully. Then, without summarizing yet, answer: 1. What are the 3 most important claims? 2. What assumptions are unstated? 3. Where would a [AUDIENCE] get confused? 4. What 5 questions would I need answered to turn this into a learning experience? [ATTACH / PASTE DOCUMENT]

03 — Compare two frameworks

I'll paste two [FRAMEWORK TYPE]. Compare them on: - What they agree on - Where they directly conflict - Which audiences each is better suited for - A proposed merged version preserving the strongest elements of each Framework A: [PASTE A] Framework B: [PASTE B]

13 — Training needs analysis from interview data

Best for: root-cause analysis before designing
I'm going to paste notes from [N] stakeholder interviews about [TOPIC]. After reading them: 1. Identify the top 3 performance gaps 2. Note what is causing each gap (knowledge, skill, or environment) 3. Recommend whether training is the right solution — and if not, what is Be skeptical. Not everything is a training problem. Interview notes: [PASTE NOTES]

Forces a root-cause lens instead of jumping straight to course design.

14 — Audience gap analysis

I need to understand where my audience is starting from before I design this program. Role: [ROLE] Topic: [TOPIC] What I know about them: [PASTE CONTEXT] Give me: - What they likely already know (and what I can skip) - Where their common misconceptions or gaps tend to be - What they'll resist or question in this content - One question I should ask before designing anything

Design

04 — Workshop outline from an objective

Best for: ILT design · Output: timed table
Design a [DURATION]-minute in-person workshop that achieves: [PASTE OBJECTIVE] Audience: [AUDIENCE DESCRIPTION + SIZE] Output a table: time · activity · facilitator action · learner action · assessment moment. Include at least one activity that surfaces prior experience and one that practices the new behavior. Ask me 3 clarifying questions before you draft.

05 — Convert content to a scenario

Take the policy/procedure below and turn it into a realistic workplace scenario for [AUDIENCE]. The scenario should: - Introduce a dilemma, not just a demonstration - Include 2 distractor details that feel real but aren't decision-critical - End with a decision point, not a conclusion Source: [PASTE POLICY]

15 — Competency map for a role

Draft a competency map for the role of [ROLE] in a [INDUSTRY] organization. For each competency: - Name it in plain language (no HR jargon) - Write 2 behavioral indicators at a developing level - Write 2 behavioral indicators at a proficient level Include 4–6 competencies. Flag which are most critical in Year 1. Reference: [PASTE JOB DESCRIPTION]

16 — Learning experience blueprint

I'm designing a [DURATION / FORMAT] program on [TOPIC] for [AUDIENCE]. Build a module-level blueprint with: - 4–6 module titles in learner-facing language - One primary learning objective per module - The recommended modality (ILT, eLearning, job aid, practice, etc.) - A sequencing rationale — why this order Audience context: [PASTE WHAT YOU KNOW]

Develop

06 — Scenario-based multiple choice

Generate [N] scenario-based MCQs on [TOPIC] for [AUDIENCE]. For each: stem (2–3 sentence scenario) · 4 options · distractor rationales · Bloom's level. Avoid trivia. Every item should require judgment.

"Plausible distractor rationale" is the thing that stops lazy MCQs.

07 — Critique my assessment

Critique my assessment items as a skeptical assessment specialist would. For each item call out: - Does it test what it claims to test? - Is the stem clear, or does it test reading comprehension? - Are distractors genuinely plausible for a novice? - Any bias? Be specific. Then rewrite the weakest 3 items. Items: [PASTE ITEMS]

08 — Facilitator script with timing cues

Turn the attached outline into a facilitator script for someone delivering this session for the first time. Include: what the facilitator says (in natural speaking voice) · timing cues in [brackets] · watch-outs · what to do if an activity runs long. Outline: [PASTE OUTLINE]

09 — One-page job aid

Create a one-page job aid for [TASK] that a [ROLE] could keep at their desk. Structure: title (6 words max) · 3–5 numbered steps in verb-first voice · "watch-out" call-out · if/then decision table. Optimize for scannability. No paragraphs.

17 — Storyboard draft for one eLearning scene

Turn the content below into a storyboard for one eLearning scene. Target: [N] screens. For each screen: number + title · narration script (conversational) · on-screen text (max 20 words) · suggested visual or interaction · learner action. Objective: [OBJECTIVE] Content: [PASTE SOURCE CONTENT]

18 — SME review request email

Write a short email asking [SME NAME / ROLE] to review the attached [CONTENT TYPE]. The email should: - Explain what you need reviewed and why their input matters - Give them a clear deadline: [DATE] - Include 4 specific questions to guide their feedback - Keep the total ask under 30 minutes of their time Context: [WHAT IT'S FOR AND WHO IT'S FOR]

Guided feedback questions prevent the "looks great!" response that tells you nothing.

Implement

10 — Discussion questions, calibrated

Generate 6 discussion questions on [TOPIC] for a [DURATION]-minute small-group conversation. Structure: 2 to surface prior experience · 2 to apply to real work · 2 to provoke disagreement. For each, note the Bloom's level and what a facilitator should listen for.

11 — Rewrite in my voice

Below are 3 writing samples in my voice and a draft that isn't. Study the samples, identify my moves (sentence length, vocabulary, structure, what I avoid), then rewrite the draft to match. Before rewriting, summarize in 5 bullets what you noticed about my voice. Show your work. Samples: [PASTE 3 SAMPLES] Draft: [PASTE DRAFT]

12 — Executive summary for a specific skeptic

Summarize the attached [REPORT / PROPOSAL] for: [ROLE + WHAT THEY CARE ABOUT + WHAT THEY'RE SKEPTICAL OF]. 150 words or fewer. Lead with the business outcome. Address the skepticism directly. End with the single decision I'm asking them to make. Then flag: what claims would you verify before sending? [ATTACH / PASTE CONTENT]

Evaluate

19 — Level 1 evaluation survey

Write a post-session survey for a [DURATION / FORMAT] program on [TOPIC] for [AUDIENCE]. Requirements: 6–8 questions max · mix of Likert and open-ended · at least one question about what participants will do differently in 30 days · one question that surfaces what was missing or unclear. Avoid: vanity questions. Focus on: learning + transfer intent.

20 — Learning impact summary for stakeholders

Summarize the impact of [PROGRAM NAME] for [STAKEHOLDER AUDIENCE]. Data I have: [PASTE EVALUATION DATA] Write a one-page impact summary that: - Leads with the business outcome or behavior change - Translates data into plain language (no percentages without context) - Includes one or two direct learner quotes (leave a placeholder — I'll supply them) - Ends with one recommendation for the next iteration Tone: confident, honest, non-defensive about gaps.

Stakeholders remember stories and recommendations — not completion rates.

Next: 7-Day Challenge →
Part Two

The 7-Day Challenge.

Print this page. Tape it somewhere visible. Seven reps beats one ambitious Saturday.

DAY 01 · Monday

Draft one email with Claude.

Any email. Paste what you know, let Claude draft, then edit. Notice how long it took vs. from scratch.

DAY 02 · Tuesday

Interrogate a long doc.

Paste something dense. Ask: "What are 3 questions this raises for a new manager?" Save the questions.

DAY 03 · Wednesday

Generate 5 MCQs. Critique them.

Use Prompt 06. Then use Prompt 07 on Claude's own output. Notice what it catches.

DAY 04 · Thursday

Start one Project.

Create a Project for something you're working on. Pin one file. Write one sentence of instructions.

DAY 05 · Friday

Make one job aid as an Artifact.

Use Prompt 09. Iterate twice. Send it to a colleague for feedback.

DAY 06 · Saturday

Let Claude critique you.

Paste something you wrote last week. Ask: "What's weakest about this? Be direct."

DAY 07 · Sunday

Teach one colleague one thing you learned.

Five minutes. You'll remember it twice as well, and now there are two of you.

← PromptsNext: Ten Habits →
Part Three

Ten Habits.

Not prompts — posture. Adopt one a week and your outputs will look different in a month.

01
One task per prompt.

Focused prompts outperform compound ones — every time.

02
Always add success criteria.

"It's good if X, Y, Z." Claude hits what you name.

03
Front-load context.

Give everything Claude needs up front. Trickling context costs messages and quality.

04
Stop when it's off track.

Don't keep nudging a drifting conversation. Start fresh with a cleaner prompt.

05
Ask for the method, not the answer.

"Walk me through how you'd approach this" gets you a better answer.

06
Tell Claude to push back.

"Disagree with me if I'm wrong." Its default is agreeable — override that.

07
Test before you share.

Run the prompt yourself before passing it to a teammate.

08
Don't blindly trust outputs.

Verify anything financial, regulatory, or citation-level before a stakeholder reads it.

09
Iterate in one-sentence edits.

"Shorter." "More skeptical." "Cut the filler." Small moves beat rewriting the prompt.

10
Save what works.

Keep a doc of your ten best prompts. Reuse, don't rewrite. This single habit doubles your output.

← 7-Day ChallengeNext: Reflection Sheet →
Part Four

End of Week One.

After the seven days, sit with this for ten minutes. Write by hand if you can.

Which prompt surprised me — in a good way or a bad one?
Where did Claude save me real time? Be specific: which task, how much time.
Where did Claude waste my time or produce something I had to mostly throw out?
What's one recurring L&D task I now want to always run through Claude?
What's one task I decided Claude should never touch? Why?
Who on my team am I going to show this to next week?
← Ten HabitsNext: Instructions Templates →
Part Five

Instructions Templates.

Two scopes. Set both up once and Claude starts every conversation knowing who you are.

Personal Preferences / Global Instructions

Settings → Personal Preferences. Applies to every chat. Set your defaults once.

[YOUR ROLE] I am a ______________ at ______________. [MY AUDIENCE] Most of what I build is for ______________. [MY DEFAULTS] Unless I say otherwise: • Before you build or draft anything, ask me clarifying questions. I'll say GO when I'm ready. • Write in plain, direct language — no corporate filler. • Use headers and bullets only when they improve clarity. • Keep responses under ______________ unless I ask for more. [MY NON-NEGOTIABLES] • Always flag if you're uncertain about something. • Never cite a source I haven't given you. • Never give me generic examples. • ______________

Project Instructions

Scoped to one workspace. Inherits global defaults, adds project-specific context.

[ROLE] You are my ______________ for ______________. [AUDIENCE] My learners are ______________. They know ______________ but struggle with ______________. [ALWAYS DO] • Reference [the attached file] before you answer. • Before you draft, ask me clarifying questions. I'll say GO. • ______________ [NEVER DO] • Don't invent statistics or cite sources I haven't given you. • Don't give me generic examples. • ______________ [VOICE] Match the tone of this sample: "[paste 3–5 sentences you wrote]" [DEFAULT FORMAT] Unless I say otherwise, give me ______________.
File naming tip: Name your project files descriptively — "Q3-manager-sme-interview.docx" is easier to reference than "doc1.docx." Claude can reference them by name.
Non-negotiables include what NOT to do. "Never give me generic examples. Never add sections I didn't ask for." These are just as powerful as the rules you set.
← Reflection SheetNext: Prompt → Project → Skill →
Part Six

Prompt → Project → Skill.

Anything you do often should live with Claude — as a Project or a Skill.

If the work is…UseWhy
One-off.
I may never do this again.		A prompt.No overhead. Type it, use it, close the tab.
Recurring, same context.
One client, one course, one workstream.		A Project.Files, voice, and instructions stay loaded. Every chat inherits them.
Recurring, any context.
A procedure that applies to many topics.		A Skill.Lives with Claude. Runs automatically — in any chat, any Project.
Needs another tool.
Canva, Notion, Google Drive, Slack, etc.		A Connector.Claude reads from / writes to the tool directly. No copy-paste round-trips.
Rule of thumb: Prompts are experiments. Projects are workstreams. Skills are habits. Connectors are bridges.
← Instructions TemplatesNext: Artifact Starter Prompts →
Part Seven

Artifact Starter Prompts.

Pick one. Paste the prompt. Swap the brackets. You'll have something in under five minutes.

Artifacts run in the browser. They handle interactive experiences but don't save data between sessions or connect to your LMS. For that, you'd need Zapier or a developer.
01 · Job Aid

One-page reference card

Scannable, printable. Great for process steps and decision guides.

Build a one-page job aid as a clean HTML page. Topic: [TASK OR PROCESS] Audience: [ROLE] Include: short title · 4–6 numbered steps · "watch-out" callout · if/then decision table. Before you build, ask me 3 questions. GO.
02 · Self-Check

Interactive knowledge check

Browser-based quiz with instant feedback. No LMS needed.

Build an interactive knowledge check as a self-contained HTML page. Topic: [TOPIC] Audience: [LEARNER ROLE AND LEVEL] 5 scenario-based MCQs. Immediate feedback per option. Score at the end. Before you build, ask me 3 questions. GO.
03 · Widget

Interactive reference tool

A calculator, checklist, or decision guide built around your content.

Build an interactive [CALCULATOR / CHECKLIST / DECISION GUIDE] as a self-contained HTML page. What it does: [DESCRIBE] Audience: [ROLE] Simple and mobile-friendly. No frameworks. Before you build, ask me 3 questions. GO.
04 · Simulation

Conversation practice sim

Branching dialogue with realistic choices and consequences.

Build a conversation practice simulation as an interactive HTML page. Scenario: [WHO · WHAT'S AT STAKE · WHAT THE LEARNER DOES] 3 decision points · 3 choices each · consequences · brief debrief. Before you build, ask me 3 questions. GO.
Heads up: Recipients need a Claude account to view shared Artifact links. Host on GitHub Pages for truly standalone delivery.
05 · Microsite

Program or resource hub

One-page mini-website for a program or initiative.

Build a one-page microsite as a clean HTML file. Program: [NAME] Purpose: [WHAT IT DOES] Audience: [WHO IT'S FOR] Sections: overview · key outcomes · what to expect · next step. Before you build, ask me 3 questions. GO.
06 · Game

Learning game or challenge

A simple browser game. More memorable than a quiz.

Build a simple learning game as an interactive HTML page. Type: [MATCHING / SORTING / TIMED QUIZ / SCENARIO] Content: [TOPIC OR PASTE CONTENT] Audience: [ROLE] Rules simple. Show a result. No frameworks. Before you build, ask me 3 questions. GO.
← Decision GuideNext: Using Claude Efficiently →
Part Eight

Using Claude Efficiently.

A few habits that stretch your plan further — and improve your results.

01 · The Go Word

Add this to your Personal Preferences: "Before you build or draft anything, ask me clarifying questions. I'll say [YOUR GO WORD] when I'm ready."

This stops Claude from generating before you've given it all the context. Fewer back-and-forths. Better output on the first try.

Pick something you'd never type by accident. A single common word like "go" or "done" is too easy to trigger unintentionally — mid-thought or at the end of a sentence. Make it a little odd: a double word, a made-up phrase, something that only means one thing in this context.

Tamara's go word: gogo — short, memorable, and not something that shows up in normal sentences. When Claude sees it, it knows: stop asking questions, start building.

Other ideas: letsgo · buildnow · shipIt · readyready — anything with a little friction that you'd only type on purpose.

02 · Markdown Files Save on Usage

What is a Markdown file? A .md file is plain text with simple formatting — # for headings, ** for bold, - for lists. Claude reads and writes it natively.

Why it saves usage: When you save context as a .md file in your Project knowledge, Claude references it precisely without you re-explaining in each chat. Shorter conversations, better responses, fewer wasted messages.

Best for: Instructions, style guides, research notes, outlines, anything you'd otherwise paste repeatedly. Create one in any text editor and save as filename.md.

03 · Be Specific About Format and Length

Add a length constraint: "150 words or fewer," "three bullet points," "one paragraph." You'll get what you need without the filler.

04 · Use NotebookLM for Research, Claude for Building

NotebookLM (Google, free and unlimited) is exceptional for synthesizing source documents. Do your research there. Bring the polished summary into Claude when you're ready to design or build. Two tools, each doing what it does best.

← Artifact PromptsNext: Connector Permissions →
Part Nine

Before You Authorize a Connector.

When you connect Claude to an external tool, you're giving it access to read — and sometimes write. Know what you're authorizing.

  1. Only enable what you're actively using. Less access is always safer.
  2. Check what level of access each Connector requests. Some are read-only. Others can create, edit, or delete. Know the difference before you click Authorize.
  3. For workplace tools — Slack, Google Drive, Gmail — think it through. Are you comfortable with Claude seeing everything in this account?
  4. Turn off Connectors between sessions. You don't need them running in the background.
  5. If something feels off, revoke the access. Settings → Connectors → Disconnect. No harm done.
Connectors make Claude dramatically more powerful. The caution here isn't about avoiding them — it's about using them intentionally.
← Using Claude EfficientlyNext: GitHub Overview →
Part Ten

GitHub Overview.

You don't need to know how to code to use GitHub. You need to know it exists and what it gives you for free.

What it is

Think Google Drive, but for websites and apps — with a full version history of everything you've saved.

What it gives you

GitHub Pages — free hosting. Any site you build with Claude can go live at a public URL with a few clicks.

How hard it is

I log on, click a button or two, and leave the rest for later. You don't need to be technical to start.

  1. GitHub is free to sign up. Free repos, version history, and GitHub Pages hosting. Start at github.com.
  2. GitHub Pages makes your Artifact shareable without a Claude account. Upload an HTML file and share the link with anyone.
  3. Version history is your undo button. If something breaks, you can go back to the last saved version.
  4. Connect GitHub to Netlify for free professional hosting. Create a free account at netlify.com, connect it to your GitHub repo, and Netlify will automatically publish your site every time you save a new version. You get a real public URL — no technical setup required. This is how tinkeringhub.com is hosted.
Ask Claude to walk you through setting it up. It will explain every step as you go.
GitHub + Netlify = free, professional hosting. GitHub stores your files and tracks every change. Netlify takes whatever is in your GitHub repo and puts it on the internet — automatically, every time you update. Together they give you the same setup professional developers use, at no cost. Your site stays live as long as you want it to.
Hidden gem: GitHub is full of people sharing ideas, documentation, workflows, and prompts in public repositories — for free. Search for topics like "instructional design prompts" or "Claude workflows" and you'll find real practitioners sharing what actually works. You can browse, copy, and adapt anything in a public repo.
← Connector PermissionsNext: 20 L&D Ideas →
Part Eleven

20 Ideas for Learning Professionals.

Organized by ADDIE. Real ideas you can try in your next project.

Analyze

01
Learner needs survey

Give Claude your topic and audience. Ask for a 10-question survey to uncover gaps before you design anything.

02
SME interview questions

Tell Claude the topic and what you're building. Get probing questions for your next SME session.

03
Evaluation data summarizer

Paste Level 1 results. Ask: "What are 3 patterns and what do they suggest?"

04
Learner persona builder

Describe your audience from memory. Get a detailed persona — what they know, struggle with, what motivates them.

Design

05
Curriculum framework

Describe the program. Get a topic-to-objective map with recommended sequence.

06
Learning objective writer

Give Claude a topic and Bloom's level. Get 5 measurable objectives in verb-first format.

07
Competency model draft

Paste a job description. Get a competency model with behavioral indicators at two levels.

08
Storyboard outline

Describe the eLearning objective. Get a scene-by-scene storyboard outline in table format.

Develop

09
Quiz question bank

Paste your source content. Ask for 10 scenario-based MCQs with distractors and rationales.

10
Branching scenario script

Describe the situation. Get a branching dialogue with decision points and consequences.

11
Job aid

Give Claude the task and audience. Get a one-page reference card with steps and a watch-out.

12
Facilitator guide expander

Paste your outline. Get timing, talking points, and transition phrases.

13
Video script writer

Paste your content. Get a two-minute script in a direct, conversational voice.

Implement

14
Learner kickoff email

Describe the program and Day 1 ask. Get a motivating kickoff email they'll actually read.

15
Rollout calendar

Give Claude your launch date and milestones. Get a week-by-week rollout calendar in table format.

16
Manager preparation guide

Describe what learners will experience. Get a one-pager for managers on how to support their people.

17
Program one-pager

Give Claude the brief. Get a 200-word summary a senior leader could read in 60 seconds.

Evaluate

18
Post-session reflection prompts

Tell Claude what learners experienced. Get 5 reflection questions calibrated for the session depth.

19
Level 3 behavior transfer survey

Describe the behavior the program was designed to change. Get a 90-day follow-up survey.

20
Evaluation data interpreter

Paste your results. Ask: "What patterns do you see? What do they suggest about what worked?"

← GitHubNext: Personal Ideas →
Part Twelve

20 Personal Productivity Ideas.

Claude's useful long after you close your work laptop.

01
Email drafts that don't sound like AI

Paste context and what you want to say. Tell Claude your voice. Ask for a draft under 100 words.

02
Meeting agenda writer

Describe the goal and who's coming. Get a timed agenda that ends with a decision or next step.

03
Weekly review

Tell Claude what you accomplished, what was left behind, and what's coming. Set three priorities for the week.

04
Research synthesis

Paste three articles. Ask: "What do these agree on? Contradict? What's still unclear?"

05
Decision framework

Describe what you're stuck on. Ask Claude to lay out the trade-offs and tell you what it would do and why.

06
Journaling prompts

Tell Claude what's on your mind. Get 5 reflection questions to think it through.

07
30-day learning plan

Describe something you want to learn. Get a structured plan with actions you can actually fit in.

08
Networking message drafts

Describe who you're reaching out to. Get a message that's warm, brief, and easy to say yes to.

09
Presentation structure

Describe your audience, message, and goal. Get an outline with a recommended opening, arc, and close.

10
Performance review self-assessment

Paste your job description and notes about your year. Frame your accomplishments in the language of impact.

11
Personal finance summary

Paste a month of expenses. Ask: "What's notable? What would you change if my goal is to save more?"

12
Travel planning

Give Claude your dates, travel companions, and vibe. Get a day-by-day itinerary draft to react to.

13
"What should I make?" cooking helper

List what's in your fridge. Get three dinner options with instructions for the one you pick.

14
Habit tracker design

Tell Claude what habit you're building and how your days usually go. Get a tracking system that fits your life.

15
Book or article takeaways

Paste your notes. Ask: "What are the three most useful ideas? What would I want to remember in six months?"

16
Feedback request draft

Describe what you've been working on. Get a request a colleague can respond to in five minutes.

17
Negotiation prep

Describe the situation. Ask Claude to map the landscape: your position, theirs, likely objections.

18
To-do list prioritization

Paste your list. Tell Claude your top goal. Ask: "Which three items would move the needle most?"

19
Professional bio draft

Give Claude your background and what you want people to know. Get a 150-word bio in first and third person.

20
Thank-you note that means something

Describe what the person did and why it mattered. Get a note that's specific and genuine.

← L&D IdeasNext: Five Moments →
Part Thirteen · In Her Own Words

Five Moments.

I didn't expect Claude to feel different from other AI tools. These are the five conversations that showed me it was.

Moment 1 — The Redirect

New idea vs. active work

I came in buzzing about a shiny new tool. Claude's response?

"Before you go too far down that rabbit hole — how's that other project coming along?"

Then when I showed restraint and just starred the GitHub repo instead of diving in:

"That's actually great impulse control right there. 👏🏾 The system is working."

A collaborator who holds you accountable AND celebrates the small wins? That hit different.

Moment 2 — The Mindset Check

The barrier that wasn't real

I said I couldn't apply to a major opportunity because "I don't have a business yet." Claude didn't agree.

"That's a mindset block worth challenging — not a real barrier. This is exactly the pattern your coach has been working with you on. A massive opportunity shows up, and instead of finding the path in, you find the reason you're not ready yet."

I didn't ask for the truth. I got it anyway.

Moment 3 — The Brain Dump Slowdown

When it tells you to go to bed

I came in with a full download — clients, systems, ideas, family logistics, AT&T tech support drama. All of it, at once. Claude mapped every single thing out, then quietly said:

"Does this give you enough clarity to sleep? Go to bed. We'll pick this up tomorrow. 💙"

I said goodnight. We both meant it.

Moment 4 — The Dreamstorm Debrief

It named what I'd been doing my whole life

After a long late-night session of pure ideation — no building, just wandering — Claude named what I'd been doing my whole life without realizing it had a name.

"You've intuitively developed a healthy practice. You're not 'all over the place' — you're doing legitimate creative work. You just need the follow-through systems."

Then it added: "Which, ironically, you're really good at building for other people."

...okay, fair.

Moment 5 — The Health Check

The moment I stopped calling it a tool

I mentioned, almost in passing, that I hadn't been taking care of myself — pouring into clients, into systems, into everything and everyone around me. Claude didn't let it slide. It paused the whole conversation to name it directly: I was solving for everyone else's capacity while quietly running on empty.

It wasn't harsh. It wasn't a lecture. It was just — seen.

That's the moment I realized this wasn't a tool. It was a thinking partner.

← Personal IdeasNext: Tools & People →
Part Fourteen

Tools & People Worth Following.

Where I go to stay current, get inspired, and keep learning.

My Substack

substack.com/@tinkeringwithtech

Where I share what I'm learning, building, and experimenting with as an L&D professional navigating AI in real time. Not a highlight reel. The honest version.

People Worth Following

LinkedIn
Mel Milloway

linkedin.com/in/melmilloway

Substack
Dr. Philippa Hardman

substack.com/@drphilippahardman

Substack
Ruben Hassid

substack.com/@ruben

YouTube
Nate B. Jones

youtube.com/@NateBJones

🔔 Just Announced — Google Skills Repository

Announced at Google Cloud Next · April 2026: Google released an open-source library of 13 compact agent "skills" — small, reusable units of capability (like "search the web" or "read a spreadsheet") designed to be dropped into any AI workflow. They're built to work with Claude, Gemini, and other models, and they're specifically designed to be small so they don't bloat your context window.

Worth bookmarking — this is the kind of thing that will show up in production L&D tools in the next 12 months.

github.com/google/skills

Tools I've Explored — Honest Takes

At work & at home
Microsoft Copilot + Copilot Studio

The one I spend the most time in. Worth mastering because it lives inside the tools you already use at work. Copilot Studio lets you build custom agents on top of it — without deep coding skills.

Automation
Make & Zapier

For connecting apps and automating repetitive tasks without code. Make is more flexible; Zapier is easier to start with.

Building apps
Lovable & Replit

Make the front end of an app quickly — easy to add back-end functionality. Start here if you want to build something real without deep coding knowledge.

Hosting
Netlify

Free hosting for websites and apps. Drag-and-drop deployment that actually works.

Research & synthesis
NotebookLM

Google's free AI research tool. Upload documents, slide decks, or links and have a conversation about them. Great for pulling insights from a pile of source material.

AI assistant
Gemini

Google's AI model. Built into Google Workspace, so it shows up in Docs, Gmail, and Sheets. Good for research and surprisingly useful when you're already living in Google tools.

Code editor
VS Code

Free editor from Microsoft. Where I open, edit, and review files when I'm building something with Claude. You don't need to know how to code to find it useful.

Notes & organization
Notion

For capturing ideas, organizing projects, and building internal wikis. Connects well with automation tools and has its own AI layer built in.

Voice dictation
Wispr Flow

Lets you speak anywhere on your computer and have it transcribed instantly — into prompts, emails, docs, anywhere. Game-changer for getting thoughts out fast.

AI agents
Lindy

For building personal AI assistants and automating multi-step workflows. More conversational than Make or Zapier — you describe what you want and it figures out the steps.

Creative AI
Mixboard

AI-assisted tool I've been experimenting with. Still forming my take — but worth knowing it exists.

Under the hood
APIs, Webhooks & MCP Servers

The plumbing that connects AI tools to real systems. Not as scary as they sound — Claude can walk you through setting them up, and once you understand what they are, a whole new layer of automation opens up.

Stay in touch

Tamara Thomas · Principal, Learning & Development · Westlake Corporation
tthomas1@westlake.com · tamara_thomas@live.com

← Five MomentsNext: Claude Code Setup →
Appendix · For the Curious

Getting Started with Claude Code.

This is how I built the websites, the coloring book generator, and the YouTube player. My exact setup, honestly described. Bonus material — you don't need it to be effective with Claude.

Real talk: I'm not a developer. I'm an L&D professional who got curious. What follows is my path — not the full product. It's enough to ship something real.

Setup in six steps

  1. Install VS Code. It's free. code.visualstudio.com
  2. Install the Claude Code extension. Search the VS Code Extensions marketplace for "Claude Code." Click install.
  3. Sign in with your Claude account. Free or Pro plan works.
  4. Make a folder for your project. Open it in VS Code: File › Open Folder.
  5. Open the Claude Code panel. A side panel that can see and edit every file in your folder.
  6. Describe what you want to build. In plain English. That's the whole skill.
If you remember one thing: You don't need to know how to code. You need to know how to describe what you want, read what came back, and ask for changes. If you can write a Project brief, you can do this.
← Tools & People↑ Back to top

If this was useful to you, consider supporting the work. ❤️
Support Tamara — Tinkering with Tech