
mrhinkle/vibe-coding-for-non-technical-professionals
Developer toolsA six-hour hands-on class for non-technical professionals: simplified SDLC, GitHub and Vercel, a website, a browser game, and reusable chatbot skills.
Overview
A full-day, hands-on class for business professionals with no programming experience. Use your favorite chatbot to create two things you can share: . The class starts with 30 minutes on how software is developed. Students then learn GitHub, Vercel, and a repeatable workflow: describe the outcome, build a small version, check what it actually does, save progress, and publish. six teaching hours (360 minutes), plus lunch and breaks. course documentation assembled; seven runnable website starters are included; game checkpoints and classroom rehearsal remain preparation work. The existing presentation is included as reference. Complete the instructor preflight before teaching. for the student route. Point an authorized coding assistant at this repository and ask it to read . If your chatbot cannot access the private repository, download and attach , a single text file containing the current lessons, prompts, templates, and skills.
README
Vibe Coding for Non-Technical Professionals
A full-day, hands-on class for business professionals with no programming experience. Use your favorite chatbot to create two things you can share: a simple website on Vercel, then a browser game.
The class starts with 30 minutes on how software is developed. Students then learn GitHub, Vercel, and a repeatable workflow: describe the outcome, build a small version, check what it actually does, save progress, and publish.
Duration: six teaching hours (360 minutes), plus lunch and breaks.
Instructor: Mark Hinkle.
Status: course documentation assembled; seven runnable website starters are included; game checkpoints and classroom rehearsal remain preparation work. The existing presentation is included as reference. Complete the instructor preflight before teaching.
Give this course to your chatbot
Start here for the student route. Point an authorized coding assistant at this repository and ask it to read AI-START.md. If your chatbot cannot access the private repository, download and attach AI-COURSE-PACK.md, a single text file containing the current lessons, prompts, templates, and skills. If file upload is unavailable, paste the entry point and current lesson.
Read AI-START.md from this repository or the course materials I attached. Be my patient guide. Tell me which files you actually received, ask whether I am starting or continuing, and guide me through the website first, then the game. Use one checkpoint at a time and show me how to check each result.
Private repository access does not transfer automatically to your chatbot. Students need repository access or an instructor-supplied copy. Instructions never require sharing passwords or access tokens. The website and game belong in separate learner-owned repositories.
Start here
| You are… | Open this |
|---|---|
| Preparing to attend | Pre-class laptop preparation, then account and chatbot setup |
| Wanting an illustrated overview | 18-page participant PDF, Markdown, or offline HTML |
| Taking the class | Student workbook |
| Teaching the class | Instructor guide and timed lesson plan |
| Building the website | Website and lifecycle skills |
| Building the game | Game skills, recipes, and prompts |
| Following a worked example | Website walkthrough plus Alien Tic-Tac-Toe and quiz-game walkthroughs |
| Stuck or seeing an error | 30 troubleshooting paths and help request template |
| Wanting multiple AI helpers | Three collaboration options and sample AGENTS.md |
| Changing chats or stopping for the day | Project state template |
| Looking for words or prompts | Glossary and prompt library |
| Updating the slides | Presentation reference and adaptation plan |
| Checking where the material came from | Source map |
What students will accomplish
- Explain the software development lifecycle in plain language.
- Use a chatbot, GitHub, and Vercel for different parts of the work.
- Turn an idea into a small brief with observable completion checks.
- Build and publish a one-page website with a meaningful link or button.
- Create a playable game with understandable rules, controls, results, and replay.
- Test the actual experience with another person and improve it from observations.
- Leave with saved project files, test notes, release records, and next steps.
The target is two working URLs. If an account or hosting problem prevents publication, retain the working files and record the specific blocker.
The day
| Teaching time | Minutes | Activity |
|---|---|---|
| 0:00–0:30 | 30 | How software gets developed: simplified SDLC |
| 0:30–1:00 | 30 | GitHub, Vercel, and your chatbot: setup and capability check |
| 1:00–2:30 | 90 | Project 1: define, build, test, and publish a simple website |
| 2:30–2:45 | 15 | Tour the All Things AI Arcade and choose a game pattern |
| 2:45–3:05 | 20 | Define the game and its rules |
| 3:05–4:10 | 65 | Build the first playable version |
| 4:10–4:40 | 30 | Improve appearance and feedback |
| 4:40–5:20 | 40 | Partner playtest, repair, and tune |
| 5:20–5:45 | 25 | Publish the game and check the live experience |
| 5:45–6:00 | 15 | Demonstrations and handoff |
The times above exclude lunch and breaks. A sample day is 9:00 a.m.–4:30 p.m. with a 45-minute lunch and three 15-minute breaks.
Two small projects
Project 1 — A simple website. Choose a personal introduction, event, hobby, community group, or fictional business. Build one page with a clear heading, two or three sections, a visual treatment, and a working primary action. Save it to a learner-owned my-first-site repository and publish it on Vercel.
Project 2 — A browser game. Choose Alien Tic-Tac-Toe, a five-question quiz, or a one-button space dodger. In the featured game, selecting a square starts an alien battle: win to claim X; lose and the alien claims O. Mark proposed this new classroom concept; the other recipes adapt patterns from the All Things AI Arcade. Keep a short start → play → result → restart loop. Use a separate my-first-game repository and Vercel project.
Both projects can be static HTML, CSS, and JavaScript. Accounts, databases, multiplayer, global leaderboards, and paid APIs are outside the core exercises. A real commercial website needs a hosting plan appropriate to its use; see the setup guide.
Use your favorite chatbot
The portable route works with a chatbot that can return complete runnable files:
- Open a skill below and paste or attach its
SKILL.mdto your conversation. - Add your idea or the previous stage’s output and use the matching prompt in the guide.
- Save the returned files, open them in your browser, and check the result.
- Upload the checked files to your own GitHub repository and import it into Vercel.
A supported coding workspace can edit and save the files directly after you connect it. The setup guide distinguishes ordinary chat, GitHub connections, Claude Code, Codex, and deployment access. Native skill installation is optional; pasting a skill does not grant tools or account permissions.
Skill library
| Shared workflow and website | Game project |
|---|---|
| Understand the SDLC | Choose and define a game |
| Prepare accounts and workflow | Write rules and controls |
| Write the project brief | Build the playable loop |
| Scope the first version | Use the agreed game rules to limit scope |
| Plan the page and increments | Improve appearance |
| Build a small increment | Explain outcomes and replay |
| Check quality | Playtest and tune |
| Publish the website | Publish the game |
| Maintain and recover | |
| Demonstrate and hand off |
Repository contents
README.md Class overview and navigation
START-HERE.md Student entry point and copy/paste startup prompt
PRE-CLASS-PREP.md Mac/Windows setup, accounts, and readiness checklist
prep/laptop-check.html Offline file-opening and button/keyboard check
AI-START.md AI tutor workflow and honest capability checks
AI-COURSE-PACK.md Single-file chatbot handoff, generated from current docs
AGENTS.md / CLAUDE.md Course-repository assistant entry points
course-map.json Machine-readable course stages, files, and timings
instructor-guide.md Timed teaching plan and facilitation notes
setup-guide.md Accounts, connections, publishing, troubleshooting
skill-guide.md Ten shared skills and starter prompts
game-skills-guide.md Seven game skills and three beginner recipes
handouts/student-workbook.md Fill-in briefs, rules, tests, releases, and handoff
instructor/preflight.md Rehearsal and classroom preparation checklist
docs/ Worked examples, troubleshooting, agents, prompts, glossary
templates/ Learner AGENTS.md, state, help, agent tasks, and handoffs
guides/ Illustrated participant guide: PDF, HTML, Markdown, diagrams
skills/ Website and lifecycle SKILL.md files
game-skills/ Game SKILL.md files
presentations/ Existing six-hour deck, assets, and adaptation plan
repository-map.md Sources, inspected versions, and adaptation choices
licenses/ Original website material's license
tools/ Rebuild the guide and single-file course pack
Current readiness
The curriculum, 17 skill entrypoints, detailed self-study documentation, illustrated participant guide, and student templates are assembled. The 18-page guide uses the existing All Things AI logo and palette with explanatory diagrams. It is separate from the existing 51-slide deck preserved under presentations/reference-six-hour-class/. That older deck teaches one business application and includes database and email topics; it has not yet been rewritten for this two-project agenda.
Before class, revise the slides, prepare and test recovery checkpoints, rehearse each offered chatbot route, and playtest the selected game recipes. Seven standalone website starters are included and checked locally; playable game checkpoints still need preparation. Documentation checks are not a substitute for a classroom rehearsal.
The multiple-agent lesson is optional. It does not add a required block to the 360-minute agenda. Begin with one builder and one read-only reviewer; advanced native agents and isolated worktrees are extensions.
Sources and reuse
This course adapts Mark’s VibeCoding-a-Website, the existing private Presentations class folder, and patterns from the All Things AI Arcade. See the source map for pinned versions and attribution, and reuse notes for license scope. The repository is private so the existing presentation assets remain within the same visibility boundary.
Students proud of their game can prepare an optional Arcade submission. Mark and the All Things AI team can select games for a later Arcade addition; course completion does not automatically publish a game there.
Optional closing invitation: add vibe coding to your LinkedIn profile and post about your class experience, then send Mark the links for a skill endorsement. See the LinkedIn wrap-up guide.
Choose a website starter—or make your own
Open the starter collection: one vanilla page, two All Things AI fan-site designs, and four themes—dream restaurant, dream product, dream business, and pet. Download the course and open website-starters/index.html for the visual gallery. Every starter is a complete offline index.html; copy one into your own project. Follow brief → scope → plan before remixing it.
Recommended Tools
Try a different keyword or remove a filter.
Install
npx skillfish add mrhinkle/vibe-coding-for-non-technical-professionals