Lust for Prompts
Coding & Development

Review this code as a senior software engineer at a top tech company (FAANG-level standards). Identify: (1) Bugs and edge cases I haven't handled, (2) Performance bottlenecks, (3) Security vulnerabilities, (4) Code smells and anti-patterns, (5) Missing error handling, (6) What would fail in production at 10x scale. For each issue: explain why it's a problem, what the impact is, and provide a corrected code snippet. Code: [PASTE YOUR CODE]

Refactor this legacy [LANGUAGE] code for modern standards. Goals: (1) Improve readability without changing behaviour, (2) Remove code duplication, (3) Add meaningful variable names, (4) Split into smaller functions, (5) Add JSDoc/docstrings, (6) Make it testable. Show me: the refactored code with comments explaining each change, what you changed and why, and what tests I should write. Original: [PASTE CODE]

Help me debug this issue. Language/Framework: [SPECIFY]. Error message: [PASTE ERROR]. What I expected to happen: [DESCRIBE]. What actually happened: [DESCRIBE]. What I've already tried: [LIST]. Code in question: [PASTE CODE]. Walk me through diagnosis step by step. Identify the root cause, not just the symptom. Then give me the fix with an explanation of why it works. Also tell me how to prevent this class of bug in future.

Design the system architecture for [FEATURE/PRODUCT]. Requirements: [LIST REQUIREMENTS]. Scale target: [USERS/REQUESTS PER DAY]. Tech stack preference: [YOUR STACK OR "RECOMMEND"]. Constraints: [BUDGET/TEAM SIZE/TIMELINE]. Give me: (1) High-level architecture diagram (describe in text/ASCII), (2) Database schema, (3) API design, (4) Key technical decisions and trade-offs, (5) What to build first vs. defer, (6) Known scaling bottlenecks to plan for.

Design a RESTful API for [FEATURE/SERVICE]. Give me: (1) Complete endpoint list with HTTP methods and paths, (2) Request/response schemas for each endpoint, (3) Authentication approach, (4) Error response format, (5) Pagination strategy, (6) Rate limiting recommendation. Follow REST best practices. Include an OpenAPI/Swagger spec snippet for the 3 most important endpoints. Explain any design decisions that aren't obvious.

Help me choose the right tech stack for [TYPE OF APP]. Context: Team of [SIZE], budget [AMOUNT], timeline [MONTHS], existing skills [LIST LANGUAGES/FRAMEWORKS TEAM KNOWS], expected scale [USERS IN YEAR 1]. Compare 3 realistic options for: frontend, backend, database, hosting, auth. For each option tell me: pros, cons, cost estimate, learning curve, and which Indian developers/companies use this stack. Give a final recommendation with clear reasoning.

Write a comprehensive test suite for this [LANGUAGE/FRAMEWORK] code. Include: (1) Unit tests for each function, (2) Edge cases and boundary conditions, (3) Error handling tests, (4) Integration tests where applicable. Use [TESTING FRAMEWORK — e.g. Jest/PyTest/JUnit]. Make tests descriptive — I should understand what's being tested from the test name alone. Cover at least 90% of branches. Code: [PASTE CODE]

Write comprehensive developer documentation for [WHAT YOU'RE DOCUMENTING — API/library/service]. Include: (1) Quick start (working example in under 5 minutes), (2) Core concepts explained simply, (3) Full API reference with parameters, return types and examples, (4) Common use cases with code samples, (5) Error reference, (6) FAQ. Audience: [SKILL LEVEL] developers. Make every code example copy-paste ready and tested.

Explain this code to [AUDIENCE — e.g. a non-technical product manager / a junior developer / a client]. Use plain language with no assumed technical knowledge. Include: what this code does in one sentence, why it exists and what problem it solves, a real-world analogy that makes it intuitive, any important limitations or things that could go wrong, and what would happen if this code was removed. Code: [PASTE CODE]