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.

Multi-Step

Combine Context with Action

The best prompts tell Claude what exists (context) and what you want changed (action) in the same breath. Context without action is a description; action without context is a guess.

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.

Refactor with Context
You have a `utils/formatters.ts` file with three formatting functions that all share repeated logic for locale handling. You want to refactor them to use a shared helper, but you also need Claude to understand the existing behavior so nothing breaks.
MCP + Local Edit
Your project has TypeScript types in `src/db/types.ts` that mirror the Postgres `users` table. The team has been hand-editing them, and they've drifted: the `users` table has a `last_login_at` column that the TS type is missing, and a column was renamed from `display_name` to…
Triage, Then Propose a Batch
It's Monday and you have sixty unread messages. A plain 'summarize my inbox' gives you a wall of text you still have to act on one by one. What you actually want is the reading AND a recommendation: each message sorted into a clear next step, grouped so you can approve a whole…

Combine Context with Action

Where you'll practice this

Refactor with Context

MCP + Local Edit

Triage, Then Propose a Batch

Other principles in Multi-Step

Architect Before You Ask

Ask for a Plan First

Break the Workflow into Steps

Coordinate Across Files

Delegate to a Subagent

Describe Environments and Stages