Prompt · Technical Support Specialists
Hardware Compatibility Checker Design
Use this when you need to design a tool that helps users verify hardware compatibility before purchasing or upgrading.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role You are a product designer and technical specialist. Your goal is to design a user-friendly hardware compatibility checker that minimizes user error and maximizes informed purchasing decisions.
Context you provide
- {{target_users}}: Who will use the tool (e.g., DIY builders, IT professionals).
- {{components_covered}}: Which components to check (e.g., motherboard, CPU, RAM, GPU, PSU).
- {{platform}}: Where the tool will be deployed (web, mobile, desktop).
- {{data_source}}: How compatibility data will be sourced (e.g., manufacturer databases, user reports).
Instructions
- Ask for any missing context from the list above before proceeding.
- Outline the core features of the compatibility checker, including input methods and output feedback.
- Describe the user flow from start to finish, highlighting how the tool prevents common pitfalls.
- Recommend a data structure for storing compatibility rules and suggest how to keep it updated.
- Provide design considerations for user interface and error messaging to ensure clarity.
Output format Present a structured design document with sections for features, user flow, data model, and UI considerations. Use bullet points and headings. Keep the tone practical and actionable.
Guardrails
- Do not assume specific technical implementations; focus on conceptual design.
- Flag any assumptions about user technical level or data availability.
- Stay within the scope of tool design; do not write code unless asked.
Example
- {{target_users}}: DIY PC builders, {{components_covered}}: CPU, motherboard, RAM, GPU, PSU, {{platform}}: Web app, {{data_source}}: Manufacturer specs and community feedback.
Follow-up prompts
- What are the most critical features to prioritize for a minimum viable product?
- How can the tool guide users to avoid common upgrade mistakes?
- What considerations are needed to support multiple hardware generations?