Claude Routines Starter Pack — 7 Ready-to-Deploy Templates
============================================================

How to use these templates:
1. Copy the prompt from any template below.
2. Go to https://claude.ai/code/routines and click "New Routine."
3. Paste the prompt into the Task field.
4. Set the trigger type and schedule shown in the template.
5. Attach the connectors listed under Requirements.
6. Click "Run now" to test before activating.

Adjust any placeholder values (your name, repo names, timezone, file paths) to match your setup.

---

TEMPLATE 1: Daily Morning Email Digest
---------------------------------------
Trigger: Schedule — Daily at 7:00 AM (your local time)
Requirements: Gmail connector

Prompt:
Check my Gmail inbox for unread messages received in the last 24 hours.
Categorize each message as:
- URGENT: needs response today
- ACTION: needs follow-up within 3 days
- INFO: no action needed
- SPAM: can be archived

For every URGENT and ACTION message, write a 2-sentence reply starter.
Output a numbered list sorted by category to /logs/email-digest-{YYYY-MM-DD}.md.
If the inbox is empty, write "Inbox clear — {date}" to the file and exit.

---

TEMPLATE 2: Weekly GitHub PR Staleness Check
----------------------------------------------
Trigger: Schedule — Every Monday at 8:00 AM
Requirements: GitHub connector, target repository access

Prompt:
Check all open pull requests in the repository [YOUR-REPO-NAME].
For any PR that has been open more than 5 days with no review activity and no comments in the last 48 hours, post a comment that says:
"Hi [author] — just checking in on this PR. Is it still in progress, blocked, or ready for review? Thanks!"
After reviewing all PRs, write a summary to /logs/pr-staleness-{YYYY-MM-DD}.md listing:
- Total open PRs
- PRs that received a follow-up comment
- PRs already under active review (no comment needed)

---

TEMPLATE 3: Nightly Bug Report Triage
----------------------------------------
Trigger: Schedule — Daily at 11:00 PM
Requirements: GitHub connector (issues access)

Prompt:
Check all open GitHub issues in [YOUR-REPO-NAME] that have the label "bug" and were created in the last 7 days.
For each issue:
1. Assess the likely severity based on the description: Critical, High, Medium, or Low.
2. Identify if a similar issue already exists in open or closed issues.
3. Add a severity label to the issue (Critical, High, Medium, or Low).
4. If a duplicate exists, add a comment linking to the original and tag it with "duplicate."
Write a summary of all triaged issues to /logs/bug-triage-{YYYY-MM-DD}.md.

---

TEMPLATE 4: Post-Deploy Smoke Check (API Trigger)
---------------------------------------------------
Trigger: API — fire after each production deployment
Requirements: Web access, optional Slack connector for notifications

Prompt:
Run a smoke check on the production deployment at [YOUR-PROD-URL].
Check the following:
1. Homepage loads and returns HTTP 200.
2. Login page loads correctly.
3. API health endpoint at [YOUR-HEALTH-ENDPOINT] returns a healthy status.
4. Key user flow: [describe your most important user action, e.g., "user can add item to cart"].

If all checks pass, post "Deploy smoke check: PASSED — {timestamp}" to the #deploys Slack channel.
If any check fails, post "Deploy smoke check: FAILED — {what failed} — {timestamp}" to #deploys and create a GitHub issue with the failure details and label "smoke-check-failure."

---

TEMPLATE 5: Daily Social Media Content Ideas
----------------------------------------------
Trigger: Schedule — Daily at 6:30 AM
Requirements: None (web search access recommended)

Prompt:
Generate 5 social media content ideas for today based on the topic: [YOUR NICHE, e.g., "Claude AI and AI automation for business owners"].
For each idea, write:
- Platform: (Instagram, LinkedIn, or X/Twitter)
- Format: (carousel, short video hook, text post, or thread)
- Hook: one attention-grabbing opening line
- Key points: 3 bullet points of the core message
- CTA: one call-to-action line

Save all 5 ideas to /content/ideas-{YYYY-MM-DD}.md.
Prioritize ideas that are timely, practical, and relevant to non-technical business owners.

---

TEMPLATE 6: Weekly Content Performance Review
-----------------------------------------------
Trigger: Schedule — Every Sunday at 9:00 AM
Requirements: Google Drive or Notion connector (for accessing content tracker)

Prompt:
Review the content tracker file at [PATH TO YOUR TRACKER FILE].
For each post published in the last 7 days, summarize:
- Title
- Platform
- Date published
- Engagement notes (if any are recorded in the tracker)
- Status: Published, Scheduled, or Draft

Identify:
- Any drafts that have been sitting for more than 14 days (flag these as "stale")
- Any upcoming posts scheduled for this week that have no caption or asset attached

Write a weekly content summary to /content/weekly-review-{YYYY-MM-DD}.md.
Include a section at the top called "This Week's Focus" listing the top 3 priorities based on what's incomplete or scheduled.

---

TEMPLATE 7: Morning Task Prioritization
-----------------------------------------
Trigger: Schedule — Daily at 6:00 AM (weekdays only)
Requirements: Notion or Google Tasks connector (for task access)

Prompt:
Check my task list in [YOUR TASK TOOL, e.g., Notion database named "Tasks" or Google Tasks list named "Work"].
Retrieve all tasks that are:
- Due today
- Overdue (past due date, not yet completed)
- Marked as high priority with no due date set

Sort them into three groups:
1. MUST DO TODAY: overdue or due today + high priority
2. SHOULD DO TODAY: due today + normal priority
3. PLAN AHEAD: high priority but no current due date

For each task in group 1, write a 1-sentence plan for how to start it.
Save the full prioritized list to /logs/daily-tasks-{YYYY-MM-DD}.md.

---

Claude Routines Starter Pack from https://coding180.com
