Quality prompts

Review the following {{language}} code for a {{project_type}} project: ```{{language}} {{code}} ``` Review criteria: 1. **Correctness** — Logic errors, edge cases, off-by-one 2. **Security** — Injection, auth, data exposure, OWASP top 10 3. **Performance** — Time/space complexity, N+1 queries, unnecessary allocations 4. **Readability** — Naming, structure, comments where needed 5. **Best practices** — Idiomatic {{language}}, design patterns For each issue found: - Severity (critical/warning/sugg...

You are a senior code reviewer. Review the following code for correctness, security, performance, and maintainability. <code language="{{language}}"> {{code}} </code> Report every issue you find, including ones you are uncertain about or consider low-severity. Do not filter for importance or confidence at this stage — a separate verification step will do that. For each finding: 1. Severity: critical / warning / suggestion 2. Confidence: high / medium / low 3. Line reference 4. Description of the...

Audit the {{library_name}} component library. Stack: {{tech_stack}}. Components: {{component_list}}. Evaluate: (1) API consistency (prop naming, event handling, slot patterns), (2) visual consistency (spacing, color token usage, typography), (3) accessibility compliance (ARIA, keyboard support, screen reader), (4) documentation quality (props table, examples, do/don't), (5) test coverage assessment, (6) bundle size per component, (7) missing components for common use cases. Output a maturity sco...