6 prompts
You are a business continuity planner. Business: [details] Critical operations: [list] Key dependencies: [systems, suppliers, people] Create a plan covering: critical functions and recovery time targets, scenarios (IT outage, key person absence, supplier failure, office inaccessible, data loss), response steps for eac…
Prepare for disruptions like outages, staff absence or supply problems with a practical continuity plan.
You are a product marketer who uses jobs-to-be-done. Product: [details] Customer interview notes or reviews: [paste] Identify: the main job(s), functional, emotional and social dimensions, the trigger moments, alternatives they 'fired', anxieties and habits holding them back, and how to use these insights in messaging…
Uncover why customers really 'hire' your product using the jobs-to-be-done framework.
You are a senior engineer conducting a system design interview. System: [e.g. URL shortener, chat app, news feed, ride sharing] My level: [junior / mid / senior] Run the interview interactively: 1. Ask me to clarify requirements, then reveal the expected functional and non-functional requirements 2. Let me propose a h…
Practise system design questions with a guided walkthrough of requirements, architecture, scaling and trade-offs.
You are a senior React developer. Component: [name and purpose] Props: [list with types] Behaviour: [interactions, states, loading/error/empty] Styling: [Tailwind / CSS modules / styled-components] Data: [static / fetched from API endpoint] Write a functional component in TypeScript that: - Is accessible (semantic HTM…
Generate an accessible, reusable React component with TypeScript types, state handling and styling.
Refactor the code below to make it clean and maintainable, without changing its behaviour. Language: [language] Style guide or conventions: [e.g. PEP 8, Airbnb] Goals: - Clear, descriptive names - Small functions with a single responsibility - Remove duplication and dead code - Simplify nested conditions (early return…
Clean up hard-to-read code with better names, smaller functions and less duplication, without changing what it does.
You are a senior software engineer writing a technical spec. Feature idea: [describe the feature] Product context: [what the app does and who uses it] Tech stack: [e.g. Next.js, Postgres, Laravel] Constraints: [deadline, team size, things we can't change] Write a spec with: 1. Goal and success metrics 2. User stories…
Go from a one-paragraph feature idea to a developer-ready spec with user stories, data model, API endpoints, edge cases and a task breakdown.