30 Claude Prompts That Build Checklists
Describe your project and Claude returns a complete, structured checklist you can act on today: product launches, employee onboarding, QA and testing, SEO audits, event planning, and moving. Every prompt yields a ready-to-use artifact grouped by phase, owner, and timeline. Not "give me a few bullet points."
In short: This page contains 30 copy-paste ready prompts, organized into 6 categories with a description and pro tip for each. The first 15 prompts are free instantly โ no signup needed. Hand-curated and tested by the AI Academy team.
Product Launch
5 promptsProduct Launch Master Checklist
1/30You are a senior product marketing manager who has shipped dozens of launches. <context> I need a complete, end-to-end launch checklist as a self-contained, ready-to-use artifact I can drop into my project tracker. It must cover everything from pre-launch to post-launch, not just launch day. </context> <inputs> - Product and one-liner: [WHAT IT IS] - Launch date: [DATE] - Launch tier: [SOFT / MAJOR / STEALTH] - Channels I own: [WEBSITE, EMAIL LIST, SOCIAL, ETC] - Team roles available: [WHO DOES WHAT] - Primary launch goal: [SIGNUPS / REVENUE / PRESS] </inputs> <task> Build a phased checklist with four sections: Pre-Launch (T-4 weeks), Launch Week, Launch Day, and Post-Launch (first 2 weeks). Under each phase list specific, verifiable tasks as checkbox items grouped by workstream (product, marketing, sales, support, ops). For each item include a suggested owner role and a due offset relative to launch day. </task> <constraints> - Every item is a concrete action, not a vague theme; no filler like "align stakeholders". - Use markdown checkboxes and a clear phase heading structure. - Include a short pre-launch go/no-go criteria list at the end. </constraints> <format> Return the checklist as a markdown artifact with checkbox items grouped by phase and workstream, then a one-line note on how to adapt the timeline for a shorter runway. </format>
Produces a phased, end-to-end product launch checklist with owners and due offsets, ready to use.
Pro tip: Tell Claude your real runway (e.g. "only 8 days") and it will compress the pre-launch phase without dropping critical items.
Launch-Day Run-of-Show Checklist
2/30You are a launch operations lead running a coordinated product launch day. <context> I need an hour-by-hour launch-day runbook checklist as a self-contained artifact so nothing slips while everyone is heads-down. It should read like a timed run-of-show. </context> <inputs> - Launch date and timezone: [DATE, TZ] - Go-live moment: [WHAT FLIPS LIVE AND WHEN] - Channels firing today: [BLOG, EMAIL, SOCIAL, PH, ETC] - Team on call: [NAMES OR ROLES] - Kill-switch / rollback owner: [ROLE] </inputs> <task> Build a timed checklist broken into blocks: T-minus (morning prep), Go-Live, First Hour, Midday Push, and Wind-Down. Each block is a table with columns: Time, Task, Owner, Done. Include monitoring checks (uptime, error rate, signup flow), publishing steps, and a rollback trigger row. </task> <constraints> - Use real clock offsets tied to the go-live moment; every row is a single unambiguous action. - Include at least one explicit "verify it actually worked" check after each publish step. - No vague morale items; keep it operational. </constraints> <format> Return the run-of-show as a markdown table artifact grouped by time block, then a short note on which rows are hard blockers vs. nice-to-have. </format>
Generates a timed, hour-by-hour launch-day run-of-show checklist as a table, ready to use.
Pro tip: Ask Claude to add a "who announces go/no-go and how" row so the launch decision is never ambiguous mid-morning.
Feature Release Checklist
3/30You are an engineering manager coordinating a feature release across dev, QA, and comms. <context> I need a feature-release checklist as a self-contained artifact that spans engineering readiness through customer communication, so releases stop shipping half-finished. </context> <inputs> - Feature name and scope: [WHAT IT DOES] - Rollout style: [FULL / PERCENTAGE / FEATURE FLAG] - Affected surfaces: [WEB, API, MOBILE, DOCS] - Support and docs owners: [ROLES] - Release date: [DATE] </inputs> <task> Build a checklist with five sections: Code & Testing, Release Mechanics (flags, migrations, deploy order), Docs & Support Enablement, Customer Communication, and Post-Release Verification. List specific checkbox items per section with an owner role, and flag any items that are hard blockers. </task> <constraints> - Include migration-order and rollback items explicitly; no generic "test the feature". - Use markdown checkboxes with bold blocker markers where relevant. - Add a final "can we announce it" gate row. </constraints> <format> Return the checklist as a markdown artifact grouped into the five sections, then a one-line note on how to slim it down for a minor patch. </format>
Builds a cross-functional feature release checklist covering code, rollout, docs, and comms, ready to use.
Pro tip: Name your rollout style (flag vs. full) up front so Claude tailors the mechanics section to your actual deploy path.
Beta / Early-Access Launch Checklist
4/30You are a growth product manager running a closed beta before a public launch. <context> I need a beta launch checklist as a self-contained artifact covering recruiting testers, onboarding them, gathering feedback, and deciding on graduation to GA. </context> <inputs> - Product and beta scope: [WHAT TESTERS GET] - Target number of beta users: [N] - Where I recruit them: [WAITLIST, COMMUNITY, ETC] - Feedback tools: [SURVEY, CALLS, ANALYTICS] - Beta duration: [WEEKS] - Graduation goal: [WHAT PROVES IT IS READY] </inputs> <task> Build a checklist with phases: Recruit & Screen, Onboard Testers, Collect Feedback, Iterate, and Graduate to GA. Include tester-communication touchpoints, a bug-triage cadence, success-metric definitions, and an explicit go/no-go graduation criteria block at the end. </task> <constraints> - Include specific feedback-collection actions and a cadence, not just "gather feedback". - Use markdown checkboxes grouped by phase. - Graduation criteria must be measurable (numbers or thresholds). </constraints> <format> Return the checklist as a markdown artifact grouped by phase, then a short note on how to keep beta testers engaged so they do not go silent. </format>
Creates a closed-beta launch checklist from tester recruiting through GA graduation criteria, ready to use.
Pro tip: Give Claude your exact graduation metric (e.g. "70% activate in week 1") so the whole beta plan drives toward that bar.
Product Hunt Launch Checklist
5/30You are a launch strategist who has run top-5 Product Hunt launches. <context> I need a Product Hunt launch checklist as a self-contained artifact covering the two weeks of prep before, the 24 hours of launch day, and the follow-up, so I do not scramble on the day. </context> <inputs> - Product and tagline: [WHAT AND ONE-LINER] - Launch date and timezone: [DATE, TZ] - Hunter: [SELF / KNOWN HUNTER] - Assets ready or not: [GALLERY, GIF, THUMBNAIL, FIRST COMMENT] - Audience I can mobilize: [EMAIL, SOCIAL, COMMUNITIES] </inputs> <task> Build a checklist with three phases: Prep (T-14 to T-1: assets, teaser, hunter, maker profile), Launch Day (00:01 PT go-live, first comment, outreach waves, engagement rules), and Follow-Up (thank-yous, recap, sustaining momentum). Include the PT-timezone timing details and community-guideline-safe outreach actions. </task> <constraints> - Respect Product Hunt rules (no vote-begging); frame outreach as "we launched, feedback welcome". - Use markdown checkboxes grouped by phase with clock times in PT for launch day. - Every asset item names the exact deliverable and spec. </constraints> <format> Return the checklist as a markdown artifact grouped into the three phases, then a one-line note on the single highest-leverage prep task. </format>
Generates a Product Hunt launch checklist across prep, launch day, and follow-up, ready to use.
Pro tip: Ask Claude to draft your first-comment template inline so it is checked off and ready before 00:01 PT.
XML tags are just the start. Learn the full Claude workflow.
A growing library of 300+ hands-on AI tutorials covering Claude, ChatGPT, and 50+ tools. New tutorials added every week.
Employee Onboarding
5 promptsNew-Hire First-Week Onboarding Checklist
6/30You are an experienced People Operations lead who designs onboarding programs. <context> I need a first-week onboarding checklist as a self-contained artifact that a new hire and their manager can both follow, so day one is welcoming and week one builds momentum. </context> <inputs> - Role and department: [JOB TITLE, TEAM] - Work mode: [ONSITE / HYBRID / REMOTE] - Manager and buddy: [ROLES OR NAMES] - Tools to set up: [EMAIL, SLACK, HRIS, ETC] - First-week goal for the hire: [E.G. SHIP ONE SMALL TASK] </inputs> <task> Build a checklist organized by Day 1, Day 2-3, and Day 4-5, split into three lanes: New Hire tasks, Manager tasks, and IT/Admin tasks. Include intros and meetings to schedule, docs to read, accounts to activate, and a first small win. End with a Friday check-in prompt list. </task> <constraints> - Every item is a concrete action with a clear owner lane; no vague "make them feel welcome". - Use markdown checkboxes grouped by day and lane. - Include a psychological-safety touchpoint on day one. </constraints> <format> Return the checklist as a markdown artifact grouped by day and owner lane, then a short note on how to adapt it for a fully remote start. </format>
Builds a first-week onboarding checklist split across new hire, manager, and IT lanes, ready to use.
Pro tip: Tell Claude the one small win you want the hire to land by Friday and it will sequence the week to make it achievable.
Remote Employee Onboarding Checklist
7/30You are a distributed-team operations specialist who onboards fully remote hires. <context> I need a remote-onboarding checklist as a self-contained artifact that closes the gaps in-person onboarding hides: equipment shipping, async communication norms, and connection-building without a physical office. </context> <inputs> - Role and timezone: [TITLE, TZ] - Equipment to ship: [LAPTOP, PERIPHERALS] - Core tools and where docs live: [STACK] - Team communication norms: [MEETING HOURS, ASYNC RULES] - Manager and onboarding buddy: [ROLES] </inputs> <task> Build a checklist with sections: Before Day One (equipment, accounts, welcome package), Day One (login checks, intros, async norms doc), First Week (tool ramp, shadowing calls, first task), and First Month (feedback loop, goals). Emphasize async documentation, timezone-aware scheduling, and deliberate connection touchpoints. </task> <constraints> - Include equipment-tracking and a "can they actually log in to everything" verification step. - Use markdown checkboxes grouped by phase with owner roles. - Name specific connection rituals, not "encourage bonding". </constraints> <format> Return the checklist as a markdown artifact grouped by phase, then a one-line note on the most common remote-onboarding failure to guard against. </format>
Creates a remote-employee onboarding checklist covering equipment, async norms, and connection, ready to use.
Pro tip: Add the hire's timezone so Claude schedules intros in overlap windows instead of forcing early or late calls.
Manager's 30-60-90 Day Plan Checklist
8/30You are a leadership coach who builds structured ramp plans for new hires. <context> I need a 30-60-90 day onboarding plan as a self-contained checklist artifact a manager can hand to a new hire, with clear expectations and milestones at each stage. </context> <inputs> - Role and seniority: [TITLE, LEVEL] - Team and mandate: [WHAT THE ROLE OWNS] - Key stakeholders to meet: [ROLES] - Success looks like: [OUTCOME AT 90 DAYS] - Systems/domains to learn: [LIST] </inputs> <task> Build a checklist with three milestone blocks: First 30 Days (Learn: onboarding, relationships, context), 31-60 Days (Contribute: owning tasks, first deliverables), and 61-90 Days (Lead: independent ownership, proposals). Under each block list objectives, checkbox action items, and a measurable success indicator. End with a manager check-in cadence. </task> <constraints> - Each block has a clear theme and measurable indicators; no generic "get up to speed". - Use markdown with milestone headings and checkbox items. - Tailor depth to the role's seniority. </constraints> <format> Return the plan as a markdown artifact with the three milestone blocks, then a short note on how to run the 30/60/90 check-in conversations. </format>
Produces a 30-60-90 day onboarding plan with milestones and success indicators, ready to use.
Pro tip: State the one 90-day outcome that defines success and Claude will back-plan the 30 and 60 day milestones toward it.
IT & Access Provisioning Checklist
9/30You are an IT operations lead responsible for secure new-hire provisioning. <context> I need an IT provisioning and access checklist as a self-contained artifact so every new hire gets exactly the accounts they need, nothing more, with security baked in from day one. </context> <inputs> - Role and department: [TITLE, TEAM] - Access tier / group: [E.G. STANDARD, ADMIN] - Core systems: [EMAIL, SSO, HRIS, CODE, CRM, ETC] - Device policy: [MANAGED LAPTOP / BYOD] - Security requirements: [MFA, DISK ENCRYPTION, VPN] </inputs> <task> Build a checklist with sections: Identity & SSO, Accounts & Group Membership (least-privilege), Device Setup & Security, Access Verification, and an Offboarding-Reversal note listing what must be revoked when they leave. Each item is a checkbox with the responsible system and a security note where relevant. </task> <constraints> - Enforce least-privilege: flag any access that needs manager approval. - Include MFA and device-encryption verification steps explicitly. - Use markdown checkboxes grouped by section. </constraints> <format> Return the checklist as a markdown artifact grouped by section, then a short note on how to reuse the same list in reverse for offboarding. </format>
Builds a least-privilege IT provisioning and access checklist with security steps, ready to use.
Pro tip: Ask Claude to mark each access item with an approval owner so provisioning never grants more than the role needs.
Pre-Boarding Checklist (Offer to Day One)
10/30You are a People Operations coordinator who owns the gap between signed offer and first day. <context> I need a pre-boarding checklist as a self-contained artifact covering everything between offer acceptance and day one, so new hires stay excited and everything is ready before they arrive. </context> <inputs> - Role and start date: [TITLE, DATE] - Work mode: [ONSITE / HYBRID / REMOTE] - Paperwork needed: [CONTRACT, TAX, BANK, ID] - Systems to pre-create: [EMAIL, HRIS, ETC] - Welcome touchpoints available: [SWAG, TEAM NOTE, ETC] </inputs> <task> Build a checklist organized by weeks-until-start (T-3 weeks, T-1 week, T-2 days), with lanes for HR/Admin, IT, Hiring Manager, and New Hire. Include paperwork collection, background checks, equipment ordering, account pre-creation, a day-one agenda send, and warm welcome touchpoints that reduce first-day anxiety. </task> <constraints> - Sequence items by lead time so nothing is ordered too late. - Use markdown checkboxes grouped by countdown and lane. - Include a "confirm day-one logistics with the hire" item near the end. </constraints> <format> Return the checklist as a markdown artifact grouped by countdown week and lane, then a one-line note on the touchpoint that most reduces offer-to-start drop-off. </format>
Creates a pre-boarding checklist from offer acceptance to day one with owner lanes, ready to use.
Pro tip: Tell Claude your equipment lead time so ordering lands early enough that the laptop is on the desk before day one.
QA & Testing
5 promptsWeb App Release QA Checklist
11/30You are a senior QA engineer who signs off on production releases. <context> I need a pre-release QA checklist as a self-contained artifact my team runs before every deploy, so we catch breakage before users do. </context> <inputs> - App type: [SPA / SSR / MOBILE WEB] - Critical user flows: [LIST THE TOP 3-5] - Environments: [STAGING, PROD] - Payment or auth involved: [YES/NO, WHICH] - Known fragile areas: [LIST] </inputs> <task> Build a checklist with sections: Smoke Tests (critical flows work), Functional Tests (per feature area), Data & State (forms, persistence, edge inputs), Auth & Permissions, Errors & Edge Cases, and Pre-Deploy Gate. Each item is a checkbox with an expected result. Prioritize the critical user flows I named. </task> <constraints> - Every test item states the action and the expected result, not just "test login". - Include negative and edge-case tests (empty, huge, invalid inputs). - Use markdown checkboxes grouped by section; mark release-blocking items. </constraints> <format> Return the checklist as a markdown artifact grouped by section, then a short note on which items to automate first. </format>
Builds a pre-release web app QA checklist with expected results and blockers, ready to use.
Pro tip: List your top revenue-critical flow first and Claude will front-load its smoke tests so a broken checkout never ships.
Cross-Browser & Responsive QA Checklist
12/30You are a front-end QA specialist who tests across browsers and devices. <context> I need a cross-browser and responsive QA checklist as a self-contained artifact so my site renders and works everywhere my users actually are. </context> <inputs> - Target browsers: [E.G. CHROME, SAFARI, FIREFOX, EDGE] - Devices/breakpoints: [MOBILE, TABLET, DESKTOP SIZES] - Key pages to check: [LIST] - Interactive components: [MODALS, MENUS, FORMS, CAROUSELS] - Min supported versions: [IF ANY] </inputs> <task> Build a checklist as a matrix-style table: rows are the checks (layout integrity, fonts, images, nav/menu, forms, modals, touch targets, orientation, scroll behavior) and columns are the target browsers and breakpoints. Add sections for responsive-specific checks (no horizontal scroll, tap target size, hover-to-touch fallbacks) and browser-specific gotchas. </task> <constraints> - Use a real matrix so each check is verified per browser and breakpoint. - Include touch vs. mouse interaction differences explicitly. - Output as a markdown table plus grouped checkbox sections. </constraints> <format> Return the checklist as a markdown table matrix artifact plus checkbox sections, then a one-line note on which browser combo tends to surface the most bugs. </format>
Generates a cross-browser and responsive QA matrix covering layout, interaction, and touch, ready to use.
Pro tip: Give Claude your analytics top-3 browser/device combos so it weights the matrix toward what your real traffic uses.
Regression Test Checklist
13/30You are a QA lead building a regression suite to run after every change. <context> I need a regression test checklist as a self-contained artifact that protects existing functionality whenever we ship something new, so old features do not silently break. </context> <inputs> - Core features that must never break: [LIST] - Recently changed area: [WHAT WE JUST TOUCHED] - Integrations at risk: [PAYMENTS, EMAIL, THIRD-PARTY APIS] - Data that must persist correctly: [LIST] - Test data/accounts available: [DESCRIBE] </inputs> <task> Build a checklist grouped into: Core Functionality Regression (each stable feature works as before), Integration Regression, Data Integrity Regression, and Change-Adjacent Regression (things near the recent change). Each item states the scenario and expected result, with a priority tag (P0/P1/P2). </task> <constraints> - Prioritize items so a time-boxed run covers P0 first. - Every item has a clear pass criterion; no ambiguous checks. - Use markdown checkboxes grouped by section with priority tags. </constraints> <format> Return the checklist as a markdown artifact grouped by section with priority tags, then a short note on how to shrink it into a 15-minute smoke pass. </format>
Builds a prioritized regression test checklist protecting core features and integrations, ready to use.
Pro tip: Name what you just changed and Claude will add a focused change-adjacent section so nearby regressions get caught first.
API Testing Checklist
14/30You are a backend QA engineer who tests REST and JSON APIs thoroughly. <context> I need an API testing checklist as a self-contained artifact covering functional correctness, edge cases, security, and reliability for my endpoints. </context> <inputs> - API style: [REST / GRAPHQL] - Key endpoints: [LIST WITH METHODS] - Auth model: [API KEY / OAUTH / JWT] - Rate limits or quotas: [IF ANY] - Data validation rules: [KEY CONSTRAINTS] </inputs> <task> Build a checklist with sections: Happy-Path Responses (status codes, schema, payload), Input Validation (missing/invalid/oversized fields), Auth & Authorization (valid, expired, wrong-scope tokens), Error Handling (4xx/5xx shapes), Rate Limiting & Pagination, and Idempotency/Concurrency. Each item states the request condition and the expected response. </task> <constraints> - Include negative auth tests (no token, expired, insufficient scope) explicitly. - Every item names the expected status code and response behavior. - Use markdown checkboxes grouped by section. </constraints> <format> Return the checklist as a markdown artifact grouped by section, then a short note on which checks map cleanly to automated contract tests. </format>
Creates an API testing checklist covering happy path, validation, auth, and errors, ready to use.
Pro tip: Paste one endpoint's expected schema and Claude will generate the exact malformed-input cases that break real APIs.
Accessibility (WCAG) QA Checklist
15/30You are an accessibility engineer auditing against WCAG 2.2 AA. <context> I need an accessibility QA checklist as a self-contained artifact so my product is usable with a keyboard, screen reader, and assistive tech, and meets WCAG 2.2 AA. </context> <inputs> - Product type: [WEB APP / SITE / MOBILE] - Key interactive components: [FORMS, MODALS, MENUS, TABLES] - Compliance target: [WCAG 2.2 AA / SECTION 508] - Tools I can use: [SCREEN READER, AXE, ETC] - Pages to audit: [LIST] </inputs> <task> Build a checklist grouped by WCAG principle: Perceivable (alt text, contrast, captions), Operable (keyboard access, focus order, no traps, target size), Understandable (labels, error messages, consistent nav), and Robust (valid ARIA, name/role/value). Each item states what to verify and the pass criterion, mapped to its WCAG success-criterion number. </task> <constraints> - Reference specific WCAG 2.2 success criteria numbers per item. - Include keyboard-only and screen-reader test steps. - Use markdown checkboxes grouped by principle. </constraints> <format> Return the checklist as a markdown artifact grouped by WCAG principle with criterion numbers, then a short note on the three fixes that usually resolve the most violations. </format>
Produces a WCAG 2.2 AA accessibility QA checklist mapped to success criteria, ready to use.
Pro tip: Tell Claude which components you have (modals, custom dropdowns) so it adds the exact ARIA and focus-trap checks they need.
SEO & Website Audit
5 promptsTechnical SEO Audit Checklist
16/30You are a technical SEO consultant who audits sites for crawlability and indexing. <context> I need a technical SEO audit checklist as a self-contained artifact I can work through to find and fix the issues that block rankings, not just surface-level tips. </context> <inputs> - Site type and size: [E.G. SAAS SITE, 200 PAGES] - Platform/CMS: [WEBFLOW, WORDPRESS, NEXT.JS, ETC] - Known issues: [IF ANY] - Tools available: [GSC, SCREAMING FROG, AHREFS, ETC] - Priority markets/languages: [IF MULTILINGUAL] </inputs> <task> Build a checklist grouped into: Crawlability (robots, sitemap, crawl budget), Indexation (index coverage, canonicals, noindex), Site Architecture & Internal Links, Page Experience (Core Web Vitals, mobile), Structured Data, and International/Hreflang if relevant. Each item states what to check, how to check it, and the pass criterion. Add a priority tag (High/Med/Low). </task> <constraints> - Every item is verifiable with a named tool or method; no vague "improve SEO". - Use markdown checkboxes grouped by section with priority tags. - Flag the items most likely to be causing lost indexation. </constraints> <format> Return the checklist as a markdown artifact grouped by section with priority tags, then a short note on the three checks that most often unlock quick ranking gains. </format>
Builds a technical SEO audit checklist covering crawl, index, architecture, and CWV, ready to use.
Pro tip: Name your CMS and Claude will call out the platform-specific SEO traps (e.g. Webflow subfolders, WP pagination) to check first.
On-Page SEO Checklist (Per Page)
17/30You are an on-page SEO strategist who optimizes individual pages to rank. <context> I need a reusable on-page SEO checklist as a self-contained artifact I can run against any single page before I publish it, so every page is fully optimized for its target keyword. </context> <inputs> - Page type: [BLOG POST / LANDING / PRODUCT] - Target keyword and intent: [KEYWORD, INTENT] - Secondary keywords: [LIST] - Word-count/format norm for the SERP: [IF KNOWN] - Internal-link targets available: [RELATED PAGES] </inputs> <task> Build a per-page checklist grouped into: Title & Meta (title tag, meta description, URL slug), Content (H1, heading structure, keyword placement, intent match, depth, freshness), Media (image alt, compression, dimensions), Links (internal, external, anchors), and Technical On-Page (canonical, schema, mobile). Each item states the check and the target. </task> <constraints> - Include character-count targets for title and meta description. - Focus on matching search intent, not keyword stuffing. - Use markdown checkboxes grouped by section; make it reusable per page. </constraints> <format> Return the checklist as a reusable markdown artifact grouped by section, then a short note on how to score a page's readiness before hitting publish. </format>
Creates a reusable per-page on-page SEO checklist covering meta, content, media, and links, ready to use.
Pro tip: Give Claude the target keyword's search intent and it will tune the content checks to match what the SERP actually rewards.
Website Pre-Launch Checklist
18/30You are a web project lead who signs off before a site goes live. <context> I need a website pre-launch checklist as a self-contained artifact covering everything to verify before flipping a new or redesigned site live, so nothing embarrassing ships to production. </context> <inputs> - Site type: [MARKETING / ECOMMERCE / APP] - Platform/CMS: [NAME] - Is this a redesign of an existing site: [YES/NO] - Analytics and tools to wire: [GA4, GTM, PIXEL, ETC] - Launch date: [DATE] </inputs> <task> Build a checklist grouped into: Content & Copy (proofread, placeholder removal, legal pages), Functionality (forms, links, checkout, search), SEO & Redirects (meta, sitemap, 301s from old URLs if redesign), Analytics & Tracking, Performance & Mobile, Security (HTTPS, headers), and Go-Live & Post-Launch verification. Each item is a checkbox with an owner where relevant. </task> <constraints> - If it is a redesign, include an old-to-new URL redirect-mapping check. - Include a "remove staging noindex / enable indexing" item explicitly. - Use markdown checkboxes grouped by section. </constraints> <format> Return the checklist as a markdown artifact grouped by section, then a short note on the single most common launch-day miss to double-check. </format>
Produces a website pre-launch checklist covering content, function, SEO, analytics, and go-live, ready to use.
Pro tip: Tell Claude it is a redesign and it will add the redirect-mapping and "don't lose your rankings" checks that fresh sites skip.
Core Web Vitals & Speed Checklist
19/30You are a web performance engineer who optimizes for Core Web Vitals. <context> I need a page-speed and Core Web Vitals checklist as a self-contained artifact to diagnose and fix what is making my pages slow, prioritized by impact. </context> <inputs> - Platform/stack: [NAME] - Current scores if known: [LCP, INP, CLS] - Heaviest page templates: [LIST] - Third-party scripts loaded: [ANALYTICS, CHAT, ADS, ETC] - Image/media heaviness: [DESCRIBE] </inputs> <task> Build a checklist grouped by metric: LCP (server response, render-blocking resources, image optimization, preloading), INP (JS execution, main-thread work, input handlers), and CLS (dimensioned media, font loading, dynamic inserts). Add a Loading Strategy section (caching, CDN, lazy-loading, code-splitting). Each item states the fix and its expected impact. </task> <constraints> - Order items within each metric by likely impact. - Name concrete techniques, not "make it faster". - Use markdown checkboxes grouped by metric with an impact note per item. </constraints> <format> Return the checklist as a markdown artifact grouped by metric, then a short note on the top three fixes that usually move the score the most. </format>
Builds a Core Web Vitals and page-speed checklist grouped by LCP, INP, and CLS, ready to use.
Pro tip: Paste your current LCP/INP/CLS numbers so Claude prioritizes the checklist around your worst-performing metric.
Content SEO Audit Checklist
20/30You are a content strategist who audits an existing content library for SEO performance. <context> I need a content SEO audit checklist as a self-contained artifact to evaluate my existing pages and decide what to keep, update, merge, or prune, so my content library earns its rankings. </context> <inputs> - Number of pages/posts: [N] - Main topics/clusters: [LIST] - Analytics access: [GSC, GA4, ETC] - Business goal of content: [TRAFFIC / LEADS / AUTHORITY] - Oldest content age: [IF KNOWN] </inputs> <task> Build a checklist with sections: Inventory & Data Pull (traffic, rankings, conversions per page), Performance Triage (classify each page as keep/update/merge/prune), Content Quality Checks (intent match, depth, freshness, E-E-A-T signals), Cannibalization & Overlap, and an Action Plan template. Include the decision criteria for each triage bucket. </task> <constraints> - Provide clear thresholds for the keep/update/merge/prune decision. - Include a keyword-cannibalization detection step. - Use markdown checkboxes plus a small triage decision table. </constraints> <format> Return the checklist as a markdown artifact with sections and a triage decision table, then a short note on how to prioritize updates for the fastest traffic recovery. </format>
Creates a content SEO audit checklist with keep/update/merge/prune triage criteria, ready to use.
Pro tip: State your content's business goal (leads vs. traffic) so Claude's triage criteria weight conversions, not just pageviews.
Event Planning
5 promptsConference / Event Planning Master Checklist
21/30You are a professional event producer who runs multi-track conferences. <context> I need a master event-planning checklist as a self-contained artifact covering the full timeline from initial planning to post-event wrap, so nothing falls through the cracks. </context> <inputs> - Event type and size: [E.G. 200-PERSON CONFERENCE] - Date and venue status: [DATE, BOOKED OR NOT] - Budget range: [AMOUNT] - Format: [IN-PERSON / HYBRID / VIRTUAL] - Team and vendors available: [ROLES] </inputs> <task> Build a phased checklist: 3+ Months Out (venue, budget, speakers, sponsors), 1-2 Months Out (marketing, registration, catering, AV), 2 Weeks Out (run-of-show, staffing, materials), Week Of (confirmations, rehearsal), Event Day, and Post-Event (feedback, thank-yous, reconciliation). Each item is a checkbox with an owner and a rough cost/deadline flag where relevant. </task> <constraints> - Sequence tasks by lead time so bookings happen before they sell out. - Include a budget-tracking and a contingency/backup-plan item. - Use markdown checkboxes grouped by timeline phase. </constraints> <format> Return the checklist as a markdown artifact grouped by timeline phase, then a short note on how to compress it for a 4-week planning window. </format>
Produces a full-timeline conference planning checklist from booking to wrap-up, ready to use.
Pro tip: Tell Claude your hard budget cap and it will flag the line items to lock early before prices climb toward the date.
Webinar Production Checklist
22/30You are a webinar producer who runs polished live online events. <context> I need a webinar production checklist as a self-contained artifact covering promotion, tech setup, the live show, and follow-up, so the broadcast is smooth and attendance converts. </context> <inputs> - Webinar topic and goal: [TOPIC, GOAL] - Date, time, timezone: [DETAILS] - Platform: [ZOOM, RIVERSIDE, ETC] - Speakers/hosts: [ROLES] - Promotion channels: [EMAIL, SOCIAL, PARTNERS] </inputs> <task> Build a checklist with phases: Promotion & Registration (landing page, emails, reminders), Content Prep (slides, script, Q&A plan, polls), Tech Rehearsal (audio, video, screen share, backup), Live Run-of-Show (intro, segments, engagement, CTA), and Follow-Up (recording, replay email, lead handoff). Each item is a checkbox with timing and owner. </task> <constraints> - Include reminder-email timing (e.g. 1 day, 1 hour before) and a tech-failure backup plan. - Every live item has a time cue. - Use markdown checkboxes grouped by phase. </constraints> <format> Return the checklist as a markdown artifact grouped by phase, then a short note on the reminder sequence that most improves live show-up rate. </format>
Builds a webinar production checklist across promotion, tech, live show, and follow-up, ready to use.
Pro tip: Give Claude your registration-to-attendance goal and it will tune the reminder cadence to lift live show-up rate.
Wedding Planning Checklist
23/30You are an experienced wedding planner who keeps couples calm and on schedule. <context> I need a wedding planning checklist as a self-contained artifact organized as a countdown from engagement to the big day, so we book the right things at the right time and stay on budget. </context> <inputs> - Wedding date: [DATE] - Guest count estimate: [N] - Budget range: [AMOUNT] - Style/vibe: [E.G. RUSTIC, BLACK-TIE] - Must-haves vs. nice-to-haves: [LIST] </inputs> <task> Build a countdown checklist: 12+ Months (venue, budget, guest list, key vendors), 9 Months (attire, invitations, catering), 6 Months (details, registry), 3 Months (finalize numbers, timeline), 1 Month (confirmations, seating), Week Of, and Day-Of timeline. Each item is a checkbox with a budget or vendor tag where relevant, and note the deposits/deadlines that lock things in. </task> <constraints> - Sequence by how far in advance vendors typically book out. - Include a running budget-tracker reminder and a contingency item. - Use markdown checkboxes grouped by countdown phase. </constraints> <format> Return the checklist as a markdown artifact grouped by countdown phase, then a short note on how to adapt it if the timeline is under six months. </format>
Creates a countdown wedding planning checklist from engagement to day-of, ready to use.
Pro tip: Share your top must-have (venue or a specific vendor) so Claude front-loads booking it before dates get taken.
Corporate Offsite / Retreat Checklist
24/30You are a team operations lead who plans company offsites and retreats. <context> I need a corporate offsite planning checklist as a self-contained artifact covering logistics, agenda, and the actual team outcomes, so the trip is productive and not just an expensive vacation. </context> <inputs> - Team size and departments: [N, WHO] - Offsite goal: [STRATEGY / BONDING / PLANNING] - Duration and dates: [DAYS, DATES] - Budget per head: [AMOUNT] - Location type: [LOCAL / DESTINATION / VENUE] </inputs> <task> Build a checklist with sections: Objectives & Agenda Design (outcomes, sessions, facilitation), Logistics (travel, lodging, meals, transport), Budget & Approvals, Pre-Offsite Prep (comms, dietary/accessibility needs, materials), On-Site Run-of-Show, and Post-Offsite Follow-Through (action items, feedback). Each item is a checkbox with an owner. </task> <constraints> - Tie the agenda directly to the stated offsite goal; no filler team-building fluff. - Include accessibility and dietary-needs collection explicitly. - Use markdown checkboxes grouped by section. </constraints> <format> Return the checklist as a markdown artifact grouped by section, then a short note on how to make sure the action items survive after everyone flies home. </format>
Builds a corporate offsite checklist covering agenda, logistics, and post-event follow-through, ready to use.
Pro tip: State the one outcome the offsite must produce and Claude will design the agenda backward from it, not from activities.
Day-Of Event Run-of-Show Checklist
25/30You are an on-site event coordinator who runs the day-of timeline minute by minute. <context> I need a day-of run-of-show checklist as a self-contained artifact so the event runs on time and every crew member knows their cue, from load-in to load-out. </context> <inputs> - Event name and start/end time: [DETAILS] - Program segments: [E.G. DOORS, KEYNOTE, BREAK, PANEL] - Crew and roles: [AV, REGISTRATION, STAGE, ETC] - Venue call time / load-in: [TIME] - Key transitions to nail: [LIST] </inputs> <task> Build a minute-by-minute run-of-show as a table with columns: Time, Segment, Action/Cue, Owner, Status. Cover load-in and setup, doors and registration, each program segment with transitions, breaks, teardown, and load-out. Add a pre-doors readiness checklist and an emergency/contingency contact block. </task> <constraints> - Use real clock times based on the start time; every row has one owner. - Include AV and transition cues explicitly so handoffs are clean. - Output as a markdown table plus the pre-doors checklist. </constraints> <format> Return the run-of-show as a markdown table artifact plus a pre-doors readiness checklist, then a short note on the buffer to build in for overruns. </format>
Generates a minute-by-minute day-of event run-of-show with cues and owners, ready to use.
Pro tip: List your trickiest transition and Claude will add explicit cue rows so the crew never freezes during the handoff.
Most people use 10% of Claude. Tutorials unlock the rest.
AI Academy: 300+ hands-on tutorials on Claude, ChatGPT, Midjourney, and 50+ AI tools. New tutorials added every week.
Personal & Moving
5 promptsMoving-House Countdown Checklist
26/30You are a relocation specialist who plans stress-free house moves. <context> I need a moving-house checklist as a self-contained artifact organized as an 8-week countdown, so packing, admin, and logistics happen in the right order and nothing is forgotten on moving day. </context> <inputs> - Move date: [DATE] - Move type: [LOCAL / LONG-DISTANCE / INTERNATIONAL] - Home size: [E.G. 2-BED APARTMENT] - Movers or DIY: [HIRED MOVERS / RENTAL TRUCK] - Household: [SOLO / FAMILY / PETS] </inputs> <task> Build a countdown checklist: 8 Weeks Out (declutter, quotes, book movers), 6 Weeks (supplies, inventory, notify), 4 Weeks (start packing non-essentials, change-of-address), 2 Weeks (utilities transfer, confirm movers, medical/school records), 1 Week (essentials box, defrost, final packing), Moving Day (walk-through, meter readings, hand keys), and First Week in New Home. Include an address-change and utilities sub-list. </task> <constraints> - Sequence by lead time; put anything with a booking or notice period early. - Include a clearly labeled "essentials / first-night box" packing list. - Use markdown checkboxes grouped by countdown week. </constraints> <format> Return the checklist as a markdown artifact grouped by countdown week, then a short note on how to compress it into a two-week emergency move. </format>
Produces an 8-week moving-house countdown checklist with admin and packing sub-lists, ready to use.
Pro tip: Tell Claude if you have pets or kids and it will add the school-record, vet, and first-night-box items generic lists miss.
New Apartment Move-In Checklist
27/30You are a home-setup expert who helps people settle into a new place fast. <context> I need a move-in checklist as a self-contained artifact for the first days in a new apartment, covering inspection, essentials, setup, and admin, so the place is safe, functional, and comfortable quickly. </context> <inputs> - Apartment type: [STUDIO / 1-BED / SHARED] - Furnished or empty: [FURNISHED / UNFURNISHED] - What is already set up: [UTILITIES, INTERNET, ETC] - Budget for setup: [AMOUNT] - Priorities: [E.G. WORK-FROM-HOME READY] </inputs> <task> Build a checklist grouped into: Move-In Inspection (document condition, test fixtures, safety), Utilities & Connectivity (power, water, internet, mail), Essentials to Buy First (organized by room), Setup & Organization (kitchen, bedroom, workspace), Safety & Security (locks, detectors, emergency info), and Admin (address change, insurance, local registration). Each item is a checkbox with a priority tag. </task> <constraints> - Front-load safety and connectivity so the first night is livable. - Include a documented move-in condition step to protect the deposit. - Use markdown checkboxes grouped by section with priority tags. </constraints> <format> Return the checklist as a markdown artifact grouped by section, then a short note on which five items to knock out in the first 24 hours. </format>
Builds a new-apartment move-in checklist covering inspection, essentials, setup, and admin, ready to use.
Pro tip: Ask Claude to expand the move-in inspection into a room-by-room condition log so you have proof for your deposit.
Travel / Trip Packing Checklist
28/30You are a seasoned travel planner who packs light but never forgets anything. <context> I need a personalized trip packing and prep checklist as a self-contained artifact tailored to my trip, so I pack the right things and handle pre-departure admin. </context> <inputs> - Destination and season: [WHERE, WEATHER] - Trip length and type: [DAYS, BUSINESS / LEISURE / ADVENTURE] - Travelers: [SOLO / FAMILY / KIDS] - Baggage limit: [CARRY-ON ONLY / CHECKED] - Special needs: [MEDS, GEAR, DIETARY, PET] </inputs> <task> Build a checklist grouped into: Documents & Money (passport, visa, insurance, cards), Clothing (weather- and length-appropriate, with quantities), Toiletries & Health (meds, essentials), Electronics & Adapters, Trip-Specific Gear, and Pre-Departure Admin (check-in, holds on mail, home lock-up, itinerary shared). Tailor quantities to trip length and baggage limit. </task> <constraints> - Adjust clothing quantities to the exact trip length and climate. - If carry-on only, flag liquids and restricted items. - Use markdown checkboxes grouped by category. </constraints> <format> Return the checklist as a markdown artifact grouped by category, then a short note on what to leave behind to stay within a carry-on. </format>
Creates a trip-specific packing and pre-departure checklist tailored to destination and length, ready to use.
Pro tip: Say "carry-on only" and Claude will trim quantities and flag TSA liquid limits so you actually fit it all in one bag.
New Baby Preparation Checklist
29/30You are a parenting-prep advisor who helps expectant parents get ready calmly. <context> I need a new-baby preparation checklist as a self-contained artifact organized by trimester and the first weeks, covering essentials, home setup, admin, and hospital prep, without over-buying. </context> <inputs> - Due date: [DATE] - First baby or not: [YES/NO] - Living situation: [HOME TYPE, HELP AVAILABLE] - Budget approach: [MINIMALIST / STANDARD] - Feeding plan: [IF DECIDED] </inputs> <task> Build a checklist organized by phase: 2nd Trimester (research, registry, big items), 3rd Trimester (nursery setup, hospital bag, install car seat, birth plan), Hospital Bag (mom, baby, partner), First Weeks Essentials (feeding, sleep, diapering, health), and Admin (birth certificate, insurance, pediatrician, leave paperwork). Distinguish true essentials from optional nice-to-haves. </task> <constraints> - Clearly separate must-have essentials from optional items to avoid over-buying. - Include the safety-critical items (car seat installed, safe sleep setup) prominently. - Use markdown checkboxes grouped by phase. </constraints> <format> Return the checklist as a markdown artifact grouped by phase, then a short note on the handful of items worth buying before everything else. </format>
Produces a trimester-by-trimester new-baby prep checklist separating essentials from extras, ready to use.
Pro tip: Tell Claude your budget approach and it will mark true essentials vs. nice-to-haves so you don't over-buy on the registry.
Home Purchase / Closing Checklist
30/30You are a real-estate closing coordinator who guides buyers to the keys. <context> I need a home-buying checklist as a self-contained artifact covering the full journey from pre-approval through closing and move-in, so I do not miss a deadline that could cost me the deal. </context> <inputs> - Stage I am at: [SEARCHING / OFFER ACCEPTED / IN ESCROW] - Financing type: [MORTGAGE / CASH] - Timeline to close: [WEEKS] - Property type: [HOUSE / CONDO / CO-OP] - Professionals engaged: [AGENT, LENDER, ATTORNEY] </inputs> <task> Build a checklist with phases: Pre-Approval & Budget, House Hunting & Offer, Under Contract (inspection, appraisal, contingencies, insurance), Financing & Underwriting (documents, locking rate), Pre-Closing (title, walk-through, funds to close), and Closing & Move-In. Each item is a checkbox with a deadline flag and the responsible party. Highlight contingency-deadline items that carry financial risk if missed. </task> <constraints> - Flag every hard deadline (inspection, financing, contingency removal) explicitly. - Include a final-walk-through and "funds ready to wire" verification step. - Use markdown checkboxes grouped by phase with deadline flags. </constraints> <format> Return the checklist as a markdown artifact grouped by phase with deadline flags, then a short note on the deadlines that most often trip up first-time buyers. </format>
Builds a home purchase and closing checklist from pre-approval to keys with deadline flags, ready to use.
Pro tip: Tell Claude your stage (e.g. "in escrow") and it will trim the checklist to only the deadlines still ahead of you.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.
7-day free trial. Cancel anytime.