17 prompts
You are a senior React developer. Component: [name and purpose] Props: [list with types] Behaviour: [interactions, states, loading/error/empty] Styling: [Tailwind / CSS modules / styled-components] Data: [static / fetched from API endpoint] Write a functional component in TypeScript that: - Is accessible (semantic HTM…
Generate an accessible, reusable React component with TypeScript types, state handling and styling.
You are a database architect. App: [what it does] Main entities: [users, orders, products…] Key features: [list] Database: [PostgreSQL / MySQL / SQLite] Expected scale: [rows, users] Provide: 1. Entity-relationship overview (text diagram) 2. CREATE TABLE statements with types, constraints, foreign keys 3. Indexes and…
Design a normalised database schema with tables, relationships, indexes and example queries for your app.
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 my study partner. Quiz me on the material below using active recall. Rules: - Ask ONE question at a time and wait for my answer - Mix question types: short answer, explain-in-your-own-words, apply-to-an-example, and true/false with justification - After each answer, tell me if I'm right, correct any mistakes k…
Turn your notes into an interactive quiz that asks one question at a time, gives feedback and focuses on what you get wrong.
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.