Tools & setup

The recommended stack and how to get it approved.

VIBE does not mandate a specific tool, since schools use what fits their existing tech agreements. But advisors ask us what we actually use, so we wrote a dedicated page with the stack, the AI platform comparison, the district compliance story, and step-by-step action items.

Full guide

Tools & setup

The recommended stack (Claude Code web + GitHub + Vercel), a Claude vs. Gemini vs. ChatGPT comparison, compliance posture for each tool, and an action-item checklist to run before week 1.

Open the tools guide →
Quick answer

If you only have five minutes

Claude Code web, GitHub, and Vercel make up the recommended stack. They are all browser-based, all compliant with 13+ terms of service, and all viable on a free tier. The whole stack runs on a Chromebook or an iPad with nothing to install. If your district has already approved a different AI (Gemini via Workspace for Education is common), please use that, since the curriculum is tool-agnostic.

District compliance: GitHub has the strongest compliance posture (Microsoft-backed, FERPA DPAs, SDPC-listed). Claude and Vercel require more legwork, so see the tools guide for the honest breakdown and the workarounds that have actually worked. Then see AI tool policies for the full compliance page.

Session plan

The twelve-week playbook.

A quick overview of what happens each week. The full curriculum has session-by-session plans with time maps, activities, and advisor notes for every week.

V · Wk 1

First build.

Every student makes something with AI in their first session. Advisor demos live, then students build. Comfort over mastery.

V · Wk 2

The conversation, not the command.

Students learn that iteration beats single prompts. Bad prompt vs. good prompt vs. great prompt, side by side. They improve their week 1 project.

V · Wk 3

First guide visit (or AI in the wild).

Career story and how AI fits in, open Q&A. If no guide is available, the advisor leads an “AI in the real world” walkthrough using a short clip or article from a working professional.

I · Wk 4

Second field, second perspective.

Different field than week 3. With a guide if one is available (a site visit is great when possible), or a contrasting clip or article when one is not. The contrast between fields is the lesson.

I · Wk 5

What do you want to build?

Brainstorm without filtering. Each student writes a three-sentence napkin pitch: what it is, who it's for, what problem it solves.

I · Wk 6

Scope and plan.

Project scoping worksheet. Advisor 1:1s to confirm scope. Every student leaves with an approved project and a plan.

B · Wk 7

First working version.

Build sprint. Rule of the day: working beats beautiful. Something on screen by the end of session.

B · Wk 8

Build sprint, adding features.

Each student states a session goal and builds toward it. Core features take shape.

B · Wk 9

Guide feedback or peer review.

Outside perspective on every project. Midpoint check. Scope-down conversations happen here if needed.

B · Wk 10

Feature complete.

Core functionality done. Language shifts from "building" to "finishing." Polish begins.

E · Wk 11

Showcase prep.

Three-minute presentation framework. Students write, practice, and get feedback from a partner.

E · Wk 12

Showcase.

Families, administrators, sponsors, and press invited. Each student presents for three minutes. Celebrate shipped work.

Templates

Copy, adapt, send.

Ready-to-use templates for the most common tasks an advisor faces. Each one has been tested in pilot planning.

Communication

Guide invitation email

The exact email to send to professionals in your community. Copy it, fill in the blanks, and send. Available on the guides page.

Planning

Project scoping template

Students fill this out in weeks 6–7. Fields: project name, target audience, definition of done, tools needed, weekly milestones. Keeps scope realistic.

Communication

Parent introduction letter

Explains the program to families: what it is, what students will do, how AI tools are used responsibly, and what the showcase looks like.

Reporting

End-of-semester review

One-page template for advisors to capture what worked, what to change, and what to pass to the next advisor. The institutional memory of the program.

Legal & compliance

What schools need to say yes.

We know principals and district offices need specific documentation before approving a new program. These resources address the most common requirements.

Need help?

We will walk you through it.

If you are an advisor launching a cohort and need help with any of these resources, reach out. We respond to every email.

[email protected]