Examples#

Each example is one request you can paste as is (change the names). The assistant does the set-up work right away and asks for your yes before anything goes public or reaches your players.

Put a new game on Gamearly#

"Create a page for my game from its Steam page https://store.steampowered.com/app/123456. Then tell me what's still missing, fix what you can, and submit it for review when it's ready."

Gamearly imports the page from Steam: texts, genres, modes, status, platforms, system requirements, cover, logo, trailers and screenshots.
The assistant gives you the link to the new project and tells you what, if anything, is still missing. It asks you only for that, often nothing.
It submits the project for review once you confirm.

Plan a launch week#

"Our demo launches on the 20th. Plan the week around it: quests, a vote, a dev diary on launch day and a fan art contest. Check the calendar first so nothing overlaps."

It reads the content calendar and finds the free days.
It proposes a schedule with the quests, the vote, the article and the contest.
You approve, change or drop each item; it creates and schedules what you keep.

Let the quest manager run quests#

"Set up the quest manager for Starfall. Ask me the questions you need, then plan a month of quests. I want to review every quest with a reward before it goes live."

It writes the game brief and asks you its open questions.
It generates the plan and shows it to you, week by week.
It approves the quests you agree with and keeps the rewarded ones for your review.

Ship a build to beta testers#

"Check builds/Starfall-0.5-win.zip, upload it as 0.5 for Windows, publish it on the beta channel and give access to my 'Top testers' list."

It checks the zip: there must be a real game executable inside.
It uploads the build from your computer and waits until it's ready.
It shows the launch executable it picked; you confirm or change it.
It publishes on beta ⚠ and grants access to the list ⚠ after your yes.

This needs an assistant that can run commands (Claude Code, Cursor, VS Code). A chat-only assistant gives you the commands to run instead.

Run a playtest#

"Run a 2-week closed playtest of 0.5 with an NDA and a short survey about the combat. Accept players with more than 5 hours played. When it ends, summarise the feedback."

It creates the playtest with the NDA, the questionnaire and the dates, then opens it ⚠.
It approves the matching registrations.
At the end, it reads the stats and the AI summary, and lists the main issues with quotes.

Weekly review#

"Give me the weekly review of Starfall: audience, engagement, quests, sales and what players said. Compare with last week and suggest 3 actions."

It reads the dashboard sections for the last 7 days and the 7 before.
It reads the best and worst quests, the forum and the comments.
It writes the review, with where each number comes from, and proposes 3 actions you can start right away.

Win back players who stopped#

"Find players with more than 10 hours who haven't played in 3 weeks. Tell me how many they are and what they have in common, then send them a message about update 0.5 with a comeback quest."

It turns your words into a segment and counts the players.
It compares them with active players.
It creates the comeback quest.
It shows the message and who will get it, then sends it after your yes ⚠.

Make in-game events readable#

"List our raw in-game events, give each a readable name and category, build a funnel from tutorial to the first boss, and pin it on the events overview."

It reads the event catalogue and proposes labels.
It saves the labels, the funnel and the pinned chart.
It tells you where players drop most.

Keep the community clean#

"Go through the comments and forum threads of the last 3 days. Remove spam and insults, pin the best bug report, and draft replies to unanswered questions for me to approve."

It reads the latest threads and comments.
It proposes what to remove and what to pin, and drafts the replies.
It applies only what you approve.