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

Delegate to a Subagent

Spawn a subagent for research-heavy subtasks; brief it on scope, limits, and report shape.

When a task has a heavy research or exploration phase, hand it to a subagent instead of doing it in the main thread. The subagent runs its searches, files its findings, and returns a concise report — your main context stays clean for the decisions only you can make. Say what you want the subagent to do, what it shouldn't do, and how to report back.

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.

Delegate to a Subagent
You're about to plan a migration off an old `legacyAuth` middleware, but first you need to know every place it's used across the codebase. Doing the search in the main thread would fill your context with ripgrep output you don't actually need. This is a textbook job for a…
Chain Diagnose, Then Fix
Sentry just paged the team: a small but steady stream of 500s on `POST /api/orgs/:slug/invitations` since the 09:14 deploy. The deploy bumped the `clerk` SDK from 4.x to 5.x. You don't yet know whether the bug is in the SDK upgrade, in your wrapper around it, or in a downstream…

Delegate to a Subagent

Where you'll practice this

Delegate to a Subagent

Chain Diagnose, Then Fix

Other principles in Multi-Step

Architect Before You Ask

Ask for a Plan First

Break the Workflow into Steps

Combine Context with Action

Coordinate Across Files

Describe Environments and Stages