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

Pass Context Between Tools

Hand one tool's output deliberately to the next.

Real work spans tools: an email becomes a calendar hold, a document becomes a digest, a thread becomes a ticket. Don't assume the agent will carry the right details across the gap. Name what travels from one step to the next, the date and attendees from the email, the decision from the doc, the summary into the channel, so each tool gets exactly the input it needs. The hand-off is where multi-tool workflows quietly break.

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.

Email Into a Calendar Hold
A prospect emailed: 'Could we find 30 minutes next week to walk through the rollout? Mornings are best for me.' You want Claude to take it from there, read the email, pull out what matters, check your availability, and come back with a proposed hold plus a draft reply offering…
Turn Support Email Into Issues
Five bug reports landed in support@ overnight. You want Claude to turn each one into a proper Linear issue and then reply to the customer with a link to track it. The catch is the hand-off: each email's real detail, the symptom, the steps to reproduce, the customer, the…

Pass Context Between Tools

Where you'll practice this

Email Into a Calendar Hold

Turn Support Email Into Issues

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

Delegate to a Subagent