New Hire Onboarding Checklist
Onboard a new hire across accounts, training, and first-week goals.
What it adds
Build an onboarding checklist that groups setup, training, and first-week tasks with owners and progress.
What your builder is told to do
4
What your builder is told to do
4-
1
Inspect the onboarding phases, owners, and required steps in the source files.
-
2
Build grouped items for accounts, equipment, training, and goals with owner fields.
-
3
Add progress, dependent states, and reset behavior.
-
4
Provide export, copy, or save hooks where supported.
Edge cases it handles
5
Edge cases it handles
5- Keep the tool focused on one primary job. If the source asks for a suite, build the first usable tool and list the obvious follow-ups.
- Do not invent testimonials, guarantees, legal disclaimers, revenue numbers, scarcity, or unverifiable claims.
- If formulas, scoring weights, or recommendation rules are missing, create editable placeholders and call out the assumptions.
- If payment, email, analytics, CRM, or storage integrations are missing, build clear seams and document the variables or endpoints still needed.
- Match the existing app or page design system unless the user explicitly asks for a standalone visual direction.
Definition of done
5
Definition of done
5- The tool is buildable as a standalone page, lightweight SPA, embeddable widget, or cleanly integrated app screen.
- The primary input, primary output, and primary action are obvious without extra instructions.
- The implementation includes empty, loading, error, and completed states.
- Mobile, tablet, and desktop layouts are accounted for.
- The agent reports the source files used, assumptions made, and any formulas or rules that still need owner review.
Related tool files
Travel Packing Checklist
Travel Packing Checklist
Generate a packing list from trip type, length, and weather.
What it does
Build a packing checklist that generates grouped items from trip details and tracks what is packed.
How it works
- 1 Inspect any packing templates or category rules in the source files.
- 2 Create inputs for trip type, length, weather, and travelers.
- 3 Generate grouped checklist items with progress and add or remove support.
Copy the prompt
No account needed
Build this as a complete, standalone tool. Read the blueprint first and follow it exactly — make it responsive, handle empty and error states, and keep it production-ready:
https://buildthistool.com/x/travel-packing-checklist
SEO Audit Checklist
SEO Audit Checklist
Work through on-page, technical, and content SEO checks.
What it does
Build an SEO audit checklist that groups checks by area with progress and prioritized next actions.
How it works
- 1 Inspect the audit areas, checks, and priority rules in the source files.
- 2 Build grouped items for on-page, technical, content, and links with priority tags.
- 3 Add progress, notes, and a prioritized next-actions summary.
Copy the prompt
No account needed
Build this as a complete, standalone tool. Read the blueprint first and follow it exactly — make it responsive, handle empty and error states, and keep it production-ready:
https://buildthistool.com/x/seo-audit-checklist
Moving Checklist
Moving Checklist
Countdown checklist for a move, from 8 weeks out to move day.
What it does
Build a moving checklist organized by time-to-move with progress and exportable next actions.
How it works
- 1 Inspect the timeline buckets and required tasks in the source files.
- 2 Build grouped items by weeks-to-move with progress and per-item notes.
- 3 Add dependent states, reset behavior, and an overdue indicator.
Copy the prompt
No account needed
Build this as a complete, standalone tool. Read the blueprint first and follow it exactly — make it responsive, handle empty and error states, and keep it production-ready:
https://buildthistool.com/x/moving-checklist
How it works
-
1
Copy the link
Grab the Markdown blueprint URL for this tool type.
-
2
Give it to your builder
Paste it into Claude Code, Cursor, Codex, or whatever AI builder is already working in your app.
-
3
It maps, then builds
Your agent reads the blueprint first, then builds the tool into your app around the rules, audience, and stack.
Works with your stack
These blueprints are written to adapt. They tell the agent to detect your framework, match your existing design system, and use your source files instead of guessing the tool rules.
Need it tighter than that? Customize the tool file and tell it exactly which source docs and stack to use.