Ship a Feature in a Codebase You’ve Never Seen
A practical workshop on using Claude Code inside a real, unfamiliar Chrome Extension codebase — reading it, extending it, and shipping a working feature in one session. Not a blank-file tutorial.
No public schedule yet — small groups, by request.
Why this workshop exists
Most AI coding content starts from an empty file. You type a prompt, a to-do app appears, everyone claps. That’s not what real engineering work looks like.
Most of the time, you’re dropped into someone else’s code — a codebase you didn’t write, with conventions you don’t know, under a deadline you didn’t set. That’s exactly where AI tools either save you hours or quietly make a mess you have to untangle later.
This workshop is built around that exact situation. You’ll open a real, working Chrome Extension you’ve never seen before, and use Claude Code to understand it, extend it, and ship a feature that works — the same way you’d do it on day one at a new job.
What you’ll build
You’ll extend a production-grade Chrome Extension monitoring tool used to track new listings on a website. By the end, it’ll support a brand-new site the extension doesn’t currently cover — plus, if you want it, an AI filtering step (via the OpenAI API) that only surfaces the listings that actually matter.
- ✓Your own working fork of the extension, extended by you
- ✓A CLAUDE.md (or AGENTS.md) you wrote for a real project
- ✓At least one reusable Claude Code Skill
- ✓A monitoring tool that actually runs, on a site you chose
What you’ll learn
Mapping an unfamiliar codebase fast
where the logic lives, how the pieces talk to each other, before you touch a single line
Prompting Claude Code to extend code, not generate it
a different skill, and the one you’ll actually use at work
When to write a CLAUDE.md / AGENTS.md
and what actually belongs in one — most people get this wrong
Building a reusable Claude Code Skill
so you stop re-explaining the same task every session
Judgment
what to hand off completely, what to review line by line, and what to never delegate
Chrome Extension architecture basics
manifest, content scripts, background workers, message passing
Wiring an AI filtering step into a scraping pipeline
with the OpenAI API (optional, if time allows)
Debugging AI-written changes fast
instead of re-prompting and hoping
Who this is for
- ✓Software engineers who want to get faster at AI-assisted work on real codebases, not toy projects
- ✓Technical founders who need to move fast without writing every line themselves
- ✓People already using Claude Code, Cursor, or Codex who want to use them properly instead of by feel
- ✓Anyone tired of AI demos that only work on a blank file
Who this is NOT for
- ✕Complete beginners with no programming background — you should be comfortable reading JavaScript/TypeScript
- ✕People looking for a slide deck about "the future of AI" — this is 100% hands-on
- ✕People who want a finished tool built for them — you’re doing the building
- ✕People who want a from-scratch coding bootcamp — this assumes you already know how to code
Workshop format
Small group, capped on purpose so everyone gets real attention — this isn’t a webinar.
A short live walkthrough of the codebase and Claude Code setup, then structured build blocks with hands-on troubleshooting. Most of the time is spent building, not watching slides.
Remote or in-person, depending on the group — we’ll sort it out when you reach out.
What to bring
- A laptop with VS Code and Node.js installed
- Claude Code installed and signed in (a free or Pro account is enough)
- Comfortable reading JavaScript or TypeScript
- Basic Git (clone, commit, branch)
- Optional: an OpenAI API key, if you want to try the AI-filtering step
Questions people actually ask
About the instructor
I’m an AI Enablement consultant and software engineer. I help developers and companies adopt AI in their day-to-day engineering work — not the theory of it, the practice of it.
This workshop comes directly out of production work: building and maintaining scraping and browser-automation tools for real clients at AIScrapers. The Chrome Extension you’ll work on is drawn from that same body of work, not built as a teaching prop.
Want in on the next one?
There’s no public sign-up page — sessions run in small groups, by request. Message me and I’ll tell you about the next date, or we can set up a private session for you or your team.
Usually replies within a day.