11 articles
-
Prompt package, from design to screen in six prompts
Six prompts to copy that take you from a briefing to a built screen that actually looks like your design, with a description you read through yourself first.
Creating a design with AI actually works very well today. Things usually go wrong the moment your agent has to build that design. Then you get screens that work, but look different. That is why I simply listed the prompts I use myself, from the briefing to the built screen. The first two are for Google Stitch or another design tool. The others work in any agent that can read images. Count on about fifteen minutes per screen.
What you get
You get six prompts, in the order I use them. Two are for the design tool, and four are for your agent: describe, adjust, build and compare. You already get the first one here. It lets your design tool explore three directions instead of one, so I think you see much faster what appeals to you.
Free with an accountRead -
Let your agent tell you what he sees first
An agent that has to build a design often turns it into something else. I let him describe the design first, and only build it afterwards.
Last weekend I rebuilt my website with AI. I absolutely did not want it to look like all those typical AI websites. So I went through all the steps that I also show in my training courses. First brainstorming, then designing, and only then building.
Along the way I got a new idea. People also had to be able to register on my website, for example to make an appointment. And then I started thinking further about what else they could do there, once they are registered anyway. That is how a complete learning space was added. And for that I first took a step back, to the design.
Free with an accountRead -
How to get IT on board when you start building yourself
Anyone building their own tools with AI will clash with IT sooner or later. Why this resistance exists, and why a small, concrete request works much better.
On the second day of a vibe coding training, I first ask everyone to share what they have done in the meantime. One participant had put vibe coding on the agenda of a meeting with the IT team that week. That was not well received, there was serious pushback. Another participant also got nowhere at work. They just built a website about music instead, just to be able to learn.
I actually hear this in every group. And I understand the people in IT too. So I want to explain how I see it, and what I would do.
Feel free to copy the prompt at the bottom of this article, so you immediately have a short request for your IT department.
Free with an accountRead -
Shareable card, the babysitting loop for vibe coding
One card to hang next to your screen or share with your team, plus six sentences to guide your AI in plain language while it builds for you.
In my building training sessions, one sentence comes back so often that participants finish it themselves after an hour. Dumb it down, chunk it down, and babysit your AI. It fits on a card, and you can find that card below. Hang it next to your screen, put it in your team channel, or send it to that colleague who just told their agent to 'solve it yourself'.
The card
You are free to share it, as long as the name stays on it.
Free with an accountRead -
Checklist, building safely with AI before your app goes online
A short checklist for anyone building apps with AI, including the security paragraph for your brief and the prompt to have a second agent attack your app.
Building an app with AI goes so fast today that security easily becomes an afterthought. And later rarely comes. This checklist fits on one screen and walks with you through three moments: when you write your brief, while you build, and right before you go online. You do not need to be a developer to use it. You just have to ask the right things.
The three questions that catch the most
If you only have five minutes, start here. Where are my passwords and keys, and are they going online? What happens if someone pastes malicious text into my input fields? And where is my users' data stored, in Europe or outside of it? Ask your agent those three questions and really read the answer.
Free with an accountRead -
Babysit your AI, even if it can do it itself
You can give an agent a goal and let it go, or watch along step by step. I teach the second in my workshops, and I explain why.
There are two ways to build something with AI. In the beginning, they actually look the same. With the first, you write a good, detailed description of what you want. You give your agent a goal, and then you let it go. With the second, you work step by step. After each step, you look at what it has done. You try to understand it, and then you adjust.
In my workshops, I teach the second. The models can do a lot, and they get better every month. But I have seen what happens when no one watches along anymore.
Below this article you will find the share card with the babysitting loop, which is free for Members.
Free with an accountRead -
Git is just pressing save
Anyone who builds with AI will sooner or later be asked if they can commit. I explain what Git, a repo and GitHub are, without jargon.
After a few hours of building with their AI, almost every group reaches the same moment. The agent then asks if it can commit the changes, and no one understands what it means. And then everyone looks at me. The word sounds like something you need training for.
That is actually not too bad. Anyone who has ever saved a Word document already understands the most important part of Git. Only the jargon holds people back. And that barrier is lower than it seems.
Feel free to copy the prompt at the bottom of this article, and your AI will set up version control for you.
Free with an accountRead -
Model, app, environment: know which layer you are in
ChatGPT, Claude, VS Code, Cursor, Craft Agents: people who are just starting out often lump them all together. I work with three layers, and they help you choose.
At the end of a long workshop day, I asked the group what they were taking away. And one participant said something I have not forgotten since. He had used two programs side by side all day. And only now did he realise they were two different things. Another participant did not see the added value of an agent app, because 'I already have ChatGPT'.
Those are actually questions everyone has. Only not everyone dares to ask them. And they all have the same cause. We talk about AI tools as if they are one thing. But actually there are three, slotted neatly into each other.
Free with an accountRead -
The most important file in your AI project is not code
Anyone building with an AI agent notices they have to explain where everything is over and over again. One simple Markdown file solves that. What belongs in it, and why.
When I open a project in a building training, participants usually look at the code first. I then point to another file. A plain text file, a few screens long, without a single line of code. That is the file that determines whether your agent can work independently or comes to ask you something every five minutes.
At the bottom of this article is a prompt with which your agent helps you draft such a file.
The problem everyone knows
Anyone who works on a project with an AI agent for a while knows it. Every new session starts with an explanation. This is the project, this is how it is put together, the files are there, this is how we want it. If you forget something, the agent goes looking for itself, and makes assumptions that you have to correct later.
Free with an accountRead -
Security belongs in your briefing, not at the end
Building an app with AI is fast. Building a secure app requires you to include security from the start, store your secrets well, and have a second agent attack your work.
Vibe coders who say they built three apps today must be one hundred percent sure that those apps not only work, but are also secure. I say it in every building training, and I always see a few people swallow hard. Working has become the easy part. Being secure does not happen by itself.
Below this article you will find the checklist for building securely with AI, free for members.
Why afterwards does not work
The classic reflex is: build first, and if it works, we look at security. When building with AI, that is extra risky. The agent makes architecture choices at every step based on what it knows. If it does not know that security is important, it chooses the fastest route. And that fastest route is often difficult to change afterwards.
Free with an accountRead -
Vibe coding does not start with the code
Anyone building an app or tool with AI gets stuck by starting to build immediately. Why the discovery phase and a few early choices save you days of work later.
Vibe coding is really just talking to your computer, and it builds it. That is how I explain it to participants who have never heard the term. You describe what you want in plain language, and an AI agent writes the code. A tool, a website, a small app. What used to require a team, one person can do today.
But anyone starting for the first time almost always runs into the same thing. After a promising start, things go wrong somewhere, and the AI seems unable to change direction anymore.
Copy the prompt at the bottom of this article, you use it to brainstorm your idea first before you start building.
Free with an accountRead