Straight answers.

No. The whole first chapter assumes zero code, and the on-ramp into the rest is deliberately gentle. By the time you see your first command line, you have already shipped a working tool. Code shows up when it actively helps you, not before.

No. Prompt engineering is a single move. PromptDojo teaches the whole loop: name a problem, shape a tool, test for failure, ship something that survives. Prompts are the brushwork; we teach the whole painting.

That is exactly who we built this for. The lessons assume nothing: not technical jargon, not a CS background, not even comfort with computers beyond using one for work. You will feel deliberately oriented.

Probably yes for the first chapter; possibly no for the rest. If you can already ship working tools, you are not the target audience. If you have never shipped one but you do code, the workflow chapter and build chapter may still be useful.

Small, useful tools you can run on your own work. The first one most builders ship reads meeting notes and drafts the follow-up messages. Others include calendar triagers, lead trackers, job-match agents, and notes-to-action automators. They are tiny, opinionated, and shaped to your job.

Yes. Everything you build runs in your browser and the work is yours: copy your tools and prompts out whenever you want, and they keep working even if you cancel. A saved library with one-click export is planned. The dojo is a place to learn the loop; what comes out is a real thing you can use on Monday.

Not as the promise. We focus on personal-scale tools you actually use. If you later want to take a tool and turn it into something bigger, you will have the muscle to do it. We do not pretend to be a startup school.

Chapter 00 runs about 75 minutes across 10 short lessons and is free to work through. Later chapters are paced for one sitting at a time, usually 30 to 60 minutes, with natural break points. You can pause anywhere and your place is saved.

No. The dojo is text-and-build, not lecture-and-watch. We use cinematic visuals for atmosphere, but the lessons themselves are interactive: you write, you decide, you ship. Reading something is one move; reading and immediately doing it is the move.

One every chapter, but they test understanding, not trivia. Five questions, no traps, no Python esoterica. They exist to make sure the muscle stuck before you move on.

The free path is $0. Plus is $5 a month or $49 a year, and opens the full dojo. See the full pricing breakdown.

Refunds follow the billing channel. Web purchase questions go through support; Apple and Google refund rules apply only to native app-store purchases.

Yes. Cancel through the billing channel you used. The work you built is yours: copy it out of the dojo before or after you cancel, and it keeps working.

The free path runs in the browser. Later Plus lessons may ask you to connect local tools or APIs when the project needs them, and the lesson will say that before you start.

No. The core lessons run in your browser and do not need an AI account. Lessons about model APIs use safe simulations, so you learn the real workflow without spending money. When a lesson invites you to point your own AI tool at the work, it says so up front, and that part is optional.

The dojo is model-agnostic by design. Model and API lessons run on safe simulations rather than one vendor's live endpoint, and when you bring your own AI tool, you pick the model. We teach decisions that survive any model swap, not tricks tied to one vendor.

It might replace the typing. It will not replace the deciding. The skill we teach is taste, framing, and ownership, which is what is left when the typing stops being valuable.

No. Your data is yours. See our trust philosophy for the details.