21 prompts
You are a Node.js backend engineer focused on security. Requirements: [user fields, roles, routes] Database: [details] Write an Express app with: password hashing (bcrypt/argon2), login returning a short-lived access token plus refresh token handling, auth middleware, role checks, input validation, rate limiting on lo…
Build a secure Node.js/Express API with sign-up, login, protected routes and token handling.
You are an identity and security engineer. App type: [web, SPA, mobile] Providers: [Google, Microsoft, GitHub] Stack: [details] Explain the right flow (e.g. authorization code with PKCE), step by step, with a sequence diagram in Mermaid, how to handle state and nonce, token storage, account linking, logout, and common…
Plan a 'Sign in with Google/Microsoft/GitHub' flow securely, with the right OAuth/OIDC settings.
You are an HR policy writer. This is a draft to review with legal/HR professionals. Company: [size, locations] Model: [fully remote / hybrid with X office days] Key concerns: [communication, security, fairness, time zones] Draft a policy with sections: purpose and scope, eligibility, working hours and availability, co…
Draft a clear remote or hybrid work policy covering expectations, communication and equipment.
Act as a procurement specialist. What we're buying: [product/service] Vendors: [list with key details] Priorities: [cost, quality, support, security, integration, contract terms] Create a weighted scorecard, score each vendor with reasoning, list questions to ask each vendor, identify red flags, and recommend a choice…
Compare suppliers or software vendors objectively with weighted criteria.
I have a [hours]-hour layover in [airport/city]. Nationality: [country] Luggage: [checked through / carry-on] Time of day: [details] Interests: [rest, food, quick sightseeing] Tell me whether leaving the airport is realistic (and what entry rules to verify), a timed plan for both staying airside and going into the cit…
Make a long layover productive or fun, whether you stay airside or explore the city.
You are an application security engineer. Review the code below for vulnerabilities, using the OWASP Top 10 as a checklist. Stack: [language/framework] Context: [what this code does, who can access it] For each issue: severity (critical/high/medium/low), location, how it could be exploited (conceptually), and a fixed…
Review code for common vulnerabilities like injection, XSS, broken auth and insecure data handling, with fixes.
You are a senior software engineer doing a careful code review. Language/framework: [e.g. TypeScript/React, Python/Django] What this code does: [short description] Context: [production app, prototype, library] Review the code and report findings grouped by severity: Critical (bugs, security), Major (performance, desig…
Get a thorough review covering bugs, security, performance, readability and tests, with severity levels and suggested fixes.
You are a patient senior developer explaining code to a [beginner / intermediate] developer. Language/framework: [e.g. Python, JavaScript/React] Explain the code below: 1. In 2–3 sentences, what does it do overall and why would someone write it? 2. Walk through it section by section (group related lines), explaining w…
Paste any code and get a plain-English walkthrough: what it does overall, what each part does, and anything risky or unusual to watch out for.
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.