CoachingAboutVideosBookFAQContact
DE|EN
Book Free Consultation

What this is about

The videos in this hub are about concrete builds: a sticker app, a website, small offline tools and the path from design to code. These are not perfect product launches. They are working examples.

The pattern is the same every time: keep the scope small, plan first, build second, check after. That is what separates useful AI work from vibe coding that only looks good in a screenshot.

How I would read the workflow

  • 1. Start with a real problemThe small HTML app and StickerLog show why concrete friction beats an abstract app idea.
  • 2. Do not skip designClaude Design is not a replacement for product thinking, but it helps make an idea visible before code is written.
  • 3. Build locally and versionedThe Wix rebuild shows why files, GitHub and Netlify often work better for AI-assisted websites than a closed builder.
  • 4. Plan for a second lookClaude Code vs Codex and StickerLog show why review, debugging and a second opinion are quality control, not bureaucracy.

Relevant videos

Some videos intentionally appear in more than one hub when the context is useful there too.

FAQ

For small, clearly scoped tools, yes. You still need judgment, testing and a tight scope. The more critical the system becomes, the more technical review matters.

Many problems are too small for an IT project and too specific for standard software. One local file can be exactly right.

It shows how AI can rebuild a website in a way that is not only faster, but also more controllable and machine-readable.

Do not start with code. First clarify the problem, data, boundaries, user flow and checks. Then the AI becomes much more useful.

All videos

Want to build cleaner AI workflows?

I help freelancers, consultants, coaches and small teams turn AI tools into real workflows. Practical, inspectable and matched to how you actually work.

Book a free strategy call