Explain this scientific paper to a [level] reader: research question, why it matters, method, key results, limitations and what it means in practice. Define technical terms and say how strong the evidence is. Paper: [paste abstract or text]
Results for “technical”
12 prompts
Write a documentation page for [feature/API/tool] aimed at [audience]. Include an overview, prerequisites, step-by-step setup, a code or configuration example, common errors with fixes, and related links. Use clear headings and second person. Base it on these notes: [notes].
Technical documentation page
Clear technical docs with steps, examples and troubleshooting.
You are a staff engineer experienced with legacy systems. System: [description, age, language] Pain points: [bugs, slow changes, outdated libraries] Constraints: [can't stop shipping features, limited tests] Create a plan: characterisation tests first, the strangler-fig approach, which areas to modernise first (by ris…
Modernise legacy code
Plan an incremental modernisation of old code without a risky big-bang rewrite.
You are a tech lead planning an upgrade. Current and target versions: [e.g. React 17 → 19, Python 3.8 → 3.12, Laravel 9 → 11] Codebase size and test coverage: [details] Key dependencies: [list] Create: breaking changes to check (verify against official upgrade guides), dependency compatibility plan, step-by-step upgra…
Framework upgrade migration plan
Plan a safe upgrade between major versions of a framework or language.
You are a live-streaming producer. Platform: [Instagram Live / YouTube / TikTok / LinkedIn Live] Topic: [topic] Length: [minutes] Guest (optional): [name] Goal: [engagement, sales, community] Create: 1. A title and 2 promo posts 2. Run-of-show with timings: welcome, hook, main segments, Q&A, CTA, close 3. 5 interactio…
Live stream plan
Plan an engaging live session with a run-of-show, interaction moments, promotion and replay strategy.
Explain [concept] using everyday analogies. My background: [what I already know] Audience: [me / students / customers] Give: 1. 3 different analogies from everyday life (cooking, sports, traffic, etc.) 2. For each, how it maps to the real concept 3. Where each analogy breaks down or could mislead 4. A one-sentence acc…
Explain with everyday analogies
Make abstract or technical ideas click with relatable, accurate analogies, and learn where each analogy breaks down.
You are an API technical writer. API: [name and purpose] Base URL: [url] Auth: [API key / Bearer token / OAuth] Endpoints: [method, path, what it does, parameters, request body, responses] Create: 1. An OpenAPI 3.0 YAML spec with schemas, examples and error responses 2. A getting-started guide (auth, first request wit…
API documentation in OpenAPI format
Turn your endpoints into a complete OpenAPI 3 spec plus human-friendly docs with examples.
You are a risk management consultant. Project/business: [describe] Timeline and budget: [details] Key dependencies: [suppliers, people, technology, approvals] Create a risk register table: Risk | Category (financial, operational, technical, legal, people, market) | Likelihood (1–5) | Impact (1–5) | Score | Early warni…
Risk register for a project or business
Identify, score and plan responses to the risks that could derail your project, launch or business.
You are a science communicator who explains research clearly and accurately. My background: [e.g. no science background / undergraduate in biology / practitioner] Explain the paper below: 1. One-sentence summary 2. The question the researchers asked and why it matters 3. How they studied it (methods, sample size), in…
Research paper simplifier
Understand dense academic papers fast: plain-English summary, methods, key findings, limitations and what it means in practice.
You are a technical writer for developer tools. Write a README.md for my project. Project name: [name] What it does: [description] Who it's for: [audience] Tech stack: [languages, frameworks] How to install: [steps or commands] Main features: [list] Configuration options: [env vars, config files] License: [license] Se…
README and documentation for your project
Write a clear, well-structured README with installation, usage examples, configuration and contributing guidelines.
You are a hiring manager who runs structured, fair interviews. Role: [job title and level] Key competencies to assess: [e.g. problem solving, communication, technical skill X] Interview length: [minutes] Create: 1. 8–10 questions mixing behavioural ("Tell me about a time…"), situational and role-specific questions 2.…
Interview questions with a scoring rubric
Get structured interview questions for any role, what a strong answer looks like, red flags, and a scorecard to compare candidates fairly.
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…
Turn a feature idea into a technical spec
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.