Claude Code

Go from zero to confident Claude Code operator, no coding background required

For procurement, supply-chain, and small-business people who want to automate real file-based work with Claude Code and have something concrete to show for it.

FORGE-02

6 chapters, 15 lessons

14-day refund on the yearly plan. Real pricing on the plans page, no surprises.

15

lessons, yours to run

What you'll learn

Easy to pick up, built to get you the next job

No coding background needed, and you write code with Claude as you go.

Every section below turns into something a hiring manager recognises, not just notes.

Get Claude Code running on your actual machine, today
  • You'll install Claude Code and navigate your own folders using three plain terminal commands, no prior technical setup assumed
  • You'll run your first real task against files you already own, not a demo dataset someone else prepared
  • You'll understand exactly what Claude Code can and cannot touch without your permission, so you start with confidence, not anxiety
Direct an AI agent through real file work, start to finish
  • You'll read, explain, and approve edits to your own documents using a review step that shows you every change before it lands
  • You'll write prompts specific enough to get the result you actually want, a skill hiring managers recognise as AI literacy, not just prompting
  • You'll work across multiple files at once, proposing and approving changes at a project level, not file by file
Protect your work with a version-control safety net
  • You'll commit snapshots, review history, and undo mistakes in plain English without touching a line of code
  • You'll inherit a folder you did not build, map it safely before touching anything, and flag what is fragile, exactly the habit employers want
Walk away with a working demo you built yourself
  • You'll complete a capstone project that shows a real workflow automated end to end, something you can screen-share in an interview
  • You'll customise your own setup so the agent understands your specific context, a step most beginners skip and employers notice you did not
Outcome

Finish this course and you can do all of this, no prior background required:

  • You'll be able to run Claude Code against your own files and approve changes through a formal review step, the hands-on AI workflow employers are actively hiring for.
  • You'll be able to work across a multi-file project, propose and approve a restructure, and explain every decision, a skill that separates operators from people who just use chatbots.
  • You'll be able to inherit a folder you did not build, map it safely before touching anything, and flag risks before they become problems, exactly the due-diligence habit operations teams value.
  • You'll be able to commit, review, and undo changes in version control using plain English, so no mistake you make in Claude Code is ever permanent.
  • You'll be able to write prompts with enough specificity that Claude Code returns what you actually need, not a reasonable guess, a skill a hiring manager can see immediately in a demo.
  • You'll be able to present a capstone project showing a real automated workflow, end to end, as portfolio evidence that you can operate AI tools, not just talk about them.
FORGE-02

15 lessons, 6 chapters

Built by practitioners, not influencers

Every agent, skill file, and dataset is drawn from 25+ years and 50+ Oracle ERP implementations across pharma, manufacturing, semiconductor, and distribution.

Kept current with the stack

Claude Code, skills, and MCP move fast. Your licence includes every system update for as long as you're subscribed. Your system gets better, not obsolete.

Where most people are stuck

Every job post now mentions AI tools, but when you apply, you have nothing to show. You have used chatbots, copied answers out of a browser tab, and pasted them into a document by hand, that is not what employers mean when they say they want someone who can work with AI. Meanwhile the people getting shortlisted have built actual things: agents that open files, make changes, and run tasks end to end. You do not need a computer science degree to do that, but you do need somewhere honest to start, with real files, real mistakes, and someone who explains what is happening at every step.

What you'll be able to do, module by module

Every module leaves you able to build and run something real. Here is the syllabus, in the order you work through it.

Curriculum

6 chapters · 15 lessons

Module 1: Getting oriented

You can install Claude Code, navigate your own folders with three terminal commands, and run a first real task against files you already own, with a clear mental model of what an agent is versus a chatbot.

Lessons2 items
  • What Claude Code actually is🔒
  • Install, first run, and just enough terminal🔒

Module 2: The core workflow

You can read a file, review a proposed change line by line in a diff, approve only what you asked for, and write prompts specific enough to get the result you actually wanted the first time.

Lessons3 items
  • Your first task: read, explain, edit🔒
  • Reviewing and approving changes🔒
  • Writing prompts that get good results🔒

Module 3: Real files, real projects

You can work across an entire project folder, map a project you did not build before touching it, and use version control to commit, review history, and undo mistakes in plain English.

Lessons3 items
  • Working across multiple files and folders🔒
  • Understanding a project you didn't build🔒
  • Version control as your safety net🔒

Module 4: Customising your setup

You can configure Claude Code to understand your specific working context so it behaves consistently across every task, not just the ones from the lesson.

Lessons2 items
  • CLAUDE.md and project memory🔒
  • Slash commands and plan mode🔒

Module 5: Going further

