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

Respect the Calendar

Give the agent your timezone, hours, and constraints before it schedules.

A calendar is only readable if the agent knows the rules around it. Give it your timezone, your working hours, how much buffer you want between meetings, and which existing events are immovable. Without those, free/busy data is just blocks on a grid, and the agent will happily book over lunch or at 6am. State the constraints up front and 'find a time' becomes 'find a time that actually works.'

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.

Read My Real Availability
Your Google Calendar MCP server is connected. You asked 'when am I free this week for a 45-minute call?' and got back slots at 7am, smack in the middle of lunch, and during the all-day team offsite on Tuesday. Claude read your free/busy correctly, it just didn't know the rules…
Schedule Around the Conflicts
Now you're writing to the calendar, not just reading it. You want a 30-minute 1:1 with Priya next week. Last time, Claude created the event at a time that landed right on top of her team standup, because it booked against your calendar alone and never checked hers. You want it…

Respect the Calendar

Where you'll practice this

Read My Real Availability

Schedule Around the Conflicts

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