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

Invoke the Right Skill

Match your task to an existing skill or slash command and call it by name.

Skills and slash commands are pre-written instructions the assistant already knows how to run: /commit, /review-pr, a custom /release. When your request matches one of them, invoke it by name instead of describing it from scratch. You get the team's validated workflow instead of a one-off guess.

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.

Invoke the Right Skill
You've just finished a small feature: a new `Button` component and its test. Your team has a `/commit` slash command that reads recent commit messages, drafts one in the same style, and stages the right files. Instead of describing commit conventions by hand every time, you want…
Call It By Name
Your team has a `/review-pr` skill installed across the engineering org — it walks the agent through reading the diff, checking for missing tests, flagging risky migrations, and posting a summary comment on the GitHub PR. You're about to ask Claude to look at PR #4821 (a…

Invoke the Right Skill

Where you'll practice this

Invoke the Right Skill

Call It By Name

Other principles in Clarity

Be Specific

Describe Expected Behavior

Describe the Visual Target

Describe What, Not How

Master the Art

Name the Services