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.

Context

Point It at the Project Rules

Name the CLAUDE.md or AGENTS.md file explicitly; ask the assistant to cite the rule it's applying.

Most projects carry a CLAUDE.md or AGENTS.md at the root that captures conventions the assistant can't infer from code alone: export style, naming, commit format, non-negotiables. Tell the assistant to read it before editing, and ask it to cite the relevant line so you know the rule actually landed in its context.

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.

Point Claude at the Rules
Your project has a `CLAUDE.md` at the root that sets two non-negotiable conventions: named exports only (no default exports) and every file under `src/lib/` must have a matching test next to it. You want to add a `formatCurrency` helper to `src/lib/money.ts`, and you want the…
Re-Anchor After Compaction
You're four hours into a session. The agent just compacted the conversation context (auto-summarized older turns to fit the window). You can tell because in its last response it confidently referred to a constraint you both agreed on three hours ago — except it got the…

Point It at the Project Rules

Where you'll practice this

Point Claude at the Rules

Re-Anchor After Compaction

Other principles in Context

Declare the Tools You Need

Describe Before You Prescribe

Describe the Data Shape

Explain the Integration Point

Keep Memory Reusable

Map to Real Components