Vefskólinn · The Fundamentals

Getting started
with AI

You describe. It builds. You decide.

>

press → to begin

Today's route

1Why now
2Chat vs agent
3Pick your tool
4The project
5Explore the code
6Hand-in & setup

then we install it together.

The rule

You have always been allowed to use AI.

From this guide on, you are required to.

And for the first time, we teach you how.

no more sneaking. it's the job now.

Typing was the cheap part

🎯

Specify

Know what you want before you ask. Pages, content, breakpoints, what “done” means.

🧭

Direct

Tell the assistant precisely. Give it the design. Correct it when it drifts.

🔍

Verify

Run it. Resize it. Compare it to the design. Ask why when the code and the browser disagree.

The assistant types. You specify, direct and verify. That is what a developer is now.

Chat vs agent

💬 Chat

  • Lives on a website
  • You copy and paste every file
  • Forgets your project between messages
  • Fine for questions and explanations
agent · ~/my-site
> build the homepage from design.png with Tailwind

🤖 Agent

  • Lives in your editor or terminal
  • Reads and writes your files itself
  • Runs commands, sees the errors, fixes them
  • Remembers the whole project

Use an agent for this guide. Chat is the fallback when you run out of tokens.

Pick your tool

Any assistant is allowed. These three get the best support.

Claude Code

Anthropic · Smári uses this

npm i -g @anthropic-ai/claude-code

Terminal agent. Also in VS Code.

Codex

OpenAI · Jakub uses this

npm i -g @openai/codex

Terminal agent. Also in VS Code.

Copilot

GitHub · free with the student pack

VS Code → Extensions → Copilot

Agent mode inside VS Code.

Recommendation: one basic subscription. If you cannot, the next slide is for you.

Paying for it (honestly)

Apply today

GitHub Student Developer Pack

Copilot free for verified students, plus JetBrains, cloud credits and more. You are enrolled at an accredited school, so you qualify.

education.github.com/pack

Google AI Plus

A free year for students in 140+ countries until the end of 2026. Check whether Iceland is on the list.

OpenAI & Anthropic

OpenAI's student offer is US only. Anthropic has no student discount. Both have free tiers that run out fast.

Free tiers change monthly

Expect to hit a limit mid-task. Save your work, switch tool, keep going. That is normal, not failure.

a subscription costs less than the coffee you'll drink debugging without it.

How to ask

> make me a website for a coffee shop
> Build the two pages in design.png (home, menu) as a static site
  using Tailwind. Match the layout, colours and type sizes in the design.
  Mobile-first: one column under 768px, the three-card grid above it.
  Use semantic HTML and make every link reachable with the keyboard.
  When you are done, tell me how to run it locally.

📎 Give it the design. A screenshot or Figma export beats any description.

📏 Name the constraints. Framework, breakpoints, pages, accessibility.

🏁 Say what “done” is. Otherwise it decides for you.

❓ Ask “why”. Not just “what”. The explanation is the lesson.

The project

Your prototype, built twice

🎨
Your hi-fi prototype from the Design UI guides
Build Aframework 1
Build Bframework 2
📖
Your teaching site the AI explains what it built
8–10hthe AI does the typing
2+frameworks, same design
1page that explains it all

Step 1

Choose two frameworks

Tailwind

Utility classes in your HTML. md:grid-cols-3 and done. The most common choice today.

Sass

CSS with variables, nesting and mixins. Not a framework, a preprocessor. Ask the AI why that matters.

Bootstrap

Ready-made components and a 12-column grid. The classic. Everything looks like Bootstrap unless you fight it.

shadcn/ui

Copy-in components built on Tailwind and React. Modern, but you will need a build step.

Something else

Bulma, UnoCSS, Open Props, plain CSS with custom properties. Ask the AI what it would pick and why.

> I have a two-page design (attached). Explain the difference between Tailwind, Sass,
  Bootstrap and shadcn for a beginner, and recommend two of them for this design. Explain why.

Step 2

Let it build

  1. Export your prototype as an image (or share the Figma link).
  2. One repo, one folder per framework: tailwind/, sass/…
  3. Give the agent the design, the framework and the constraints.
  4. Run it. Look at it. Tell the agent what is off. Repeat.
  5. Then do it again with the second framework.
The only rule

The AI writes every line.

You do not fix things by hand. You describe what is wrong and let it fix them. Directing is the skill.

(yes, even the one-character typo.)

Step 3

Look with your own eyes

localhost:5173 · 1100px · lg
☕ KaffiHomeMenu
Good coffee, slow mornings.
Tailwind
<div class="grid grid-cols-1
     md:grid-cols-3">
Sass
.cards { display: grid; }
@media (min-width: 768px) {
  .cards { grid-template-columns: repeat(3, 1fr); }
}

Same behaviour, two very different places in the code. Find it in both of yours.

When the browser disagrees with the code, ask: “why does it look like this?”

Step 4

Explore the code with the AI

required

Where is the responsiveness controlled in each version? Show me the exact lines.

fidelity

Compare this to my design. List three differences and fix one.

swap

What would have to change to move this from framework A to framework B?

a11y

Can I use this page with only the keyboard? Prove it.

curious

Pick anything you find interesting. “What does this do and why is it here?”

honest

Which of the two took more prompts to get right? Why?

Every answer goes on your teaching site, linked to the lines in each build.

Step 5

Your teaching site

teaching site

Tailwind vs Sass: what I learned

1 · Why these two

the AI's comparison from step 1

2 · Where responsiveness lives

snippets from both, with links to the lines

3 · Three differences from my design

and which one got fixed

4 · What I found interesting

your curious questions, answered

📖 The AI generates it. One page, every question you asked, every answer it gave.

🔗 Links to all builds. Every explanation points at the exact code in each version.

👀 Made for your reviewers. They use a different AI. Review two classmates and you have three explanations of the same thing.

your own textbook, written for you.

Hand-in

What you return

  • ✓
    One GitHub repoa folder per framework, plus the teaching site
  • ✓
    Build A and Build Bthe same prototype, two frameworks, both running
  • ✓
    The teaching sitelinks to every build, the required responsiveness answer, and your own questions
  • ✓
    A reviewof a classmate. Read their AI's explanations, compare to yours
8–10hIf you are at 12, you are fixing things by hand. Stop. Tell the agent.

the AI writes. you judge.

Right now, together

Let's set it up

1

Choose

Claude Code, Codex or Copilot. Apply for the student pack while you wait.

2

Install & log in

npm i -g @anthropic-ai/claude-code
claude
# or
npm i -g @openai/codex
codex
3

Say hello

In an empty folder, ask it to create index.html with your name in it. Open the file. It wrote it.

Nobody leaves until their agent has written one file.

Now go build it
twice.

You describe. It builds. You decide.

good code. brighter tomorrows. ☕

Keyboard

→ / space
next step
←
previous
Home / End
first / last slide
N
speaker notes
F
fullscreen
P
flip the prompt (slide 8)
?
this help