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

Keep Memory Reusable

Save patterns and preferences that survive across sessions; never save snapshots of finished work.

Memory should hold patterns and preferences that pay off in future sessions: how the user likes feedback framed, what style of code review they want, recurring constraints. It should not hold snapshots of finished work — the bug you fixed last Tuesday, the PR title you used last month. Stale snapshots actively mislead future sessions when the project moves on. Ask: 'Will this entry help me a month from now?' If not, don't save it.

Where you'll practice this

One Promptles scenario teaches this principle directly.

Memory Hygiene
You just finished a two-week feature flag rollout — the `new_dashboard` flag is now at 100% and the cleanup PR is merged. In the post-mortem, your teammate suggested you 'tell Claude to remember everything we learned' so it can help next time. You're tempted to dump a…

Other principles in Context

Declare the Tools You Need
Name the tool or MCP server by name, and say what to do if it isn't reachable.
Describe Before You Prescribe
Describe the Data Shape
Claude can't clean data it can't picture.
Explain the Integration Point
Map to Real Components
Use Code Connect so it reuses your components, not new markup.
Name the Framework

Where you'll practice this

Memory Hygiene

Other principles in Context

Declare the Tools You Need

Describe Before You Prescribe

Describe the Data Shape

Explain the Integration Point

Map to Real Components

Name the Framework