You can extend what Claude Code does for you beyond the basics covered in earlier modules, applying the core workflow to more complex or varied real-world tasks.

Lessons3 items
  • Skills: reusable playbooks🔒
  • Subagents and delegation🔒
  • MCP: connecting outside tools and data🔒

Module 6: Capstone and next steps

You can present a complete, working Claude Code workflow you built yourself from scratch, something concrete enough to screen-share in a job interview or show a line manager.

Lessons2 items
  • Build something from a blank folder to done🔒
  • Common mistakes, troubleshooting, and where to go next🔒

Most candidates say they use AI tools. You will be one of the few who can open a project folder, run an agent across real files, review every change, and demo the whole thing live. That combination of hands-on proof and a clean audit trail is what makes you the operator a hiring manager remembers after the interview.

How it works

From subscribing to running your first artifact

  1. Subscribe and preview before you commit

    Access a free preview lesson the moment you sign up. No setup required to watch it. If it is not the right fit within 14 days, you get a full refund, no questions.

  2. Open the course and follow Maya from lesson one

    Each lesson follows Maya, a small shop owner with no coding background, through one honest mistake and one small win. You mirror every step in your own folder, on your own machine, so nothing is abstract.

  3. Build and run your first real artifact

    By the end of Module 2 you will have opened a real file, reviewed a diff, approved an edit, and undone a mistake, all in Claude Code, all on files you already own. That is your first working proof of concept.

A worked example from this program

How Maya reorganises a chaotic downloads folder without breaking anything

  1. Ask for a plain-English map first

    Maya opens Claude Code in her downloads folder and asks it to describe how everything is currently organised. It names her real files, spots three groups that clearly belong together, and flags two files that look like duplicates.

  2. Request a proposed structure, nothing moved yet

    She asks for a suggested folder structure, explicitly telling it not to move anything yet. Claude Code proposes four named folders and lists which files would go where, by their actual names.

  3. Review the plan before approving a single move

    Maya reads through the proposal. One file is assigned to the wrong group because the name is ambiguous. She corrects that in plain English and asks it to revise the plan.

  4. Commit a snapshot before any changes land

    Before approving the moves, she asks Claude Code to commit the current state of the folder. She now has a restore point she can return to in one plain-English instruction if anything goes wrong.

  5. Approve and verify

    She approves the revised plan. Claude Code moves the files, and she asks it to confirm what is now in each folder. The result matches the proposal she approved, nothing extra touched.

Proof you can show

The toolkit you'll build and run in this program

You leave with working assets, not notes.

Real things you can demo in an interview.

A working Claude Code installation configured on your own machine, tested against your own files

A version-controlled project folder with commit history you created yourself, showing the safety net in action

A customised setup file that tells Claude Code about your specific working context

A capstone workflow artifact built from scratch, ready to screen-share as a portfolio piece

A personal prompt library of specific, reusable requests refined through the course exercises

Who this is for

You'll get the most from this if

People in procurement, operations, or supply chain who want to automate file-based work and have something real to show employers

Small-business owners or administrators managing folders, documents, and projects without a technical team behind them

Career changers and students who want to add genuine AI-operator skills to their CV without learning to code

Anyone who has used a chatbot and knows it is not enough, and wants to move from copy-paste to actually getting the job done

Yearly plan: 14-day keep-the-system guarantee

14-day refund on the yearly plan. Finish the first two modules, and if you haven't run your first live pipeline, take a full refund.

Questions

Straight answers before you subscribe

I am on a Mac. Does this work with my setup?

Yes. The course is designed so you work in your own folders on your own machine from lesson one. The terminal commands covered in Module 1 work on Mac, Windows, and Linux, and the lessons flag any differences as you go.

I have never written a line of code. Will I be lost?

No coding background is assumed anywhere in this course. You start with three terminal commands in Module 1 and build from there. Every step is demonstrated through Maya, who starts from exactly the same place you do, and the lessons explain what is happening before asking you to do it.

What if I start and it is not right for me?

There is a free preview lesson you can watch before you commit to anything. If you enrol and decide within 14 days that it is not the right fit, you get a full refund, no questions asked.

Will the course stay up to date as Claude Code changes?

The course is updated to reflect changes to Claude Code. Enrolled students get access to updated lessons as they are published, so what you learn reflects how the tool actually works today, not how it worked when the course was first recorded.

Can I use what I build here for real work or a client?

Yes. The workflows, prompt patterns, and capstone project you build are yours to use in your own work. The course is designed around your real files and real tasks precisely so that what you build during it is immediately useful outside it.

Finish this program and walk in as the operator employers can't ignore, not another applicant with no experience.