Code generation, debugging and documentation
83 prompts
Help me set up a scheduled job. Task: [what it does] Schedule: [e.g. every weekday at 7am in Europe/London] Environment: [Linux cron, Kubernetes CronJob, framework scheduler, cloud scheduler] Give the correct schedule expression (explain each field and the time zone), the job code skeleton, locking to prevent overlapp…
Set up reliable scheduled jobs with correct cron syntax, logging and failure alerts.
Act as a backend engineer. Stack: [details] Endpoints to protect: [list] Limits wanted: [e.g. 100 requests/minute per API key, 5 login attempts per 15 minutes per IP] Infrastructure: [single server / multiple instances / Redis available] Implement rate limiting (explain fixed window vs sliding window vs token bucket),…
Protect your API from abuse with rate limits per user, IP or API key.
Act as an Excel automation expert. Task to automate: [describe step by step] Workbook layout: [sheets, columns] Excel version: [version] Write a VBA macro with comments, error handling, and a confirmation message. Explain how to add it to the workbook, run it, and save as .xlsm. Suggest testing on a copy of the file f…
Automate repetitive Excel tasks with a commented VBA macro and instructions to run it safely.
Act as a Google Workspace automation developer. What I want to automate: [e.g. email a summary of new form responses every morning] Sheets/Docs/Calendar involved: [details] Write an Apps Script with comments, a trigger setup (time-driven or on edit), error handling, and step-by-step setup instructions including author…
Automate Google Sheets, Gmail, Calendar and Docs with Apps Script.
Act as a DevOps engineer. Stack and hosting: [details] Environments: [dev, staging, prod] Secrets used: [types, names only] Recommend: a config structure, .env usage and .env.example, validating config at startup, secret storage options for production, rotation practices, and what must never be committed to git. Inclu…
Organise configuration and secrets safely across development, staging and production.
Act as a senior iOS developer. iOS target: [version] Screen: [purpose and elements] Data: [model and source] Navigation: [details] Write a SwiftUI view with a view model (ObservableObject or @Observable), loading/error/empty states, accessibility labels, Dynamic Type support, previews, and comments.
Build a clean SwiftUI screen with state, navigation and accessibility.
Help me build this layout with CSS. Layout description: [e.g. sidebar left, cards grid that wraps, sticky header, footer at bottom] Breakpoints: [mobile/tablet/desktop behaviour] Existing HTML (optional): [paste] Give the HTML and CSS using Flexbox or Grid (explain which and why), comment each key property, and show h…
Build the layout you have in mind with modern CSS, explained property by property.
Act as a JavaScript expert. What should happen: [expected behaviour] What actually happens: [bug] Code: ```js [paste] ``` Explain the async flow step by step, identify the bug (race condition, missing await, unhandled rejection, etc.), provide fixed code, and suggest patterns to prevent it (Promise.all, AbortControlle…
Fix race conditions, unhandled promises and ordering bugs in async JavaScript.
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.
Analyse the time and space complexity of this code. ``` [paste] ``` Explain the Big-O line by line in simple terms, identify the bottleneck, describe what happens with 10× and 1000× more data, and suggest a more efficient approach if one exists, with code.
Understand your code's time and space complexity and where it will slow down at scale.
Act as a senior software architect. Project type: [web app, API, mobile app, library] Stack: [details] Team size and expected growth: [details] Features: [list] Propose a folder structure (with explanation of each folder), layering (e.g. routes, services, data access), naming conventions, where tests live, configurati…
Organise a new or growing project with a clean, scalable folder structure and conventions.
Act as a senior Next.js developer. Next.js version and router: [e.g. 15, App Router] Page: [purpose] Data source: [API/database] Styling: [Tailwind / CSS modules] Write the page using server components where appropriate, a client component for interactivity, loading and error UI, metadata for SEO, caching/revalidation…
Build a Next.js page or route with data fetching, loading and error states and SEO metadata.