中文译文
充当一名资深提示词工程师，对下面所附的提示词进行严格且实用的质量审计。
---PROMPT START--- ${paste_prompt_here} ---PROMPT END---
从清晰度、完整性、歧义、缺失约束、薄弱指令、相互冲突的指示、上下文缺口、输出格式弱点，以及任何其他可能降低输出质量、可靠性、一致性或可用性的问题，对该提示词进行评估。根据问题对输出质量的综合影响以及失败可能性对其进行优先级排序。主要关注那些会直接或可预见地影响正确性、可靠性或可用性的问题，但如果低概率、高影响的边缘案例可能影响真实世界表现，也要纳入。将分析限制在高价值洞察上。
在第一节（Issues）中，识别最重要的问题，并清楚解释每个问题为何可能导致失败、不一致、歧义或次优输出。使用编号要点，严格按照优先级顺序呈现问题。在识别问题时要全面，但解释应仅限于理解其影响所必需的内容。
在第二节（Recommendations）中，提供具体、实用且可直接应用的改进建议。确保每条建议都明确映射到对应问题（例如，Issue 1 → Recommendation 1）。不要引入无关建议，除非它们显然能解决多个已识别问题。
在第三节（Optimized Prompt）中，将提示词重写为可投入生产使用的形式，在提高清晰度、控制力、精确性、完整性和可靠性的同时保留原始意图。结果应针对重复使用中的一致、无歧义、符合格式且可清晰测试的输出进行优化。只有在有助于提高可测试性时才包含明确的成功标准。如有必要，你可以重构提示词，但不要引入新的意图。如果缺少关键要素（如上下文、约束或输出格式），请使用清晰的占位符（如 ${insert_context_here}）明确说明。只有在为使提示词可执行而必需时才做假设；否则明确识别缺失信息。
使用且仅使用以下三个章节标题来组织回答：Issues、Recommendations 和 Optimized Prompt。
这三个必需章节标题仅使用英语。其他所有内容用土耳其语撰写。严格执行编号以及各节之间的清晰映射。避免不必要的重复。
English original
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.