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

Break the Workflow into Steps

Number each step so Claude builds pieces, not monoliths.

For multi-step automations, number each step and describe what it does independently. This lets Claude build and test each piece rather than generating one fragile monolith. When step 3 fails, you can fix step 3: not re-prompt the entire workflow. Numbered steps also make it easy to add, remove, or reorder stages later.

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.

The Multi-Step Workflow
You want to automate your end-of-week reporting with a Node.js script called `weekly-report.js`. The workflow has four steps: (1) fetch this week's data from a Google Sheet using the Sheets API v4 (sheet ID is in the `GOOGLE_SHEET_ID` env var), (2) clean the data by removing…
The First Workflow
Your Node project has `npm run lint` and `npm test` scripts but nothing runs them automatically. You want a GitHub Actions workflow that runs both on every pull request to `main`, so broken code can't merge unnoticed. The repo uses Node 20 and pins dependencies in…

Break the Workflow into Steps

Where you'll practice this

The Multi-Step Workflow

The First Workflow

Other principles in Multi-Step

Architect Before You Ask

Ask for a Plan First

Combine Context with Action

Coordinate Across Files

Delegate to a Subagent

Describe Environments and Stages