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

Scope Your Request

Tell Claude exactly which files to touch and which to leave alone. Without clear scope, Claude might search your whole codebase for matches. Or worse, miss some occurrences because it only checked one file.

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 Spelling Fix
Your code has a misspelled variable name `recieve` that should be `receive`. It appears in `api/handler.js`: used as a function parameter, a local variable, and in a comment. There are about 5 occurrences total in this one file.
Zoom Out First
You've been asked to improve the slow checkout-page load times in a codebase you've never worked in before. There are seven services in the repo, the README is two years out of date, and the 'checkout' word appears in 340 files. The temptation is to dive straight in — open the…
Pull and Summarize
Your team's GitHub MCP server is connected and exposes `github__list_issues` (with `repo`, `state`, `labels`, `since`, `per_page`, `page` args). You want a quick read on the issue queue for the `acme-corp/checkout` repo: open issues touched in the last 14 days, labeled `bug` or…

Scope Your Request

Where you'll practice this

The Spelling Fix

Zoom Out First

Pull and Summarize

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