GritAI

Claude Community Oslo · Mesh · 21 Oct 2026

Claude Impact Lab.

Your team’s guide for the day. How to approach the task, the areas to choose from and prompts for Claude Code.

WHOWHATWHY
  1. 01Discuss and explore
  2. 02Ideate in groups
  3. 03Prototype together
  4. 04Showcase at the end

How to approach it

Six steps, one problem.

Start with a person and their problem, not with the tool. Most of the day goes to building and testing.

  1. 01

    Pick an area

    One of the three, as a team.

  2. 02

    Let Claude interview you

    One question at a time, to find the problem.

  3. 03

    Define the problem

    One person, what they might struggle with, and why. Before any solution.

  4. 04

    Build the smallest version

    One screen that works. Test it.

  5. 05

    Improve and expand

    Make it better, bigger or more ambitious.

  6. 06

    Show it

    Five minutes at the demos, mostly clicking through it.

09:30Welcome and teams10:00Pick a problem10:20Build11:45Lunch12:15Build13:15Demos
The day at Mesh, with most of it spent building

Problem areas

Pick one of three.

The areas come from the two questions at Claude Conversation. Use the questions under each to find a problem someone on your team knows well.

  1. 01

    My job

    What does AI mean for my job?

    • Which task eats the most of your week?
    • What do you wish you had time for?
    • Who in your field is falling behind, and why?
  2. 02

    My kids

    What is AI doing to my kids?

    • Where do children meet AI today, at home or at school?
    • What do parents or teachers worry about?
    • What would help a family talk about it?
  3. 03

    My community

    What is AI doing to my community?

    • Who in your neighbourhood is left out?
    • Where do you meet people today, in clubs, groups or online?
    • What could help people help each other?

How to work

Three steps from problem to prototype.

  1. 01

    Define the problem

    Pick a challenge or an opportunity AI brings to someone at work, at home or in the community. Name who it affects, what changes for them and why it matters.

  2. 02

    Explore solutions

    Ask Claude for many different ways to solve it before you pick one. Include a bold one.

  3. 03

    Prototype and imagine

    Build a first version people can click, and sketch how it could look when it is finished.

Get started

Quick start.

Paste it into Claude. Claude reads the brief for the day, then interviews the team.

Use this if you do not know where to start

Claude
Help us get started. https://www.gritai.studio/meetups/claude-impact-lab/brief

Demos 13:15 to 14:00

Demo time 🎉

Five minutes per team, mostly showing it working.

The problem45 sRead the statementWho it is for45 sThe person it helpsShow it2.5 minClick through it liveWhat next1 minThe first step
One team's five minutes, part by part
Big stage

Want a bigger audience? There is a chance to show what you built on the big stage in the evening, if you want to.

Before you leave

Share the link with everyone on the team, agree on one step you can take this week, and swap contact details so the team can carry on.

The day on Luma Coming events

Be more creative with HTML

Three more words at the end.

Claude can build pages with sliders, steps and stories, but it only does it when you ask. Add a few plain words to the end of your prompt.

Clickable prototypeButtons and a formScroll storyA day, before and afterWhat-if sliderA number that changesBefore and afterSide by sideOne-page pitchProblem, who, first step
Five kinds of HTML page a team can show at the demo

Then give feedback

Do not try to say everything in the first prompt. Look at the page, say what is off, and add a few words each round. One good ending, from Thariq Shihipar at Anthropic, is the whole of his ELI5 skill.

“explain like I’m someone who knows nothing about this topic, using a HTML artifact with big pictures and few words”

Prompting Claude

How to talk to Claude.

Write to it like a capable colleague who has just joined the team. Plain language works best.

Prompts to copy

Paste one, fill in the brackets, read what comes back, then change it.

  1. 01Find the problemPlan

    Claude
    We are a team at a one-day build event. Our area is [area]. Interview us with five questions, one at a time, to find a real problem worth working on today. Then write it in the form who struggles with what, because why.

  2. 02Plan the smallest versionPlan

    Claude
    Write a short plan for the smallest version we can build in two hours. What it does, what it leaves out, and the one screen that matters most. Do not build anything yet.

  3. 03Build it as one pageBuild

    Claude
    Build the plan as a single HTML file we can open in a browser. Keep it to one screen. Use made-up example data, never real names or personal details.

  4. 04Check it worksBuild

    Claude
    Open the page in the browser and try it the way a first-time user would. Fix anything broken before you tell us it is done.

  5. 05Test it as the personTest

    Claude
    Act as [the person from our problem statement]. Use the page to [the task]. Tell us where you got stuck, then make the three changes that matter most.

  6. 06Tell the storyShow

    Claude
    Make our idea into one HTML page that tells the story of [who] before and after, as a page we scroll through. Then help us plan a five-minute demo.

When you get stuck

How could we …?Ask me questions firstWho struggles most with this?What if we …?Make it simplerShow me three different waysWhat is the smallest versionwe could build today?What could go wrong?Play the person who uses itHow can I bemore ambitious?Give me a bolder ideaTurn this into a clickable prototypeExplain it to a 12-year-oldWhat are we missing?Write the demo in three sentences
Starters to copy into Claude when you get stuck