A better starting point
for your next idea.

Review a small AI-assisted app before I share it.
App purpose: {{purpose}}
Main user flows: {{flows}}
Stack and repository notes: {{stack}}
Known issues: {{known issues}}
Make a prioritized manual test plan covering empty states, invalid inputs, failed requests, keyboard access, narrow screens and saved-data persistence. For each test, state setup, action, expected result and severity if broken. Separate confirmed defects from untested risks. Do not claim to have inspected code or executed tests unless you actually did. Finish with a short release checklist and the smallest fixes for any confirmed blockers.

Act as a Senior Data Engineer and Database Administrator. I need you to generate an optimized SQL query based on my natural language request.
Context:
Dialect: {{dialect}}
My Request: {{question}}
Database Schema:
SQL


{{schema}}


Your Task:
Please provide the solution in 3 distinct sections.
Section 1: The Optimized Query
Write the SQL query to answer my request.
Use modern SQL best practices (CTEs over subqueries where appropriate).
Use proper indentation and capitalization (e.g., SELECT, WHERE).
Handle potential edge cases (e.g., NULL values or division by zero).
Section 2: The Logic Breakdown
Briefly explain how the query works in plain English.
Explain the logic behind any Joins, Grouping, or Window Functions used.
Section 3: Performance Check
Recommend one specific Index that would make this query run faster, explaining which columns should be indexed and why.
Output everything in clean Markdown.

Preserve provided facts. Identify missing evidence and assumptions. Do not promise rankings, replies, hiring, perfect fidelity or measured performance without supporting tests.

Act as a Senior Principal Software Engineer and Architect. I am submitting a code snippet in {{language}} that needs refactoring.
My Goal: {{goal}}
The Code:


{{code}}


Your Task:
Please analyze and refactor this code in 3 distinct sections.
Section 1: The Code Review (Constructive Review)
Briefly list 3-5 critical issues in the original code regarding:
Performance: (Time/Space complexity)
Readability: (Naming conventions, structure)
Security/Best Practices: (Potential vulnerabilities or anti-patterns)
Section 2: The Refactored Solution
Rewrite the code completely.
Apply modern syntax and patterns (e.g., functional programming, strict typing).
Add robust error handling.
Include JSDoc/Docstring comments explaining complex logic.
Constraint: Supply a reviewable candidate patch and tests; do not claim production readiness without execution.
Section 3: The "Why" (Education)
Explain the specific changes you made and why they are better. Use a "Before vs. After" comparison logic to help me learn.
Output everything in clean Markdown.

Preserve provided facts. Identify missing evidence and assumptions. Do not promise rankings, replies, hiring, perfect fidelity or measured performance without supporting tests.

Turn a feature request into an implementation contract for a coding assistant.
Feature request: {{feature}}
Repository context: {{repository context}}
Constraints: {{constraints}}
Expected user behavior: {{acceptance behavior}}
Produce: objective, in-scope changes, files to inspect, unresolved questions, acceptance checks, validation commands and a rollback approach. Define observable before-and-after behavior. Do not invent file names, dependencies, credentials or test commands absent from the supplied context; mark them as inspect-first. Require the agent to preserve unrelated changes, avoid printing secrets and report actual checks performed. Ask only questions that block meaningful progress.