Promptles is a scenario-based game for GTM engineers, PMs, designers, and enthusiasts shipping with AI agents — anyone who prompts Claude Code, Cursor, Replit Agents, or similar tools without a traditional software engineering background. You're handed real engineering tickets — debugging stack traces, refactoring across files, designing auth flows — and write the prompt you'd actually send. Each prompt is graded by Claude on the criteria a senior engineer would care about, and the expert prompt sits next to yours so you can read the gap.

Does Promptles use Claude?

Yes. Every prompt you write is graded by Claude Haiku 4.5, against a mix of deterministic pattern checks and AI-evaluated criteria. The Anthropic API is called server-side; players never need their own API key.

Do I need an Anthropic API key?

No. Promptles handles all AI calls server-side. Sign in once with your email and start playing — there's no key to paste, no provider to configure.

Is there a free tier?

Yes. The free tier includes the foundational scenarios, today's daily challenge, and pattern-based grading. Paid tiers (Solo, Lifetime, Team) add full AI grading, every scenario, and the daily archive.

How is Promptles different from other prompt engineering tutorials?

Most prompting tutorials teach you to write a single perfect prompt. Promptles grades multi-turn conversations: you write a prompt, see what Claude actually replies, then write the follow-up that fixes what's still wrong. The whole chain is graded, because that's what real software engineering work looks like.

Is Promptles useful for GTM engineers?

Yes — GTM engineers are a core audience. Building sales, marketing, and RevOps automation, internal tools, integrations, and AI agents means writing a lot of prompts to Claude Code, Cursor, Replit Agents, and similar tools. Promptles teaches the prompting rigor that gets reliable output the first time, so the integrations and agents you ship don't break the next morning. The vocabulary deck includes a dedicated GTM & Business Tools section covering the SaaS platforms, data models, and business concepts you'll be automating.

Can my team use Promptles?

Yes. The Team plan adds per-seat AI quotas and lets admins author custom scenarios for the team's codebase using AI assistance. Each member keeps their own progress and playbook; team-authored content shows up alongside the core library.

Errors

Include the Error Message

Always paste the exact error message when reporting a bug. The error text contains critical clues: the error type, the operation that failed, and often the exact location. 'It crashes' tells Claude nothing; the stack trace tells it everything.

Where you'll practice this

3 Promptles scenarios teach this principle directly. Each one drops you into a real engineering ticket and asks you to write the prompt you'd send to Claude Code.

The Stack Trace
Your React app is crashing intermittently in production. The error log shows `TypeError: Cannot read properties of undefined (reading 'map')` in `components/UserList.tsx` at line 12. After investigating, you realize the `users` prop is sometimes `undefined` when the component…
Feed Diagnose the Repro
A teammate just reported that the dashboard's CSV export is producing files with mangled UTF-8 characters — names like 'José' show up as 'JosÃ©' when the file is opened in Excel. The bug ticket has a one-line description and nothing else. You want to run the team's `/diagnose`…
The Red Build
Your CI just went red on a pull request. The `test` job failed during `npm ci` with an error about the lockfile being out of sync with `package.json`. You added a dependency locally but only committed `package.json`, not the updated `package-lock.json`. You want Claude Code to…

Include the Error Message

Where you'll practice this

The Stack Trace

Feed Diagnose the Repro

The Red Build

Other principles in Errors

Describe How to Reproduce

Describe the Sequence

Describe What You See

Diagnose Before You Prescribe

Quantify the Problem

Read the Error First