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.

Clarity

Pin the MCP Tool

Name the MCP tool by id and list its arguments — don't say 'check the system'.

MCP servers expose tools by id — `linear__list_issues`, `github__get_pull_request`, `postgres__query`. The tool id is what the agent matches on; vague phrasing like 'check Linear' or 'look it up in GitHub' invites guesswork: the agent calls the wrong tool, falls back to a web fetch, or invents data altogether. Name the exact tool you want, list the arguments you want passed, and the call becomes deterministic.

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.

Pin the Tool
Your team has a Linear MCP server connected to the workspace. It exposes three tools: `linear__list_issues` (filter by team, project, priority, state), `linear__get_issue` (fetch one by id), and `linear__update_issue` (set state, assignee, labels). You want to know how many P0…
Name the Tool and the Filters
A Linear MCP server is connected to your workspace. It exposes three tools: `linear_list_issues` (filter by team, project, priority, state, cycle), `linear_get_issue` (fetch one by id), and `linear_update_issue` (change state, assignee, labels). You want one number: how many…

Pin the MCP Tool

Where you'll practice this

Pin the Tool

Name the Tool and the Filters

Other principles in Clarity

Be Specific

Describe Expected Behavior

Describe the Visual Target

Describe What, Not How

Invoke the Right Skill

Master the Art