179 prompts
You are a performance-focused backend engineer. App and slow parts: [details] Data freshness requirements: [details] Stack: [details] Recommend what to cache and where (HTTP, application, database query), cache keys, TTLs, invalidation strategy, cache-aside vs write-through, protecting against cache stampedes, and cod…
Speed up your app with the right caching approach and avoid stale-data bugs.
You are a Kubernetes engineer. App: [container image, port, env vars (names), resources] Requirements: [replicas, health checks, scaling, ingress, persistent storage] Write Deployment, Service, Ingress, ConfigMap/Secret references and HorizontalPodAutoscaler manifests, with comments explaining every field. Add kubectl…
Write and understand Kubernetes manifests for deploying a containerised app.
Turn this code into documentation. Code: ``` [paste] ``` Provide: a plain-English step-by-step description, a Mermaid flowchart (or sequence diagram if it involves multiple services), the inputs and outputs, and any edge cases visible in the logic.
Visualise how a function or process works with a Mermaid flowchart and plain-English steps.
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.
Act as a senior Laravel developer. Laravel version: [version] Resource: [name and fields with types/rules] Relationships: [details] UI: [Blade / Inertia / API only] Generate: migration, model with fillable and casts, form request validation, resource controller, routes, policy for authorisation, views or API resources…
Generate a complete Laravel CRUD feature: migration, model, controller, routes, validation and views.
You are a senior engineer onboarding me to a codebase. Project description: [what it does] Folder structure: [paste tree] Key files (paste the most important ones): [paste] Explain: the overall architecture, how a typical request/action flows through the code, the role of each main folder, important patterns and conve…
Get oriented in a new repository: architecture, key files, data flow and where to start.
Act as a senior product manager. Feature: [name] Problem and evidence: [details] Target users: [who] Goals: [outcomes] Write a PRD: background, problem statement, goals and non-goals, user stories with acceptance criteria, functional requirements, UX notes, edge cases, analytics/success metrics, launch plan, and open…
Write a clear PRD with problem, goals, user stories, requirements and success metrics.
You are a business adviser (not a lawyer). Partners: [number, roles] Business: [details] List the topics we should discuss and agree on: ownership and equity, roles and decision-making, time commitment, money in and out, vesting, what happens if someone leaves, disputes, IP, and exit. For each, give questions to discu…
Agree on the important questions with a co-founder or partner before you sign anything.
You are a small business adviser. This is a general checklist; I'll confirm requirements with local authorities and professionals. Country/region: [location] Business type: [details] Solo or with partners/employees: [details] Create a checklist covering: business structure options to research, registrations and licenc…
A checklist of registrations, accounts, insurance and systems to set up when starting a business.
Act as an account executive. Prospect: [company, contacts and roles] What they cared about in the demo: [notes] Next step agreed: [details] Write a 4-email follow-up sequence over 2 weeks: recap with value summary, a relevant case study, answers to open questions/business case help, and a respectful check-in. Each und…
Keep deals moving after a demo with helpful, personalised follow-ups.
Act as a sales operations manager. Sales motion: [inbound/outbound, deal size, cycle length] CRM: [tool] Design 6–8 pipeline stages with: definition, entry criteria, exit criteria, required fields, typical probability, and actions at each stage. Add rules for stale deals and a weekly pipeline review agenda.
Define clear pipeline stages with entry and exit criteria so forecasts are reliable.