Context + specifications
Project knowledge, LLM wikis, and clear requirements.



Websites, apps, and useful experiments.
Learn by building together.
Bring an idea. Share what you learn.
oslovibecoding.tech
Example: joining an event.
What you see
Does the work
Remembers it
Keep the headline and photo. Stack the details.
3Make something together.
HTML gives the content a structure.


Bring an idea. Build together.
Works on project files, tests, and fixes.
Helps build, review, and improve code.
An AI coding editor for your project.
Coding assistance and agent workflows.
Build and run an app in the browser.
Generate interfaces and web apps.
Build web apps through conversation.
Create websites and apps in the browser.
Think about the experience you want.
Then talk to your coding agent.
The purpose, the experience, and the priorities.
Plans, builds, and makes changes.
Try it. Give feedback. Decide what ships.
Who is it for? What should it do?
Share content, images, and constraints.
Clear up questions before building.
Keep unrelated parts of the page intact.
Use a screenshot, an error, or an exact example.
Test it. Keep secrets out.
The files you edit and preview.
HTML + CSS + JavaScriptThe project and its saved versions.
Repository = project folder + history.Publishes your site at a public URL.
Deploy means publish a version.Other hosting routes: GitHub Pages and Replit Publishing.
Build it together. Publish it on Vercel.
Someone looking for people to build with.
A headline, a photo, and a button that opens the plan.
A working page to share.

Bring an idea. Build a first version with people nearby.
Pick an idea, build a first version, and test it with someone.
Open Claude Code, Codex, or your preferred coding tool.
Create a folder named oslo-hack.
Sign in to GitHub and Vercel.
Browser builders need a file export or GitHub connection.
One clear button
A clear headline, the supplied photo, and a button that opens the plan.
No account, payment, signup form, or database.
The button works, the phone layout fits, and the public link opens.
Build a one-page website called Oslo Hack.
It helps people in Oslo find others to build small projects with.
Use photo.jpg. Colors: #110F17, #FBF7F0, #FF5A2C.
Include navigation, a headline, an intro, Meet / Build / Share, and a footer.
Add a button that shows and hides a short session plan.
Use index.html, style.css, script.js, and photo.jpg. No libraries.
Make it work on a phone. Do not add login, payments, or a database.
First explain your plan and ask about missing information.Expected: the plan opens.
Actual: nothing happens.
Evidence: show the agent the page.
Review this website before publishing.
Phone layout, keyboard access, working links, and clear button labels.
Issues, fixes, and retest results.
# Website review
1. Open desktop and phone layouts.
2. Check images, links, and buttons.
3. Test Tab and Enter navigation.
4. Describe issues with evidence.
5. Fix agreed issues, then retest.
6. Ask before publishing.Name the project oslo-hack.
Upload the website files and photo at the top level.
Save a checkpoint with a short description.
Commit message
First working website
Connect GitHub and select your oslo-hack repository.
Confirm the project folder contains index.html.
Publish the project and open the URL Vercel gives you.
Plain HTML, CSS, and JS need no build step.
Try a private window or another device.
Check the photo, layout, button, and links.
Ask someone else to try it.
Add a three-question FAQ below the content.
Each answer opens when clicked.
Keep the headline, photo, colors,
and plan button unchanged.
Check phone layout and keyboard access.
Show me which files changed.No. Start with one small idea and learn as you build.
A laptop, a charger, and something you are curious about.
Yes. Join someone else's project or try the workshop example.
Add a section in the frontend.
Registrations need a backend and database.
Measure speed, errors, and cost.
"What needs to change for this feature, and what can stay simple?"
Open your website. Let someone else try it.
Who is it for, and what can they do?
A button, an answer, or a useful change.
What improved after feedback?
Project knowledge, LLM wikis, and clear requirements.
Define done, check results, and improve one step at a time.
Tools, skills, memory, tests, and safe boundaries.
Backends, databases, security, and deployment workflows.
Dates and registration coming to oslovibecoding.tech.
Any questions?
oslovibecoding.tech