Hi @ucan
I understand perfectly what you are saying. I feel your frustration because using LLMs and Prompts can be sometimes very hard and results vary a lot. It is definitely not magic.
To give you more context, almost all the use cases you see in our videos were made using Opus 4.5 model and the Cursor agent. This is very important because the model, the agent, and the prompt change everything.
I have attached here the exact Penpot file we used in the demos so you can test with the same source.
Also, after fighting a lot with agents, here is a brief summary of “Good Prompting” that works for us. If the input is weak, the output will be bad:
-
Define the Role: Don’t just say “You are a designer.” Be specific. “You are a Senior Product Designer expert in Accessibility and Design Systems.”
-
Structure the Prompt: Think of it like a User Story ticket. Give Context, Objective, Restrictions (e.g., “only use existing components”), and Quality Criteria.
-
Images are key: The AI “sees” but needs guidance. Tell it exactly where to look in the screenshot (e.g., “focus on the negative space in the header”).
-
Give specific Rules: Don’t expect it to read the full documentation. Give explicit rules: “Use only colors from /core/colors” or “Do not invent new font sizes.”
-
Iterate: Do not expect a perfect result in “one-shot.” It is a conversation: Analysis → Proposal → Feedback → Adjustments.
I hope this helps you get better results. It is a trial and error process!
