Tools — by category

OpenAI's assistant — the course's default thinking and planning surface, and the tool every mechanism gets demonstrated on.

Pick this when: Planning, brainstorming and turning a vague idea into a spec — the BC2 trainer's stated default for that work, even though he lives in Claude for connectors.

Reads screenshots well enough to turn competitor pricing pages into a feature map

Apps (its MCP equivalent) connect Canva, Figma and Spotify from the browser

The reference surface for the whole course: tokenization, hallucination and prompting were all demonstrated here

Full entry →

Anthropic's assistant — the course's pick once work involves your real files, calendar and tools.

Pick this when: The task needs to touch your actual world (connectors) or produce careful structured output — vs ChatGPT for open-ended planning.

Desktop connectors reach your local filesystem and CPU, which browser-based rivals cannot

Skills: reusable .md instruction packages that can also call tools

Connector reliability the trainer scored ~7/10 in daily use, against ~4/10 for ChatGPT apps

Full entry →

Google's assistant and model family — huge context, deep Google-app gravity, and gems as saved custom assistants.

Pick this when: You need a very large context window cheaply, or you're already living in Google Workspace.

Context windows around 1M tokens, which makes whole-document work practical

Gems: saved custom assistants, the natural home for a meta prompt in Google's world

Gemini 3 Flash proved the cheap-and-fast option for voice agents in BC6

Full entry →

A free playground on Gemini with a 1M-token window and a visible token counter — the course's build bench for prompt work.

Pick this when: You have a big document to process once and don't want to spend paid tokens doing it — the trainer builds his meta prompt here for exactly that reason.

Visible token counter — you watch a 38k-token PDF land, which teaches context spend better than any explanation

1M context on a free account

No subscription needed to do serious one-off document work

Full entry →

The open-source always-on agent runtime — an OS for a personal AI employee that you deploy to a VPS, design with md files, and talk to over Telegram.

Pick this when: You want a proactive 24/7 assistant (schedules, heartbeats, channel inboxes) that YOU design and host — not another chat app you have to open.

Proactive, not reactive: triggers (timers, calendar events, heartbeats, messages) make the agent come to you

The md-file design surface — user/identity/soul/memory + tools/heartbeat/bootstrap — turns setup into agent DESIGN

Runs anywhere (local, Hetzner, Hostinger 1-click, Railway template) with model routing across providers

Full entry →

A search-first assistant — answers grounded in live web results with sources attached.

Pick this when: The question is about the current state of the world and you want citations rather than recall.

Search-grounded by default, so freshness isn't something you have to ask for

Used in the course as a spec-checker: paste laptop specs, ask which local model variant fits

Full entry →

Google's agentic coding environment, driven by Gemini.

Pick this when: You're already in Google's model ecosystem and want its coding agent — the course treats it as a third option, not a first choice.

Gemini-native, so it inherits Google's long context

Used in BC4 to generate the example markdown and JSON files for the file-format lesson

Full entry →

Anthropic's terminal coding agent — it reads your repo, writes across files, runs commands, and iterates until the thing works.

Pick this when: The project has outgrown a vibe-coding platform and you want depth, repo awareness and parallel sessions — vs Cursor's editor-first feel or Codex's stronger back-end bias.

Clones and takes over an existing repo — the documented graduation path out of Lovable

