Create a small local utility that opens or organizes websites, apps, folders, documents, notes, checklists, tools, or project links.
This guide is designed for a need-to-know build path. Each idea appears when it becomes useful, not before.
Keep going through the final reflection — [rewarding] is the part most people do not expect.
| Path | Time | Best for | Keep it to |
|---|---|---|---|
| Verbatim Tour | Under 30 minutes | Seeing how Verbatim works | One page, one category, a few sample links |
| Guided Build | 30–60 minutes | Building something useful while following the pattern | Apps/tools, websites, files/folders |
| Thoughtful Build | 30 minutes–2+ hours | Designing something personal and considered | Categories, tabs, assets, style, storage, refinements |
All three paths can fit within 5 Verbatim writing runs when you plan before the first Recording Sheet and keep version one focused.
Choose what this first launchpad is for. Do not design every detail yet. Just choose the use case.
Pick the simplest layout that matches your time path.
You can combine modes later. A Gaming tab, Creator tab, and Builder tab can become profiles.
Use this prompt now. It should start a planning conversation, not produce code.
I want to build a simple Personal Launchpad as my first AI-assisted software project. I am using Nodarama Verbatim to help apply changes safely. The goal is to complete a small working version in 5 Verbatim writes or fewer if possible. Help me plan before writing code. Ask me only the most important beginner-friendly questions first: - whether this is a fast Verbatim Tour, Guided Build, or Thoughtful Build - what kind of launchpad I want: gaming, creator/social, builder/developer, work, school, personal, or mixed - what I want it to help me open, track, or organize - whether I want one simple page or multiple tabs/categories - whether I want it very simple or more dashboard-like - whether I use Windows, Mac, or both - what shortcuts, links, documents, folders, or apps I want included - whether I expect to use images, icons, or other assets - how much coding explanation I want - whether I want you to make most decisions or ask me before each major choice Please help me decide: - what belongs in version one - what should wait until later - whether I need an assets folder - what the page should display - what should happen when I click or use something Avoid overwhelming me with framework choices. Assume simple HTML, CSS, and JavaScript unless there is a strong reason not to. Do not write code yet. Do not prepare a Recording Sheet yet.
Keep talking with AI until the first version feels clear. Ask for help finding app paths, folder locations, or links if you need it.
Before the first write, decide whether your project only needs files or also needs folders for resources.
The simple version usually starts with:
index.html style.css script.js
If you expect images, icons, screenshots, logos, or sound files, consider creating an assets folder yourself before the first write.
personal-launchpad/
index.html
style.css
script.js
assets/
icons/
images/You do not need an assets folder for one image. You may want one if you expect five.
You do not need to study code first. Just know what each file is responsible for.
When the plan is ready, use Verbatim before asking for the first Recording Sheet.
Use this only after planning is complete and after you paste Copy Tree + Copy Contract into the AI chat.
I am ready for the first Verbatim Recording Sheet. I am providing: 1. the project tree from Verbatim 2. the aiVerbatimRecordingContract from Verbatim Use the project tree as the map of what exists and where files should go. Use the recording contract as the required format for the Recording Sheet. Prepare one Recording Sheet for the first Recording Session. For this first build, create the core project files together: - index.html - style.css - script.js If I created an assets folder or described an assets structure, reference it correctly. Do not invent asset files that do not exist unless we agreed to create placeholders. The first Recording Sheet should include: - HTML structure - CSS visual definitions - JavaScript behavior and interactions - starter categories or tabs if agreed - shortcut cards or placeholder links - any simple notes, checklist, or storage behavior we agreed on Use Write Actions for new files. Keep it beginner-friendly. Do not add unnecessary frameworks, build tools, databases, installers, or advanced packaging. Output only the Recording Sheet JSON array, with no extra explanation before or after.
Manual copy/paste into Verbatim is recommended for this first workflow because it helps control the number of writing runs.
index.html in your browser.Notice what works and what needs to change.
Customization begins after you see the first version. Choose one focused change at a time.
I tested the Personal Launchpad. Help me plan the next Verbatim Revision Sheet. Here is what worked: [write what worked] Here is what needs correction, enhancement, or troubleshooting: [write what needs changing] I may also want to add or adjust: - links or shortcuts - tabs or categories - images, icons, or assets - visual style - notes or checklist behavior - storage behavior - layout or spacing - another simple function Please group related fixes into one Recording Session when practical so I can keep the number of writes low. Before writing the Revision Sheet, briefly summarize: - what you will change - which files are affected - whether this is a correction, refinement, or added feature - whether any folder or asset organization should change Then ask for my approval before preparing the Revision Sheet.
Prepare the approved Verbatim Revision Sheet. Use the aiVerbatimRecordingContract format. Prefer Revision Actions for surgical edits when possible: - replacestring - replaceblock - replacefunction - insertbefore - insertafter Use rewritefile only if a surgical edit is not practical. Output only the Recording Sheet JSON array, with no extra explanation before or after.
index.html, style.css, and script.js together.This is not a law. It is a quick-start shape for this project. Bigger features can become their own phase later.
Do not skip the final reflection. The next screens slow the process down just enough to help you notice what you actually practiced.
Reflection 1 of 3
You just built a real utility. It may be simple, but it is yours.
What kind of launchpad did you make?
Reflection 2 of 3
When imagination starts moving, one of the hardest skills is knowing where to stop. Bigger ideas need a place to wait.
Reflection 3 of 3
You built a small tool, but you practiced a larger pattern.
You defined intent. You controlled scope. You categorized functions. You set boundaries. You separated what happens from what is displayed. You gave AI useful context. You reviewed before trusting. You learned that code can be approached on a need-to-know basis.
You also practiced folder organization, visual design choices, action planning, storage thinking, navigation planning, mode/profile thinking, and deciding what AI needed to know before writing.
They apply to everything: apps, websites, automations, dashboards, workflows, creative tools, business systems, and AI collaboration.
The launchpad is small. The thinking is universal.
You have seen and participated in a larger pattern. Now practice it and build everything you want.
Verbatim is here to help you repeat the pattern:
Describe it. Organize it. Bound it. Build a small version. Review the work. Improve it. Keep going.
You do not have to learn all of coding before you build something useful. Build on a need-to-know basis.
This first launchpad was only the beginning.
Do you know someone who might benefit from the reflection lesson in building their first launchpad? Someone who says they are “not technical.” Someone curious about AI. Someone with ideas but no obvious path to build them.
They may think they are just building a small launchpad. But by the end, they may realize they are practicing universal skills for building strong and effective systems.
Hey, I found a guided first-build workflow for Nodarama Verbatim that helps you create a Personal Launchpad — a small utility for your own links, tools, notes, shortcuts, or projects. The useful part is not just the app. At the end, it walks you through what you actually practiced: intent, scope, categories, boundaries, what happens vs what is displayed, AI context, review, and learning code on a need-to-know basis. It is a surprisingly good way to feel what building with AI can be like. Try the First Workflow Guide here: [link]
Your first launchpad was only the beginning. Now that you have seen the pattern, you can repeat it.
Verbatim helps you turn AI conversations into real local project work with review, History, DUBS, project context, and guardrails.
If you are ready to keep building without stopping at the first win: subscribe to Verbatim.