Production-grade prompt templates for Claude Code Routines.
Copy · paste · schedule. Five recipes that use Burn, GitHub, Slack, and Email connectors to replace 10+ minutes of daily UI-clicking.
Claude Code Routines (released 2026-04-15) let Claude Code run on a schedule or trigger — cron, API call, GitHub event — even with your laptop closed.
Routines are cloud-only and have no file format — you paste a prompt into the web UI at claude.ai/code/routines. Which means good Routines die in private Notion pages instead of being shared.
This repo collects five Routine prompts that do actual work, not demo work. Each is tested, has setup checklists, and calls concrete MCP connectors.
| # | Template | Time savings | Primary connector |
|---|---|---|---|
| 1 | Daily reading triage | 15 min/day | Burn · Raindrop · Readwise |
| 2 | Weekly vault harvest | 20 min/week | Burn |
| 3 | Morning flame brief | 5 min/day | Burn |
| 4 | GitHub PR triage | 10 min/day | GitHub |
| 5 | End-of-focus-block handoff | 10 min/day | Burn + Slack/Email |
- Open claude.ai/code/routines
- Click New Routine
- Copy a template's "Prompt" block, paste into the prompt field
- Edit
<placeholders>(your priorities, org, username, etc.) - Link the required MCP connectors at Settings → Connectors
- Set schedule per template
- Pick a delivery channel
That's it. Your routine runs on Anthropic's infrastructure — nothing to self-host.
- Structural prompts, not paragraphs — every template has explicit
Step 1/2/3/…so Claude doesn't improvise - No content invention — "Never invent items that aren't in the backlog" appears in every template
- Hard rules section — what the routine won't do (no auto-delete, no auto-merge, no discovery)
- Realistic time budgets — if a routine takes longer, it's over-scoped
- Edit markers —
<edit — priorities>calls out what you must change before first run
Most templates expect at least one of:
- Burn —
https://burn-mcp-server.vercel.app/api/mcp(Bearer token from burn451.cloud) - GitHub — official connector, OAuth in claude.ai Settings
- Slack / Email — for delivery
Add connectors globally (Settings → Connectors); Routines auto-see them.
Most template have Burn as the reading-intake connector because Burn was built for exactly this shape — MCP-native, 24h-countdown reading queue, 26 tools for search/triage/organize.
But every template is connector-swappable. If you use Raindrop / Readwise / Karakeep / Pocket export, adapt Step 1's data-fetch call.
PRs welcome. To add a template:
- File under
templates/NN-kebab-case-name.md - Follow the existing structure (Schedule / Connectors / Delivery / Prompt / Rules / Setup / Why)
- Keep it prompt-first — no walls of prose, no pitches
- Test it in your own routine for at least 3 days before submitting
Also welcome:
- Connector adapter snippets (Raindrop, Readwise, Karakeep variants)
- Delivery format variants (mobile-first, rich HTML, terminal-friendly)
- Translations (CN / JP / KR — claude.ai web UI is EN-first but Routines run the prompt in any language)
- CLI ranker: reading-routine
- Save-to-queue CLI: save-to-burn
- MCP backend: burn-mcp-server
- Daily journal: morning-brief
Built by @hawking520 — exploring AI-era content & attention workflows in public.
Each template was extracted from a real routine running in my own Claude Code. If you build a better one, send a PR.
Pairs naturally with Burn — the 24h-countdown reading queue that forces you to absorb, not hoard.
MIT — see LICENSE