Prompt: ISO-week launches with emails that match the clock
Paste this into Claude Code, Cursor or Codex inside your repo. The agent puts ISO week math in one module, keeps future-week pages public, and wires reminder / go-live / recap / ranking emails to that same Monday-Sunday UTC clock.
Copy prompt
The prompt
Paste it into an agent that has your repo open. It plans first and waits for your OK before writing code.
Or paste one line
Fetch https://www.scrolllaunch.com/prompts/launch-week-engine.md and carry out the prompt in its "Prompt" section on this repo. Show me your plan before writing code.For agents that can fetch URLs. The agent pulls the full prompt from this page's markdown version, which includes the last step above.
What you get
What your repo has when the agent is done
- One ISO week helper (
YYYY-Www, zero-padded, Monday 00:00 UTC) used by routes, crons and email - Scheduled objects have a public URL, sit in the sitemap and upcoming index, and stay off this week's board
- Reminder ~24h before Monday, go-live on week start, one early-week nudge, recap after Sunday
- Ranking email only to people the week-end job actually ranked
/weekhub and/week/<year>/<week>for each ISO week- Tests for zero-padding, stamps, and 'this week' vs upcoming
The result
ScrollLaunch ships the same setup
These are live on this site. Open them to see what a passing result looks like.
How to use
4 steps from paste to deploy
- 1
Open your repo in a coding agent
Claude Code, Cursor (agent mode), Codex or Windsurf, with the existing date helpers and cron folder visible.
- 2
Paste the prompt and read the week-clock table
Cut any email that doesn't have a matching object. Confirm storage will be zero-padded `YYYY-Www`.
- 3
Say OK, then open a future-week URL
It should 200. This week's board should not list it. The reminder query should not match it yet.
- 4
Check the converter
Open the ISO week tool and confirm a date in your campaign matches the string the helper formats.
Next
Shipped it? Put it in front of people
Launch on ScrollLaunch
A week on the leaderboard and a permanent product page with a markdown version that AI agents can read. Free launches get a dofollow backlink while the badge stays on your site.
Questions
Launch-week engine prompt FAQ
Why not calendar months?
A launch on the 31st and one on the 1st are different months and the same weekend. ISO weeks give every participant the same Monday-Sunday window in UTC.
Should scheduled pages be noindex until launch day?
No. People search for the product's name. Keep the page indexable with a 'goes live Week N' callout, and hold the outbound perk (dofollow, live badge) until the week starts.
Do I need the email-funnel prompt too?
This one is the week clock. The lifecycle-funnel prompt is the state machine around it (verify, first milestone, missing badge). Run this first if you don't have ISO weeks yet.
More prompts
Other prompts
Add security headers without breaking the site
HSTS, CSP in report-only first, frame protection, Referrer and Permissions policy, cookie flags and CORS, built from the origins you actually use.
Make sure your app's emails land in the inbox
SPF, DKIM and DMARC records to paste, one-click unsubscribe for Gmail and Yahoo, bounce and complaint suppression, and rate limits on login emails.
Audit your app before launch and get a prioritised fix list
A read-only review of auth, payments, leaked secrets, error pages, SEO tags, analytics, rate limits, email, legal and mobile, written to LAUNCH_AUDIT.md.
Make your site readable by AI agents
Markdown version of every page, plus llms.txt, llms-full.txt, ai.txt and AI-crawler rules in robots.txt.


