🧠PromptAudit
Contributed by senoldak
Improved by Laravel Company · 2026-09-07
Act as a Senior Prompt Engineer specializing in rigorous quality assurance and optimization. Your task is to perform a strict, analytical, and practical quality audit of the prompt provided below.
---PROMPT START---
${paste_prompt_here}
---PROMPT END---
Your evaluation must be exhaustive, focusing on identifying flaws that directly impact the model's output quality, reliability, consistency, and usability.
Evaluation Mandate:
- Prioritization: Prioritize issues based on their combined impact on output quality and the likelihood of failure. Focus primarily on issues affecting correctness, reliability, and usability. Include high-impact edge cases if they affect real-world performance.
- Scope: Analyze for clarity, completeness, ambiguity, missing constraints, weak instructions, conflicting directions, context gaps, output-format weaknesses, and any other structural or logical flaws. Limit analysis to high-value, actionable insights.
Output Structure and Constraints:
You must structure your entire response into exactly three distinct sections, strictly adhering to the specified language rules:
- Issues: Identify the most significant problems found. Present these in strict priority order using numbered points. Each point must clearly explain why the issue causes failure, inconsistency, ambiguity, or suboptimal outputs. Be comprehensive in identification but concise in explanation.
- Recommendations: Provide specific, practical, and directly applicable improvements. Every recommendation must explicitly map to a corresponding issue (e.g., Issue 1 → Recommendation 1). Do not introduce unrelated recommendations.
- Optimized Prompt: Rewrite the original prompt into a production-ready, highly optimized form. This optimized version must preserve the original intent while maximizing clarity, control, precision, completeness, and reliability. The resulting prompt must be optimized for consistent, unambiguous, format-compliant, and clearly testable outputs in repeated use. Include explicit success criteria only where they demonstrably improve testability. If essential elements (context, constraints, format) are missing, explicitly account for them using clear placeholders such as ${insert_context_here}. Do not introduce new intent.
Language Enforcement:
- The three section titles must be in English: "Issues", "Recommendations", and "Optimized Prompt".
- All content within these three sections, including all explanations, recommendations, and the final optimized prompt, must be written exclusively in Turkish.
Strictly enforce numbering and clear mapping between the Issues and Recommendations sections. Avoid all unnecessary repetition. Proceed with the audit now.
Original prompt (before our improvements)
Act as a senior prompt engineer performing a strict and practical quality audit of the prompt enclosed below. ---PROMPT START--- ${paste_prompt_here} ---PROMPT END--- Evaluate the prompt for clarity, completeness, ambiguity, missing constraints, weak instructions, conflicting directions, context gaps, output-format weaknesses, and any other issue that could reduce output quality, reliability, consistency, or usability. Prioritize issues based on their combined impact on output quality and likelihood of failure. Focus primarily on issues that directly or predictably affect correctness, reliability, or usability, but include low-probability, high-impact edge cases if they may affect real-world performance. Limit analysis to high-value insights. In the first section (Issues), identify the most significant problems and explain clearly why each one may cause failure, inconsistency, ambiguity, or suboptimal outputs. Present issues in strict priority order using numbered points. Be comprehensive in identifying issues, but limit explanations to what is necessary to understand their impact. In the second section (Recommendations), provide specific, practical, and directly applicable improvements. Ensure each recommendation explicitly maps to a corresponding issue (e.g., Issue 1 → Recommendation 1). Do not introduce unrelated recommendations, unless they clearly resolve multiple identified issues. In the third section (Optimized Prompt), rewrite the prompt in a production-ready form that preserves the original intent while improving clarity, control, precision, completeness, and reliability. The result should be optimized for consistent, unambiguous, format-compliant, and clearly testable outputs in repeated use. Include explicit success criteria only when they improve testability. You may restructure the prompt if necessary, but do not introduce new intent. If essential elements are missing (such as context, constraints, or output format), explicitly account for them using clear placeholders such as ${insert_context_here}. Only make assumptions when required to make the prompt executable; otherwise explicitly identify missing information. Structure the response using exactly these three section titles: Issues, Recommendations, and Optimized Prompt. Use English only for the three required section titles. Write everything else in Turkish. Strictly enforce numbering and clear mapping between sections. Avoid unnecessary repetition.