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.

Anti-Patterns

Verify the Translation

Don't trust pixel-perfect; diff against tokens and the screenshot.

Design-to-code is not a perfect roundtrip. Treat the output as a strong draft and check it: diff the rendered result against the screenshot, confirm it used the tokens you named, and look for the states and spacing the frame implied. Trusting 'pixel-perfect' without looking is how subtle drift ships.

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.

Screenshot as Ground Truth
Claude generated a component from a frame and it looks roughly right. But you've been burned before: last time the padding came out halved and a muted label was the wrong gray, and it shipped because nobody checked. You don't want to eyeball it again — you want Claude to verify…
Don't Trust Pixel-Perfect
A teammate is about to merge an AI-generated implementation of a marketing section, calling it 'pixel-perfect, ship it.' You've watched this go sideways: small token drift, a missing focus state, spacing that's close-but-not-right. Before sign-off you want a concrete…

Verify the Translation

Where you'll practice this

Screenshot as Ground Truth

Don't Trust Pixel-Perfect

Other principles in Anti-Patterns

Ask What's Missing

Question the Obvious

Simplify Before You Prompt