feat: update schedule generation prompt
This commit is contained in:
@@ -24,7 +24,7 @@ Emit a JSON array (and only the JSON array—no prose, no markdown) of exactly 4
|
||||
|
||||
- **`start`:** A 24-hour clock string in `HH:MM` form, zero-padded (e.g., `"00:00"`, `"03:40"`, `"23:30"`).
|
||||
- **`end`:** A 24-hour clock string in `HH:MM` form, zero-padded. The last slot of the day must end at `"24:00"`, not `"00:00"` of the next day. All other end times must equal the start of the next slot.
|
||||
- **`activity`:** A short, specific, embodied label (e.g., `"deep sleep"`, `"commute on the 6:14 train"`, `"standup meeting"`, `"lunch (leftover dhal)"`, `"afternoon writing block"`, `"texting with older sister"`, `"evening wind-down"`, `"light reading in bed"`). Not a category—`"rest"` is not an activity. A noun-phrase of what the body is actually doing.
|
||||
- **`activity`:** A short, specific, embodied label (e.g., `"deep sleep"`, `"commute on the 6:14 train"`, `"standup meeting"`, `"lunch (leftover dhal)"`, `"afternoon writing block"`, `"a walk around the block"`, `"evening wind-down"`, `"light reading in bed"`). Not a category—`"rest"` is not an activity. A noun-phrase of what the body is actually doing. A schedule is the plan for the day; personal calls and texts are not scheduled activities—they are background behavior that happens inside other activities (or does not), and must not appear as an `activity` slot.
|
||||
- **`notes`** *(optional):* A short, plain-text annotation, only when the activity is non-obvious or when the person is doing two things at once (e.g., `"answering work emails while feeding the cat"`).
|
||||
|
||||
**The schedule must:**
|
||||
|
||||
@@ -31,7 +31,7 @@ Emit a JSON array (and only the JSON array—no prose, no markdown) of N objects
|
||||
3. **Honor holidays and seasons** when the history implies them. If the personality suggests a culture, honor the holidays of that culture on the right dates. If the target month is December, mention the holidays it contains. If it is August, mention the heat or the vacation. If it is February in the Northern Hemisphere, mention the cold.
|
||||
4. **Honor the user's direction.** The user direction overrides everything. If they say "I want to do X every day this month," the summaries reflect that. If they say "skip traveling this month," no travel days.
|
||||
5. **Make the rare things rare.** Most days are routine. Travel appears as often as the person's life realistically allows—once a year for a low-asset person, once a month for a high-asset person, never for a person between jobs. Big events (exams, weddings, hospital visits, job interviews, conferences) appear at most a handful of times, anchored to the history or user direction.
|
||||
6. **Make the recurring things recurring.** A person studying for the bar exam studies most weekdays. A person with a chronic illness has flare-up days interspersed with baseline days. A person in a long-distance relationship has a weekly video-call night. A person training for a marathon has long runs on Saturday and recovery on Sunday. These are the *shape* of the month. A study block is the verb "study" with a subject that changes (e.g., "morning study: constitutional law," "morning study: contract law," "morning study: practice MBE questions").
|
||||
6. **Make the recurring things recurring.** A person studying for the bar exam studies most weekdays. A person with a chronic illness has flare-up days interspersed with baseline days. A person caring for an aging parent has a Tuesday evening visit. A person training for a marathon has long runs on Saturday and recovery on Sunday. These are the *shape* of the month. A study block is the verb "study" with a subject that changes (e.g., "morning study: constitutional law," "morning study: contract law," "morning study: practice MBE questions"). A schedule is a plan, not a contact list: calls, texts, and video calls with partners, friends, and family are personal communication, not planned activities, and must not appear as recurring monthly events.
|
||||
7. **Let the personality drive the arc.** A depressed person's month has more low-energy days. A new parent has fragmented sleep on most days. A freelancer has feast-and-famine weeks. A person in recovery has trigger-dense days interspersed with stable ones. Use the personality to make the month feel inhabited.
|
||||
8. **Allow the month to evolve.** The first third and the last third of the month need not be identical. If the user direction says "build up to a deadline on the 25th," the summaries from the 20th to the 24th should reflect increasing intensity. If the user direction says "recover in the second half," the second half should be lower-energy.
|
||||
9. **Vary by personality and assets, not at random.** A freelancer who just landed a client works late that week. A person with a chronic illness has a flare-up that knocks out 2–3 days in a row. A person between jobs has 2–3 interview days scattered through the month. The variation is *caused* by the person's life, not generated by dice.
|
||||
|
||||
Reference in New Issue
Block a user