A bookshop-management game needs more than shelves and a cash counter. The player should decide which books to stock, see which fictional customers are looking for them, and weigh a sale against the cost and space needed to restock. A staged prompt sequence helps build that loop without asking for an entire neighborhood simulation at once.
The prompts in this article are draft templates and were not run against a game builder for this package. No playable build or real retail result is claimed. The shop, titles, customer profiles, prices, and sales figures are fictional game-design examples.

Write the shop-day brief
Define the player's role and one shop-day cycle first. For this fictional example, the player curates a small independent bookshop: select stock, place books on limited shelves, open the store, serve visitors, review sales and unsold inventory, then decide what to reorder. The first objective is to complete three days without running out of cash.
Write the rules that need to stay consistent: how many books fit on a shelf, whether visitors can buy one or several titles, when a purchase happens, how restocking works, and when rent is charged. Keep customer preferences as small game profiles. They can represent invented tastes such as Mystery, Fantasy, or Nature; they are not evidence about real readers.
| Brief part | Fictional starting rule | What it clarifies |
|---|---|---|
| Shop size | One room with six book slots | Stock has a visible limit |
| Catalog | Mystery, Fantasy, Nature | Each book belongs to a simple category |
| Visitor demand | Six fictional shoppers, one preferred category each | Stock choice can match or miss demand |
| Sales and costs | 3 coins per sale; 1 coin per replacement; 4 rent/day | Revenue and operating costs remain distinct |
| Objective | Finish three shop days | The prototype has a short testable horizon |
Stage prompts from stock to sales
Ask for the room and shop-day transition before customer variety. Add the catalog and shelf slots next, then one demand rule and a ledger. Only after those states are consistent should you request more genres, special events, or staff. The prompts below are a starting sequence to adapt, not verified executions.

Prompt 1: create the small shop loop
Create a fictional bookshop-management prototype with one room, one six-slot shelf, and a three-day objective. Each day the player selects stock, opens the shop, serves visitors, reviews sold and unsold books, pays 4 coins of rent, then chooses what to reorder. Show the cash balance and shelf capacity before each day. Do not add employee systems, online orders, or multiple stores.
Prompt 2: add a small curated catalog
Extend the same shop with three fictional book categories: Mystery, Fantasy, and Nature. Stock units occupy one shelf slot each. Start with 3 Mystery, 2 Fantasy, and 1 Nature book. A book sells for 3 coins; restocking one costs 1 coin. Show the quantity of each category on the shelf and never let inventory exceed six slots. Preserve the existing day order and three-day objective.
Prompt 3: connect fictional customer preferences
Add six fictional visitors per day, each with a visible preference for one of the three book categories. Each visitor buys one matching book if stock is available; otherwise they leave without a purchase. These preferences are invented game data, not real reader research. At day end, report visitor count, units sold by category, unsold stock, revenue, restock cost, rent, and net cash change. Keep all previous prices and capacity rules.
Prompt 4: improve the purchasing decision
Polish the shop screen without changing the rules. Before opening, show current stock, six-slot capacity, last day's category sales, and available cash. At day end, distinguish sales revenue, restock spending, rent, and remaining inventory. Do not add discounts or new categories until these values remain consistent across all three days.
Each stage adds a dependency: the shop needs a day loop before it can report sales; the catalog needs slots before it can sell; demand needs stock before a preference matters. If a prompt changes an earlier rule, record that as a revision and recheck the earlier stage rather than hiding the change.
Check a fictional day-end ledger
Use a small paper calculation to check whether the prompt sequence is internally consistent. Begin with three Mystery books, two Fantasy books, and one Nature book. Six fictional visitors arrive and each buys one book matching a category that is in stock. All six sell for three coins, creating 18 coins in revenue. Replacing the six books costs six coins, and rent costs four, so the day changes cash by +8 before other expenses.
| Ledger item | Amount | Calculation |
|---|---|---|
| Sales revenue | +18 coins | 6 books × 3 coins |
| Restock cost | −6 coins | 6 books × 1 coin |
| Rent | −4 coins | Fixed daily cost |
| Net change | +8 coins | 18 − 6 − 4 |
| Ending shelf stock | 6 units after restock | Restock replaces the books sold |
This is fictional game math, not a sales forecast for a real bookshop. A playable prototype should show whether the restock happens before or after the next day's visitors, and whether the player has enough cash to replace the stock. Keep the ledger explicit so a book is not counted as both sold and still on the shelf.
Record prompt runs and corrections
When you run these prompts later, save the exact text, date, tool or model, output version, and what changed after inspection. Note whether the result was a sketch, a mockup, or a playable build. A prompt template alone does not prove that a system worked.
SEELE's official AI Game Maker page describes starting from a text prompt, testing a browser-playable result, and refining it. That is general product context. The prompt templates here have not been run and do not claim a specific result.
- Stock check: total shelf inventory never exceeds six units.
- Preference check: a visitor buys only a matching category when stock exists.
- Cash check: revenue, restock cost, and rent appear once in the ledger.
- Unsold check: any category missed by demand remains on the shelf or follows a clearly stated markdown rule.
- Evidence check: record actual output and corrections before describing a prompt as tested.

After the first loop works, add one reason to diversify stock, such as a limited event or a returning customer preference. Keep the same ledger and shelf limit while you test the new choice. This makes each new prompt easier to compare against the original shop brief.
Bookshop management prompt FAQs
Should I start with a full bookstore catalog?
No. Begin with a few fictional categories and a small shelf limit. Add more titles only after stock, demand, and the day-end ledger agree.
How do customer preferences affect the game?
Use invented profiles to create a stock decision. Show what each visitor wants and what happens when the matching category is unavailable; do not present sample profiles as real reader research.
How can I stop inventory from exceeding shelf space?
Give each book a slot cost and validate the total before opening the shop. If a restock would exceed capacity, show which units remain in storage or ask the player to choose what to display.
What should a daily ledger include?
Show units sold, remaining stock, sales revenue, restock spending, rent, and net cash change. Keep each event separate so the same book or cost is not counted twice.
Can I call these prompts tested?
Only after running them and inspecting the output. These examples are unrun drafts, and no playable build is claimed for them.
Make your own bookshop management game
Start with one room, a small curated catalog, and a ledger that connects customer choices to stock and cash. Then add the next demand pattern the player can respond to. For a general game-creation starting point, explore the SEELE AI Game Maker and adapt these draft prompts to your own prototype brief.


