Define the Glasshouse Days loop
A greenhouse simulation prompt should specify when weather, player actions and growth updates happen. If watering and growth are described without an order, two implementations can produce different harvest dates. Glasshouse Days uses two identical beds and a fixed forecast so the daily state can be traced.
Each bed begins with one planted seed, moisture 1 on a 0–3 scale, and growth 0 of 3. Temperature is shown at the start of each day and follows a fixed sequence: 2, 2, 3, 4, then 2 for the remaining days. There is no random weather in this first example.
The player gets one action per day: water one bed, adding one moisture up to the cap, or harvest a mature crop. After that action, each crop checks its conditions. At temperature 1–3 and moisture at least 2, it gains one growth and uses one moisture. A temperature of 4 pauses growth without consuming moisture. A crop matures at 3 growth.

Make the daily growth tick explicit
The result order is: show today's temperature, choose a player action, apply the action, check each bed's growth condition, advance the day. Watering cannot exceed 3. Harvest is legal only when growth is 3; harvesting clears that bed. Watering and harvesting cannot both happen on the same day.
The win goal is to harvest both crops by the end of day 10. The player may harvest either mature crop; the other keeps growing while the player tends it. There is no money, fertilizer, pest or selling system. Restart restores both seeds, moisture, growth, day counter and the forecast sequence.
By naming the tick order and thresholds, the prompt turns a cozy theme into a state model that can be checked. Additional crop types can wait until the first crop reliably moves from seed to harvest.

Trace the example
Day 1 temperature is 2. Water Bed A from moisture 1 to 2; it passes the growth check, reaches 1/3 and returns to moisture 1. Bed B remains at 0/3 and moisture 1. Day 2, water Bed A again; it reaches 2/3 and returns to 1. Day 3 temperature is 3, so another water action lets A reach 3/3 and mature.
Day 4 temperature is 4. The player harvests A; temperature pauses Bed B's growth and preserves its moisture. On day 5, water B; it reaches 1/3. Water B on days 6 and 7 to reach 3/3. Harvest B on day 8. Both crops are harvested before the day-10 deadline.
This hand-calculated schedule is a fictional rules example, not a real simulation test. It assumes the action and growth order stated above. A future build must be inspected to confirm the displayed day, temperature, moisture and growth values actually update as specified.

Write the six prompts
Use one prompt per design decision so later checks have a clear source of truth. These drafts describe Glasshouse Days; they have not been run and do not represent a generated playable game.
Prompt 1: create beds and forecast
Create two greenhouse beds, each with one seed, moisture 1/3 and growth 0/3. Show the current day and today's temperature. Use the fixed forecast 2,2,3,4,2,2,2,2,2,2.Prompt 2: limit daily actions
Give the player exactly one action per day: water one bed for +1 moisture up to 3, or harvest one mature crop. Do not allow both actions on the same day.Prompt 3: define growth and moisture
After the player action, each bed grows by 1 if temperature is 1–3 and moisture is at least 2; successful growth consumes 1 moisture. At temperature 4, pause growth and do not consume moisture.Prompt 4: set maturity and goal
A crop matures at growth 3/3. Harvest is legal only then and clears the bed. Win after harvesting both crops by the end of day 10.Prompt 5: show the tick result
At each day transition show temperature, action, moisture before/after, growth before/after and maturity. Restart restores both seeds, moisture, day and forecast index.Prompt 6: prepare future checks
For future checks, log daily state and test water cap, one-action limit, growth threshold, hot-day pause, moisture consumption, mature-only harvest, goal and Restart. Do not claim unobserved checks pass.SEELE’s official page describes general plain-English prompting, a playable first version, browser testing and refinement; it does not verify Glasshouse Days. See Free AI game maker for workflow context only.
Prepare future build checks
Compare a per-day log with the stated order. Check watering at the cap, moisture below the threshold, the hot day, mature-only harvest, the day-10 goal and full reset. These are future checks, not passed tests. Record the before and after state so a later build can be compared with the specification.
| Future check | Expected rule | Evidence to capture |
|---|---|---|
| Water action | Adds one to selected bed, maximum 3 | Moisture before/after and action count |
| Growth condition | Progress only at 1–3 temperature and moisture ≥2 | Temperature, moisture and progress |
| Hot day | Temperature 4 pauses growth and preserves moisture | Day, crop state and moisture |
| Harvest | Only 3/3 crop can be harvested | Growth and cleared-bed state |
| Win/reset | Harvest both by day 10; restart restores setup | Outcome and initial state |
No real game run, browser test or measured result is available for this fictional example. The illustrations are original concept art and are not screenshots.
Frequently asked questions
What should a greenhouse simulation prompt define?
Specify daily action order, climate values, moisture thresholds, growth, harvest, the goal and reset behavior.
How many actions can the player take each day?
Glasshouse Days allows exactly one action: water one bed or harvest one mature crop.
What happens on the hot day?
At temperature 4, crop growth pauses and moisture is not consumed.
Were these greenhouse rules tested in a playable game?
No. Glasshouse Days is a fictional rules example, and its day-by-day schedule is hand-calculated rather than observed.
When can a crop be harvested?
Only after it reaches 3 of 3 growth points; harvesting clears that bed.


