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

Make the Skill Stepwise

Split the skill into ordered phases; finish one before starting the next.

Multi-phase work — diagnose, then fix, then add a regression test — fails when the skill tries to do all of it in one pass. Break the body into ordered phases and tell the skill to complete one before moving on, ideally pausing for confirmation between risky steps. The agent gets a chance to verify each step, the user gets natural checkpoints, and a failure midway leaves the work in a recoverable state instead of a half-applied tangle.

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 Diagnose Skill
Your team has been bitten by 'just-fix-it' patches that solve symptoms without understanding root causes. You want a `diagnose` skill the agent runs when the user reports a bug. The skill should walk through five ordered phases — reproduce the failure, minimize the input, form a…
The TDD Skill
You're authoring a `tdd` skill that walks the agent through one red-green-refactor cycle at a time. The current draft tries to do every cycle in a single response: it lists the feature, writes all the tests, makes them pass, refactors, and reports — and the result is…

Make the Skill Stepwise

Where you'll practice this

The Diagnose Skill

The TDD Skill

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