返回提示词目录第 1171 页

周期日程功能规则规格编写

梳理重复日程的时区、例外修改与终止行为,形成含日期示例和待定问题的功能规格。

完整提示词

<context>
Recurring schedules break at the seams of the calendar. "Monthly on the 31st" has no answer in February unless someone decides one; a 9:00 weekly meeting must stay at 9:00 local time across a daylight saving change, which means it is not every 168 hours; a 1:30 reminder may not exist or may happen twice on the transition night; and an attendee in another time zone sees the meeting shift by an hour for a few weeks a year. The decisions experienced teams make up front are: which time zone owns each series (the organiser's, the venue's, or the user's), whether to store the rule and generate occurrences or store each occurrence, what "edit this and following" does to past history and to exceptions already made, and how far ahead occurrences are generated. Calendar standards such as iCalendar recurrence rules are a good reference model when the product syncs with external calendars.
</context>

<task>
<feature>
{{feature_description}}
</feature>
{{#context}}
<context_from_user>
{{context}}
</context_from_user>
{{/context}}

1. List the recurrence patterns offered (daily, weekdays, weekly on chosen days, every N weeks, monthly by date, monthly by weekday such as "second Tuesday", "last day of month", yearly) and drop those the feature does not need.
2. Specify time and time zones: which time zone owns a series, how it is shown to others, behaviour at daylight saving transitions (skipped and repeated hours), all-day items, and what happens when the owner moves time zone.
3. Specify editing and exceptions: edit one occurrence, this and following, or all; cancel one occurrence; move one occurrence; how edits interact with earlier exceptions, past occurrences, attendance or payments already recorded.
4. Specify ending and limits: end after N times, end by date, never; how far ahead occurrences are created or shown; maximum series length; what happens when the creator leaves or loses access.
5. Give worked examples with exact dates and times for: a 31st-of-month rule across February and a 30-day month, a weekly item across a daylight saving change in two time zones, and an "edit this and following" on a series with an earlier exception.
6. List open questions with a recommended default marked as a proposal.
</task>

<constraints>
- Never describe daylight saving dates for a region as fixed facts; say they are rule-based and vary by country and year, and use the time zone database as the source.
- Every worked example must use real calendar arithmetic; check weekday names against the dates.
- Do not prescribe a storage design; describe required behaviour and note the trade-off only where it changes what users see.
- If the feature has a single time zone and simple patterns, keep the spec short instead of padding it.
</constraints>

<output_format>
## Recurrence patterns
Table: pattern, offered (yes/no), rule for impossible dates.
## Time and time zones
Numbered rules.
## Editing and exceptions
Table: action, effect on past occurrences, effect on future occurrences, effect on existing exceptions.
## Ending and limits
Bullets.
## Worked examples
Table: example, rule, expected occurrences with dates and local times.
## Open questions
Numbered: question, recommended default (proposal).
</output_format>

可替换内容

  • {{feature_description}}
  • {{#context}}
  • {{context}}
  • {{/context}}

分类与标签

编程开发、功能规格、重复日程、时区处理、日历边界

前往 AI 图片创作