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.

Output Format

Close the Design Loop

Send the built UI back into the design tool for review.

Code can flow back to design, not just out of it. Once a screen runs, you can capture the live UI into the design tool as editable frames, so designers review the real thing, annotate it, and explore variants. Closing that loop keeps design and build looking at one artifact instead of two diverging copies.

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.

Capture the UI Back to Figma
You built a working dashboard with Claude Code and it runs on localhost. Before the design review, the team wants it in Figma as editable frames — so they can annotate spacing, try a variant of the header, and react to the real thing, not a flat screenshot pasted into a comment.…
Hand Off With DESIGN.md
A stakeholder loves a particular SaaS landing page and wants 'something like that.' Rather than describe it from memory and lose the details, you want to use Stitch to extract a DESIGN.md from that URL — a portable, plain-language brief of its layout and structure — then hand…

Close the Design Loop

Where you'll practice this

Capture the UI Back to Figma

Hand Off With DESIGN.md

Other principles in Output Format

Describe the Destination

Make the Output Findable

Show Examples in the Skill Body

Specify Output Format