Your build starts here
Replace bracketed details with your own goal, context, and checks. Keep the first build small enough to inspect.
Implement a preview-only scheduler for [local wall-clock rule] in [named IANA time zone] using the project's supported date-time library. State whether this is a calendar recurrence or a fixed elapsed interval. Require an explicit policy for a local time that does not exist and for a local time that occurs twice; do not silently inherit a library default as a product decision. Build fixtures for an ordinary date, a forward transition, a backward transition, and a time-zone change. For each planned occurrence, show local date and time, zone, offset, UTC instant, and an occurrence ID. Verify previews against the installed time-zone data and document the expected policy. Simulate process restart so an already completed occurrence is not unintentionally repeated. Keep this exercise local and execute no real external jobs until the preview and recovery checks are reviewed.Make this prompt yours
Use for calendar schedules. Date-time construction alone may not enforce your chosen gap or overlap policy; verify behavior explicitly.
You might also hear
- DST
- IANA time zone
- ambiguous local time
- missing local time
- fold
The docs behind it
These references explain the underlying concepts and APIs. The prompt templates and project plans are original examples to adapt to your own setup.
Research sources reviewed .
Editorial review · October 28, 2026
Limited: Original instructional template; not executed. Named-zone recurrence differs from elapsed intervals; gap/overlap policy and restart identity are explicit, with no assumption zoneinfo enforces a product policy automatically.