Runs several sessions in parallel on different workstreams (the BC2 trainer's team runs 3-4)

MCP-aware, so connectors like Supabase or a filesystem make its work conversational

Full entry →

Claude's desktop workspace for file and task work — described in the course as a UI wrapper over Claude Code.

Pick this when: The work is on your own machine, needs judgement rather than a fixed pipeline, and you'll be present for it.

Runs recurring scheduled tasks without you building a workflow

Full file access plus a sandboxed shell in one place

No workflow to author — you describe the task instead of drawing it

Full entry →

OpenAI's coding agent, run at GPT-5.5 'extra high' — the course's pick when back-end correctness matters more than looks.

Pick this when: You need generated config or back-end code to be right first time — it produced the only n8n JSON with native Firecrawl nodes when Claude missed them.

Reasoning effort is a dial you turn up — 'extra high' was the setting that won both BC3 and BC4 comparisons

Live preview while building

Strong at structured output (JSON, workflow definitions) where a near-miss is a broken artifact

Full entry →

An AI-first code editor — a familiar VS Code surface with an agent living inside it.

Pick this when: You want to stay in an editor and see every diff as it lands, rather than conversing with a terminal agent.

Ships its own fast model, so quick edits don't cost premium tokens

Free tier is usable as a plain editor — no subscription needed to try it

Editor-native: the agent works where you already read code

Full entry →

The free editor that hosts everything else — terminal, git, and whichever coding agent you've chosen.

Pick this when: Always, as the substrate. It's the trainer's daily editor precisely because it's free and neutral.

Free, and the default host for Claude Code in the course's local stack

Integrated terminal is where git clone and the whole local workflow happen

Full entry →

A vibe-coding platform that was the fastest to a working build in the course's five-way bake-off.

Pick this when: Speed to a first running app is the only thing you're optimizing — Lovable still wins on how it looks.

Fastest build in the BC4 bake-off, on the trainer's first-ever use

Recently acquired, which the trainer flagged as a signal of the category consolidating

Full entry →

A browser vibe-coding platform — the weakest performer in the course's head-to-head.

Pick this when: Hard to justify over Lovable or Base44 on the evidence the course gathered; try it only if the others fail your brief.

Pushes builds to GitHub like its peers, so output isn't trapped

Included in the BC4 bake-off, which is the only direct evidence the course offers

Full entry →

The WordPress page builder: free version takes over the page content box with widgets; Pro overrides theme parts (header, footer, post templates) and adds dynamic content.

Pick this when: You build client sites on WordPress and want visual editing with real dynamic-content architecture underneath — accepting plan-tier gates on the pro features.

Theme builder that overrides (not builds) WordPress theme parts with the same editor

Dynamic content + custom post types turn pages into renderings of single-source data

Saved templates and a widget library replacing single-purpose plugins

Full entry →

Another browser vibe-coding platform — 'pretty cool' in the bake-off, and a common on-ramp people graduate out of.

Pick this when: As one more parallel attempt at an MVP; nothing in the course argues it's the best pick.

Performed respectably in the five-way BC4 comparison

A learner in the cohort used it before moving to Claude Code, Cursor and Codex — a documented graduation path

Full entry →

Describe an app in a browser chat and get a working, hosted, full-stack build — the course's default MVP factory.

Pick this when: You want the best-looking first draft fastest and you'll graduate the code out later — vs Bolt (weaker), Replit (more IDE), or Base44 (faster but less polished).

Won the bake-off on design — 'the best-looking output' across five platforms tested live in BC4

One-click GitHub sync, so the project can be cloned and taken over by a coding agent

Auth, secrets prompts and a code view are built in — it scaffolds a real app, not a mockup

Full entry →

Lovable's own bundled back end — database, auth, storage and AI models with zero setup, in exchange for living inside Lovable.

Pick this when: You want the MVP working today and lock-in is an acceptable price — pick Supabase instead the moment the app matters.

Zero configuration: no separate account, no keys, no SQL editor

AI models included, so a generated app can call an LLM without you buying API credits

It's what Lovable actively steers you toward — the BC2 trainer pivoted to it mid-demo

Full entry →

A browser IDE that grew a vibe-coding agent — build, run and host in one tab.

Pick this when: You want the generated app to live somewhere runnable immediately and you like an IDE view rather than pure chat.

Built a working blog in the BC4 bake-off — a real result, not a shell

IDE plus hosting in one place, so there's no deploy step to learn

Full entry →

Vercel's component generator — the original 'describe a UI, get React' tool, now with prebuilt templates.

Pick this when: You need polished front-end components rather than a whole app, especially inside a Next.js/Vercel project.

The OG of the category — it defined component-level generation

Prebuilt templates that can be wired to an n8n back end

Full entry →

The free CMS under a third of the web: turns a folder of site files into manageable media, posts, pages, plugins and themes.

Pick this when: You want ownership, the plugin ecosystem, and portability across hosts — the LWP stack's foundation.

Biggest CMS in the world; free software installed on any hosting

Posts/comments heritage explains its architecture (born as self-publishing freedom)

Custom post types make it a general content database, not just a blog

Full entry →

Claude's desktop workspace for file and task work — described in the course as a UI wrapper over Claude Code.

Pick this when: The work is on your own machine, needs judgement rather than a fixed pipeline, and you'll be present for it.

Runs recurring scheduled tasks without you building a workflow

Full file access plus a sandboxed shell in one place

No workflow to author — you describe the task instead of drawing it

Full entry →

A closed-source visual automation platform — friendlier than n8n to start, priced per credit, and limited to the nodes it ships.

Pick this when: You want the gentlest possible on-ramp to automation and you'll never need a custom node or an agent inside the flow.

The easiest first hour in the category — the comparison the BC3 trainer drew explicitly

Large prebuilt template library

Full entry →

Open-source workflow automation — nodes on a canvas, each node a small script, wired into if-this-then-that chains with optional AI agent nodes.

Pick this when: You want ownership and depth: self-host it free, customize node logic, and embed real AI agents — accept a steeper start than make.com/Zapier.

Fully open source and self-hostable — the only major automation platform you can run for $0 on your own box

AI agent node with model/memory/tools sockets — agents inside workflows, not bolted on

Workflows are portable JSON — generate, share, and debug them with a coding agent

Full entry →

The open-source always-on agent runtime — an OS for a personal AI employee that you deploy to a VPS, design with md files, and talk to over Telegram.

Pick this when: You want a proactive 24/7 assistant (schedules, heartbeats, channel inboxes) that YOU design and host — not another chat app you have to open.

Proactive, not reactive: triggers (timers, calendar events, heartbeats, messages) make the agent come to you

The md-file design surface — user/identity/soul/memory + tools/heartbeat/bootstrap — turns setup into agent DESIGN

Runs anywhere (local, Hetzner, Hostinger 1-click, Railway template) with model routing across providers

Full entry →

Auto-posting layers for Twitter/X and LinkedIn — the publish step at the end of a content workflow.

Pick this when: A workflow generates content and something has to actually post it on a schedule.

Blotato ships a custom n8n node, so posting is one node rather than an API integration

Handles the scheduling and formatting quirks of each platform

Full entry →

The original no-code app connector — enormous integration catalogue, task-based pricing, no depth.

Pick this when: The integration you need exists there and nowhere else, and the workflow is genuinely simple.

The widest catalogue of app integrations in the category

Full entry →

Google's assistant and model family — huge context, deep Google-app gravity, and gems as saved custom assistants.

Pick this when: You need a very large context window cheaply, or you're already living in Google Workspace.

Context windows around 1M tokens, which makes whole-document work practical

Gems: saved custom assistants, the natural home for a meta prompt in Google's world

Gemini 3 Flash proved the cheap-and-fast option for voice agents in BC6

Full entry →

A free playground on Gemini with a 1M-token window and a visible token counter — the course's build bench for prompt work.

Pick this when: You have a big document to process once and don't want to spend paid tokens doing it — the trainer builds his meta prompt here for exactly that reason.

Visible token counter — you watch a 38k-token PDF land, which teaches context spend better than any explanation

1M context on a free account

No subscription needed to do serious one-off document work

Full entry →

Google's personal RAG — drop in up to 50 sources and get cited answers, mind maps and audio overviews over your own material.

Pick this when: You want to learn from documents you already have, with citations, and you don't want to build any retrieval infrastructure.

Every answer cites the exact source and passage — you can jump to where it came from

Generates a two-host audio overview and a video walkthrough of your material

Mind maps the whole corpus, so you see structure you didn't know was there

Full entry →

An app store for local models — pull an open-source LLM and run it entirely on your own machine, free and offline.

Pick this when: Privacy, zero marginal cost, or uncensored models matter more than raw capability — and you have the RAM.

One command to pull and run a model (`ollama run <model>`), which is the whole install experience

Plugs straight into n8n as a chat-model node via a local URL on the standard port

Uncensored community models that no hosted API will serve you

Full entry →

Direct API access to OpenAI's models — the canonical example of buying credits and pasting a key into something you built.

Pick this when: A generated app needs its own model access and you want the vendor relationship direct rather than routed.

The teaching example for the whole API-key pattern: create key, top up credits, paste into the app

Cost reality check — the BC2 AI project generator's whole session cost 3-4 cents

Full entry →

One API key and one endpoint in front of hundreds of models — switch model without switching integration.

Pick this when: You want to change models freely (or fall back automatically) without rewriting credentials in every workflow.

Rankings and side-by-side model comparison pages that show what's actually being used

A single credential in an n8n agent node covers every model it fronts

Makes model choice a runtime decision rather than an architectural one

Full entry →

OpenAI's connector layer — browser-based integrations with Canva, Figma, Spotify and friends.

Pick this when: You're already in ChatGPT and the task is a single-tool job in a web service — otherwise Claude's desktop connectors go further.

Zero install — it's all in the browser under Settings → Apps

Design integrations that produce finished, editable artifacts in-chat (the Canva invitation demo)

Full entry →

Claude's word for MCP servers — the plug layer that lets the desktop app read your mail, your calendar and your actual files.

Pick this when: You want an assistant that acts on your real data on your real machine, not just talks about it.

Reaches the local filesystem and CPU — the whole reason connectors are desktop-only

Granular permissions: allow-once vs always-allow, per action and per directory

Works on free accounts; pick Haiku to stretch the token allowance

Full entry →

A hosting layer for MCP servers — it runs the server and handles the auth so you only paste a URL.

Pick this when: You want a third-party integration without self-hosting anything or managing OAuth yourself.

Hosted servers mean no install and no local process to keep alive

Handles the underlying service authorization as part of the connect flow

Full entry →

A documentation-lookup MCP: fetches current, version-specific docs for thousands of libraries so generated code uses today's APIs, not the model's memory.

Pick this when: Your build depends on fast-moving or obscure library versions the model may not know — otherwise modern models fetch docs themselves.

Version-specific docs for thousands of libraries, free

Embeddable inside a skill so it fires only when that skill runs (session 13's pattern)

The course's own live controversy: endorsed by one trainer, retired by another the next day

Full entry →

A marketplace indexing thousands of MCP servers, each with a hosted URL you can paste into any host app.

Pick this when: The built-in connector directory doesn't have what you need — which is most of the time, because it's curated and small.

Reliability rating and user count on every listing — the cheapest available trust signal

Per-host install instructions, so 'add this to Claude' is copy-and-paste

Breadth: the long tail of niche tools nobody's first party will ever ship

Full entry →

An app store for scrapers — prebuilt, maintained actors for LinkedIn, Instagram, YouTube and hundreds of other platforms.

Pick this when: The target is a major platform someone has already solved — buying the maintained scraper beats writing one that breaks.

Platform-specific scrapers that survive the sites' defences, maintained by their authors

Free credits to try before committing

The trainer's explicit choice over DIY for LinkedIn

Full entry →

A marketplace of Claude skills — packaged instruction files you install instead of writing the prompt yourself.

Pick this when: Someone has already solved the instruction problem you're about to solve — sort by usage count and take theirs.

Usage counts as the quality signal — the top skill is a 1.4M-download skill-finder

Skills convert cleanly into system prompts for other tools, which is how BC3/BC4 used them inside n8n

Covers surprisingly specific ground (Azure Kubernetes advisor, web scraping, content humanizer)

Full entry →

A marketplace indexing thousands of MCP servers, each with a hosted URL you can paste into any host app.

Pick this when: The built-in connector directory doesn't have what you need — which is most of the time, because it's curated and small.

Reliability rating and user count on every listing — the cheapest available trust signal

Per-host install instructions, so 'add this to Claude' is copy-and-paste

Breadth: the long tail of niche tools nobody's first party will ever ship

Full entry →

The voice library — human-sounding synthetic speech, filterable by language and accent, and clonable from your own audio.

Pick this when: The voice itself is the product decision: you want a specific accent, gender or a cloned voice rather than a stock one.

Filterable library (English, British, male…) with a voice ID you paste straight into Retell

Voice cloning from roughly 20 minutes of audio

Multilingual voice tags for agents that must switch language

Full entry →

The platform where you assemble phone-answering AI voice agents: prompt + LLM + voice + functions, billed per minute of talk.

Pick this when: You're building phone agents without a developer background — friendlier than VAPI, vastly more tunable than GoHighLevel's built-in agents.

Deep tuning surface: latency, interruption sensitivity, transcription accuracy, voicemail/IVR handling

Post-call data extraction turns every call into structured CRM rows

Built-in cal.com scheduling functions — booking agents with zero custom code

Full entry →

A developer-first voice agent platform — the same job as Retell, aimed at people comfortable in code.

Pick this when: You're a developer who wants API-level control over the call pipeline more than a friendly builder UI.

Developer-oriented surface where Retell is UI-oriented

Near feature parity with Retell on the fundamentals

Full entry →

System-wide voice dictation that types where your cursor is — how trainers talk to Claude Code instead of typing.

Pick this when: You prompt agents faster by speaking — with the caveat that ASR garble goes straight into your prompt.

Works in any input box, including terminals

Full entry →

An app store for scrapers — prebuilt, maintained actors for LinkedIn, Instagram, YouTube and hundreds of other platforms.

Pick this when: The target is a major platform someone has already solved — buying the maintained scraper beats writing one that breaks.

Platform-specific scrapers that survive the sites' defences, maintained by their authors

Free credits to try before committing

The trainer's explicit choice over DIY for LinkedIn

Full entry →

A proxy network for scraping at scale — rotate through real IPs in the geography you need so you don't get banned.

Pick this when: Your scraper works locally and dies in production, or the target is geo-restricted.

Geo-targeted residential proxies — the fix for region-locked targets like LinkedIn

Native n8n nodes, so the proxy layer sits inside the workflow

Full entry →

Scraping built for AI — hand it a URL and get clean markdown or structured JSON back, with an LLM doing the extraction.

Pick this when: You need page content in a shape a model can use, and you don't want to write or maintain selectors.

AI extraction: give it a prompt and a JSON schema and it returns structured fields, not HTML

Native n8n nodes with quick-connect, plus 100k free credits on the hobby plan

Open source — self-host it when the credits run out

Full entry →

A search-first assistant — answers grounded in live web results with sources attached.

Pick this when: The question is about the current state of the world and you want citations rather than recall.

Search-grounded by default, so freshness isn't something you have to ask for

Used in the course as a spec-checker: paste laptop specs, ask which local model variant fits

Full entry →

The WordPress plugin that turns posts into structured data: custom post types, taxonomies, and validated custom fields — the data layer of the LWP method.

Pick this when: You're modeling client-editable content on WordPress — Reno's insistence: 'everything is in one package,' vs CPT UI (harder) and JetEngine (paid).

Post types AND fields in one free plugin (2M installs cited in-course)

Backend-UX controls: instructions, validation, prepend/append labels, field widths

Safe URL renaming via custom permalinks — the rescue for the never-change-the-post-type-key rule

Full entry →

An authentication framework for TypeScript/Next.js apps — the auth layer Claude's plans now select by default for marketplace-grade builds.

Pick this when: Your generated app needs real sign-in and you're in the Next.js ecosystem — it's what the model will likely propose anyway.

Model-selected in the s14 live build without being asked for

Reported as joining Vercel (on-screen banner) — ecosystem-aligned

Full entry →

Open-source scheduling with a real API — the booking layer voice agents plug into.

Pick this when: Something automated needs to book time on a calendar and you want event types, limits and availability defined properly.

Built-in Retell functions — booking agents with no custom code

Event types carry their own availability rules, limits and confirmation settings

Open source, so clients can host their own

Full entry →

A hosting layer for MCP servers — it runs the server and handles the auth so you only paste a URL.

Pick this when: You want a third-party integration without self-hosting anything or managing OAuth yourself.

Hosted servers mean no install and no local process to keep alive

Handles the underlying service authorization as part of the connect flow

Full entry →

Containerized app runtimes: package a service (like Postgres) with everything it needs and run it identically anywhere.

Pick this when: A build needs real backing services locally (databases, queues) — the enterprise-grade default the course's plans reach for.

The reason 'enterprise-grade' prompts pull in Postgres locally

Isolates dependencies so installs don't pollute your machine

Full entry →

Where code lives and how it moves between tools — the course calls an account 'non-negotiable'.

Pick this when: Always. It's the interchange format between vibe-coding platforms, coding agents and your own machine.

The handoff point: Lovable pushes here, Claude Code clones from here

Version history is the safety net that makes aggressive AI editing survivable

Public repos are how the course shares finished builds with the cohort

Full entry →

An agency CRM with marketing automation bundled — and native voice agents the course explicitly avoids.

Pick this when: You're running an agency that already lives in it; not for the AI features.

All-in-one agency stack: CRM, funnels, messaging, scheduling

The trainer's own agency CRM — export call notes to it rather than building agents in it

Full entry →

LWP's two recommended WordPress hosts: Hostinger the beginner-friendly value pick, SiteGround the more premium one — both with the free-subdomain feature the method leans on.

Pick this when: Hosting WordPress with full plugin freedom at sane prices — against wordpress.com and Elementor Hosting, both refused by the course.

Free subdomains by the hundred: the staging-and-portfolio mechanism of the LWP workflow

WordPress-optimized packages under $10/mo (promo pricing)

Full entry →

Lovable's own bundled back end — database, auth, storage and AI models with zero setup, in exchange for living inside Lovable.

Pick this when: You want the MVP working today and lock-in is an acceptable price — pick Supabase instead the moment the app matters.

Zero configuration: no separate account, no keys, no SQL editor

AI models included, so a generated app can call an LLM without you buying API credits

It's what Lovable actively steers you toward — the BC2 trainer pivoted to it mid-demo

Full entry →

Open-source vector database with an embedded mode — the searchable memory a RAG system stores its chunks in.

Pick this when: You want vector search inside the process (single-tenant, on-prem, laptop-sized) instead of a hosted vector-database service.

Embedded mode runs in-process — Session 22's build used one collection per conversation with no service to operate

Part of a ~107MB install alongside Haystack — vector search without infrastructure

Scales up to a real clustered service later without changing the mental model

Full entry →

Container-friendly app hosting — the agency's alternative to Vercel for things that need a real process running.

Pick this when: The app isn't a static front end — it needs a persistent server, a worker, or a self-hosted service.

Runs long-lived processes, not just serverless front ends

Named alongside Vercel as where the trainer's agency puts client MVPs

Full entry →

A browser IDE that grew a vibe-coding agent — build, run and host in one tab.

Pick this when: You want the generated app to live somewhere runnable immediately and you like an IDE view rather than pure chat.

Built a working blog in the BC4 bake-off — a real result, not a shell

IDE plus hosting in one place, so there's no deploy step to learn

Full entry →

Proper email delivery services — what you move to when a workflow's Gmail node stops being enough.

Pick this when: You're sending to more than a handful of people and deliverability, unsubscribes and templates start mattering.

Built for bulk: multi-recipient sending without tripping spam heuristics

The named upgrade path from BC4's Gmail-node newsletter

Full entry →

Cheap rented compute — roughly $10 a month for a VM that runs n8n and Ollama when your own hardware won't.

Pick this when: Local hardware is the blocker (the course singles out Intel laptops) and you'd rather rent than upgrade.

About $10/month to move the whole local stack off your machine

GPU options for model workloads local hardware can't touch

Full entry →

A managed back end in a box — Postgres database, auth, storage, and edge functions — with a generous free tier, so vibe-coded apps get real infrastructure.

Pick this when: You're graduating an app out of a vibe-coding platform's walled garden and want real Postgres you control — vs Lovable Cloud's zero-setup lock-in or Convex.

Row-level security (RLS) — table-level protection the course treats as non-negotiable

Real Postgres underneath — nothing proprietary to migrate off later

Edge functions keep API keys server-side, out of your front end

Full entry →

Push a repo, get a live URL — the course's default free hosting for anything front-end.

Pick this when: You need a shareable link today and the app is a web front end; it's the free recommendation throughout.

Deploys straight from a GitHub repo with no configuration

Free tier good enough for client demos and learner projects

Part of the course's 'serious' stack: Claude Code + Supabase + Vercel

Full entry →

The free CMS under a third of the web: turns a folder of site files into manageable media, posts, pages, plugins and themes.

Pick this when: You want ownership, the plugin ecosystem, and portability across hosts — the LWP stack's foundation.

Biggest CMS in the world; free software installed on any hosting

Posts/comments heritage explains its architecture (born as self-publishing freedom)

Custom post types make it a general content database, not just a blog

Full entry →

Proper email delivery services — what you move to when a workflow's Gmail node stops being enough.

Pick this when: You're sending to more than a handful of people and deliverability, unsubscribes and templates start mattering.

Built for bulk: multi-recipient sending without tripping spam heuristics

The named upgrade path from BC4's Gmail-node newsletter

Full entry →

Phone numbers and SIP trunking — the plumbing that connects a voice agent to the actual telephone network.

Pick this when: You need real numbers, especially outside the US, and you don't want to pay a voice platform's resale markup.

Numbers in effectively any country, where voice platforms typically resell US/CA only

SIP trunking connects those numbers to the agent platform

Clients host their own account, so the phone bill and the liability stay theirs

Full entry →

The WordPress plugin that turns posts into structured data: custom post types, taxonomies, and validated custom fields — the data layer of the LWP method.

Pick this when: You're modeling client-editable content on WordPress — Reno's insistence: 'everything is in one package,' vs CPT UI (harder) and JetEngine (paid).

Post types AND fields in one free plugin (2M installs cited in-course)

Backend-UX controls: instructions, validation, prepend/append labels, field widths

Safe URL renaming via custom permalinks — the rescue for the never-change-the-post-type-key rule

Full entry →

An authentication framework for TypeScript/Next.js apps — the auth layer Claude's plans now select by default for marketplace-grade builds.

Pick this when: Your generated app needs real sign-in and you're in the Next.js ecosystem — it's what the model will likely propose anyway.

Model-selected in the s14 live build without being asked for

Reported as joining Vercel (on-screen banner) — ecosystem-aligned

Full entry →

Open-source AI orchestration framework for building production-grade RAG pipelines and agents — the LEGO blocks under a custom answer engine.

Pick this when: You want a self-hostable, provider-swappable RAG core (OpenAI for demo, Ollama for production) rather than a hosted RAG service.

Tiny real footprint: ~107MB installed with embedded Qdrant in Session 22's measured comparison — while RAGflow demanded 16GB RAM + 50GB disk

Provider-agnostic by design — the same pipeline ran OpenAI and Ollama adapters

Pairs with an embedded vector store, so single-tenant RAG needs no database service at all

Full entry →

The code layer under most agent tooling — LangChain for chains and tools, LangGraph for stateful multi-step agents.

Pick this when: You're writing the agent in code rather than on a canvas — or you want to know what n8n's AI nodes are actually doing.

n8n's AI features are built on it, per the BC2 trainer — the canvas is a UI over this

LangGraph handles genuinely stateful agents, not just linear chains

The course's advice: point a coding agent at the docs rather than learning it by hand

Full entry →

Vercel's React framework — the base LEGO block of the course's modern web builds, and the server-rendering answer when SEO matters.

Pick this when: You're building a real site where crawlers and AI engines must see full HTML — SSR/SSG out of the box.

The foundation of the wrapper tower: components → shadcn → paid kits all sit on it

The migration target when client-rendered (Vite) sites need search visibility

Full entry →

Open-source vector database with an embedded mode — the searchable memory a RAG system stores its chunks in.

Pick this when: You want vector search inside the process (single-tenant, on-prem, laptop-sized) instead of a hosted vector-database service.

Embedded mode runs in-process — Session 22's build used one collection per conversation with no service to operate

Part of a ~107MB install alongside Haystack — vector search without infrastructure

Scales up to a real clustered service later without changing the mental model

Full entry →

Videos as React code: programmatic MP4 rendering with no video model anywhere in the loop — deterministic, editable, essentially free.

Pick this when: You want structured product/explainer video you can edit surgically (timeline studio, re-render) rather than diffusion-model clips you can only regenerate.

Official vendor skill bundle installs the company's own expertise (npx skills add)

npx remotion studio: scrub the literal timeline, name the broken frame, prompt the fix

Design-system continuity: builds videos in your site's own colors when run in the same session

Full entry →

The styling combination that makes a vibe-coded app stop looking vibe-coded.

Pick this when: Your generated app has the default purple-gradient look and you want it to pass as production.

Naming them in the prompt is the entire fix — no design skill required

shadcn's components are the ones every polished AI-built app is quietly using

Works with the reverse-engineering trick: screenshot a UI you like and ask for it in these terms

Full entry →

Browser design that non-designers can actually finish — and now an AI connector that generates editable drafts in chat.

Pick this when: You need a decent-looking visual artifact and you're not going to open a real design tool.

Generated designs open in Canva for editing — you get a draft, not a dead image

The flagship ChatGPT app demo: one prompt, finished invitation designs in-chat

Full entry →

The WordPress page builder: free version takes over the page content box with widgets; Pro overrides theme parts (header, footer, post templates) and adds dynamic content.

Pick this when: You build client sites on WordPress and want visual editing with real dynamic-content architecture underneath — accepting plan-tier gates on the pro features.

Theme builder that overrides (not builds) WordPress theme parts with the same editor

Dynamic content + custom post types turn pages into renderings of single-source data

Saved templates and a widget library replacing single-purpose plugins

Full entry →

A hand-drawn-style whiteboard — the course's thinking surface for node anatomy and workflow mind maps.

Pick this when: You want to explain a structure fast and the sketchy look signals 'this is a draft, argue with it'.

Deliberately informal styling that invites correction rather than approval

Boards export as JSON, so a diagram becomes a shareable, editable artifact

Free, instant, no account needed to start

Full entry →

The professional design tool — and an MCP server that lets an AI design in it without you opening it.

Pick this when: Real design work, or when you want an agent to produce design artifacts programmatically.

Its MCP server was BC5's headline possibility demo — design without opening Figma

The industry standard, so its file format is the lingua franca of handoff

Full entry →

Anthropic's design-specialist plugin: 'a trained employee with highly UI/UX design ideas' vs the model's generic default output.

Pick this when: Any generated page that humans will judge — the before/after in session 12 is the proof.

Visible quality jump on landing pages, demonstrated live

Auto-invoked once installed when design tasks appear

Full entry →

HeyGen's open-source video skill for Claude Code: skill + effects catalog + one prompt in, storyboarded brand-true explainer video out.

Pick this when: You want the storyboard-and-frames pipeline with stronger subtitles than Remotion, free, driven entirely by a skill.

Reads your code base to extract the design system before storyboarding

Writes a reviewable storyboard.md, then renders frames with parallel self-checking workers

Real-world proof: the trainer's session-to-YouTube-shorts pipeline with face tracking

Full entry →

Videos as React code: programmatic MP4 rendering with no video model anywhere in the loop — deterministic, editable, essentially free.

Pick this when: You want structured product/explainer video you can edit surgically (timeline studio, re-render) rather than diffusion-model clips you can only regenerate.

Official vendor skill bundle installs the company's own expertise (npx skills add)

npx remotion studio: scrub the literal timeline, name the broken frame, prompt the fix

Design-system continuity: builds videos in your site's own colors when run in the same session

Full entry →

The styling combination that makes a vibe-coded app stop looking vibe-coded.

Pick this when: Your generated app has the default purple-gradient look and you want it to pass as production.

Naming them in the prompt is the entire fix — no design skill required

shadcn's components are the ones every polished AI-built app is quietly using

Works with the reverse-engineering trick: screenshot a UI you like and ask for it in these terms

Full entry →

Vercel's component generator — the original 'describe a UI, get React' tool, now with prebuilt templates.

Pick this when: You need polished front-end components rather than a whole app, especially inside a Next.js/Vercel project.

The OG of the category — it defined component-level generation

Prebuilt templates that can be wired to an n8n back end

Full entry →

The LWP trainer's palette-and-typography generator (site + Figma plugin) - version 2 builds two coordinated color palettes and guides font pairing for the course's 8-slot color system.

Pick this when: You are at the visual-direction / design-system step of a build and want course-consistent colors and fonts fast instead of hand-assembling them.

Version 2 generates TWO coordinated color palettes - matching the course's light/dark or primary/secondary section rhythm

Ships as both a web tool and a Figma plugin, so palettes land directly in the working design file

Influential enough that a Divi plugin was built inspired by it (per the trainer)

Full entry →