Things to ask

You do not need to know the tools. Say what you want, in your own words and in any language. These show what works, and what happens behind each request.

Add a game

Add my game at https://example.com to Alldle, in the Words category.

The assistant finds the category, creates a draft and gives you a meta tag or DNS record to add. Nothing is public yet. If your site is reachable, it can read the page to draft the description and rules.

Then, once the tag is on your site:

The tag is deployed. Verify the domain and submit it.

This sends the game to review, and you get an email.

With your code open

In Claude Code, Cursor or VS Code, one request can cover it all. “Add this project to Alldle, put the verification tag in our HTML, and tell me when it is deployed so you can submit.” Check the draft first: reviewers read what it writes.

Use a real screenshot as the thumbnail

The assistant can set a thumbnail from an image at a public address.

Use https://example.com/screenshot.png as the thumbnail for my game.

For a file on your computer, upload it on the game’s Edit page instead. See the thumbnail for what works well.

Take over a listing

My game at https://example.com is already on Alldle. Help me claim it.

It returns the verification steps. Add the tag or record, then ask it to claim the game. See Claim a listed game.

Fix a rejected game

Why was my game rejected? Fix it and send it back.

It reads the reviewer’s note, proposes the change, applies it, and resubmits. Attempts are limited, so you may want to ask it to show you the change first.

Edit a listing

Rewrite my game's description to mention the new hard mode, and show me before you save it.

On a live game, the change waits for review while the old text stays up. The result says what is queued.

Read your audience

How did my games do this week compared with last week?

Which countries play my game most, and where do they come from?

Is anyone playing right now?

Do players come back? Show me next-day retention and the last few cohorts.

Read your results

These need the SDK.

How hard was this week's puzzle compared with the others?

Which of my modes do players finish least often?

Is the SDK working on my game? Did it report anything this week?

Put it together

Give me a short report on my game for the last 30 days: visitors, plays, top three
sources, next-day retention, the hardest puzzles, and one thing you would change.

Look at my listing like a player who has never heard of the game. What would make
you not press Play? Suggest a better description, but do not save it yet.

Writing good requests

• Name the game if you have several, and the period if it matters. The default period is 30 days.
• Ask to see changes first for anything that will be reviewed, because review attempts are limited.
• Ask for the thing, not the tool. The assistant picks the tools, and each one tells it what to do next.
• Check figures that surprise you. The assistant reads real numbers, then writes about them. Compare with your dashboard before acting on a big claim.