Domain Name Finder
Suggest domain ideas from keywords, style, and extension.
What it adds
Build a domain finder that generates candidate names by style and flags availability via a placeholder check.
What your builder is told to do
4
What your builder is told to do
4-
1
Inspect any naming rules, extensions, or brand keywords in the source files.
-
2
Create inputs for keywords, style, length, and preferred extensions.
-
3
Generate candidate domains grouped by style with a copy control.
-
4
Add an availability-check seam and document the lookup integration still needed.
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
Font Pairing Finder
Font Pairing Finder
Suggest heading and body font pairings from a style input.
What it does
Build a font pairing finder that recommends pairings by style with a live preview and copyable stacks.
How it works
- 1 Inspect any approved font lists or style rules in the source files.
- 2 Create inputs for style, mood, and use case.
- 3 Return pairings with a live preview, contrast notes, and copyable CSS stacks.
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/font-pairing-finder
Gift Finder
Gift Finder
Recommend gifts from recipient, occasion, and budget.
What it does
Build a gift finder that narrows to a shortlist from recipient traits, occasion, and budget.
How it works
- 1 Inspect the product set, tags, and matching rules in the source files.
- 2 Create inputs for recipient, interests, occasion, and budget.
- 3 Return a ranked shortlist with why each fits and a shop CTA.
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/gift-finder
Plan Finder
Plan Finder
Return the best plan from usage and requirement inputs.
What it does
Build a plan finder that filters plans by the user's stated needs and returns the closest match.
How it works
- 1 Inspect the plans, limits, and matching rules in the source files.
- 2 Create inputs for usage, required features, and budget.
- 3 Return the best-fit plan with reasons, close alternatives, and a checkout CTA.
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/plan-finder
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.