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.

Constraints

Gate Destructive Actions

Require an explicit OK before delete, archive, decline, or send.

Deleting, archiving, declining, and closing are one-way doors. Before the agent does any of them, make it show you exactly what it intends to change, which messages, which events, which issues, and wait for an explicit yes. A confirmation step costs you one line and saves you from an agent that helpfully archived three weeks of unread email. Reversible actions can move fast; irreversible ones need a human in the loop.

Where you'll practice this

2 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.

Confirm Before You Archive
You asked Claude to 'clean up my inbox, archive anything I don't need.' It archived forty messages, two of which you very much needed, and now you're digging through the archive to find them. Archiving isn't a preview, it pulls mail out of your inbox in one move. What you wanted…
Update the Issue Safely
Your Linear MCP server can write, not just read. You want to tidy the backlog: every issue stuck in 'In Review' for more than fourteen days should move to 'Stale' with a comment pinging the assignee. A bulk write like this is hard to walk back, and last time a similar cleanup…

Gate Destructive Actions

Where you'll practice this

Confirm Before You Archive

Update the Issue Safely

Other principles in Constraints

Bound the Skill's Scope

Define Component Boundaries

Define Inputs and Outputs

Define the Business Logic

Describe Edge Cases

Describe the Happy and Sad Paths