6 prompts
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…
Plan a safe upgrade between major versions of a framework or language.
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.
Act as a backend developer. Framework/tool: [Laravel, Django, Rails, Prisma, Alembic, raw SQL] Database: [PostgreSQL/MySQL] Change needed: [e.g. add column, rename table, split a field] Table size: [rows] Write the up and down migration, any data backfill, how to deploy it safely without downtime (e.g. expand-and-cont…
Create safe, reversible migrations for schema changes, including data backfills.
Explain this error in plain English and help me fix it. Language/framework: [e.g. Python 3.12 / Node 20 / Laravel] What I was doing: [action] Error: ``` [paste error and stack trace] ``` Relevant code: ``` [paste code] ``` Please give: 1. What the error means 2. The most likely cause (and other possible causes) 3. The…
Paste a confusing error or stack trace and get a plain-English explanation, the likely cause and a fix.
Act as a senior backend developer. Framework: [e.g. Express, FastAPI, Laravel, Django REST, Spring Boot] Database/ORM: [e.g. PostgreSQL + Prisma] Endpoint: [METHOD /path] What it does: [description] Request body/params: [fields and rules] Auth: [public / logged-in user / admin] Write: 1. The route/controller code 2. I…
Generate a production-ready API endpoint with input validation, error handling, status codes and tests in your framework.
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.