Yesterday, someone posted in r/PromptEngineering and it caught my eye. A dev named Kiro shipped Iro, a Duolingo-style app for learning prompt engineering and practical AI workflows.
Sounds like another “learn AI in 10 minutes” product at first glance. Here’s the twist.
The Problem It’s Actually Solving
You’ve done this. You save a prompt, it works once, then context shifts by one sentence and it breaks. You have no idea why. So you save another prompt. Now you have 500 of them and still can’t write a new one from scratch.
Iro isn’t a fancy prompt library. It has a Prompt Lab where you write your own prompts and get coached on the reasoning, not just handed a template to copy. Why does this structure work? What breaks it? What would you change?
That’s the actual product. The Duolingo-style lessons are just the entry point.
How It Works
- 🎯 Pick a path. Prompt Engineering is the main one, but it covers ChatGPT, Claude, agents, automation, and real-world use cases
- 📱 Short daily lessons with the same habit loop as Duolingo
- ✍️ Use the Prompt Lab to write prompts and get feedback on why they work or fall apart
- 🔁 Apply it to actual use cases: marketing, finance, job hunting, image and video generation, vibe coding
Pro Tip
Already comfortable with prompting? Skip the structured path. Go straight to the Prompt Lab and start writing. That’s where the learning actually happens, when you put your reasoning on paper and get pushed back on it.
🔗 Try it at tryiro.com
There’s a real difference between collecting prompts and understanding them. Worth checking out if you want to get better at the second thing.
Frequently Asked Questions
Q: How is learning to prompt on Iro different from just saving a bunch of prompts online?
This is the core thing. The app teaches you WHY prompts work instead of just hoarding templates. Most people save 500 prompts and still freeze when something breaks. Iro flips that, you’ll learn to debug when things fail, figure out what went wrong (missing context? vague instructions? bad info retrieval?), and actually adapt prompts to your needs.
Q: What’s prompt debugging anyway?
It’s just diagnosis, honestly. When a prompt doesn’t work, you learn to pinpoint what went wrong: Was the context missing? Instructions too vague? Did the model drift off topic? Does it have actual limitations it’s hitting? Once you can identify the real problem, the fix becomes obvious.
Q: Do I need to learn workflows if I’m just starting with prompts?
Start with prompts, move to workflows later. Early on, nail individual prompts and how to debug them. Once you get good, you’ll want to string multiple AI steps together, manage state between them, and stop treating AI as this isolated magic box. That’s where the real power comes in.
Q: What usually breaks a prompt?
Usually one of five things: missing context, fuzzy instructions, bad info retrieval (if you’re pulling documents), the model drifting off topic, or the model hitting its actual limits. Learning to spot which one is the real problem beats memorizing “the perfect prompt”, because it doesn’t exist.
I built a Duolingo-style app for learning prompt engineering and practical AI workflows
by u/Kiro_ai in PromptEngineering