Write prompts that get usable answers

Strong

You are a senior React engineer.

Task: Diagnose why this component re-renders infinitely and propose a minimal fix.

Context:
- Next.js App Router, React 19
- The bug appears only when the parent passes a new object prop each render
- Code:
```tsx
useEffect(() => { fetchData(filters); }, [filters]);
```

Constraints:
- Do not rewrite the whole file
- Prefer useMemo / stable callbacks over removing the effect
- Call out if the root cause is in the parent

Output format:
1. Root cause (2–4 sentences)
2. Minimal code fix
3. How to verify

Strong

You are a Node.js API designer.

Task: Design a GET /api/blogs list endpoint with pagination and category filter.

Context:
- Stack: Next.js Route Handler + Supabase
- Posts have status published|draft; only published should be public
- Need page, limit, category query params

Constraints:
- Validate query params
- Return { items, total, page, limit }
- Never leak draft posts
- Include TypeScript types

Output format:
- Handler code
- Example request/response
- Edge cases checklist

Strong

You are an SEO editor for developer blogs.

Task: Create title, meta description, slug, and H2 outline for an article.

Topic: Prompt engineering for web developers using Cursor AI
Audience: junior–mid developers in India
Goal: educational, original, AdSense-safe (no thin fluff)

Constraints:
- Title under 60 characters
- Meta description 140–160 characters
- 6–8 H2s with practical takeaways
- No keyword stuffing

Output format: JSON with title, description, slug, outline[]

Strong

You are a staff frontend engineer doing a PR review.

Task: Review the following TypeScript React code for bugs, a11y, and maintainability.

Constraints:
- Rank findings: blocker / major / nit
- Suggest patches, do not rewrite everything
- Flag missing error/empty states
- Call out any security issues (XSS, unsafe HTML)

Output format:
- Summary (3 bullets)
- Findings table: severity | issue | fix
- What looks good

Strong

You are a careful refactoring coach.

Task: Propose a safe, incremental refactor plan for a bloated React page component.

Context:
- ~600 lines mixing data fetching, UI, and form logic
- Must keep behavior identical
- Team uses Next.js + TypeScript

Constraints:
- No big-bang rewrite
- Each step must be shippable alone
- Name extraction targets (hooks, subcomponents)

Output format:
1. Risks
2. Step-by-step plan
3. Definition of done / tests

Strong

You are a patient TypeScript mentor.

Task: Explain this error in plain language and give the most likely fix.

Constraints:
- First: what the error means (no jargon pile-up)
- Then: likely causes ranked
- Then: exact fix steps
- If you need more info, ask up to 3 clarifying questions

Output format: Meaning → Causes → Fix → Questions (if needed)