Remove filler and artificial wording while preserving the meaning.
Read prompt
Rewrite the following text in natural, clear Turkish: [text]. Preserve the information, names, numbers and uncertainty. Do not add unsupported claims. Remove repetitive concluding sentences, inflated adjectives and introductions that announce what the text will discuss. Prioritize concrete information the reader does not already know. Vary sentence structures. Preserve a voice suited to the type of text. Return only the edited text.
Research
Check a data file
Find gaps, inconsistencies and calculation assumptions.
Read prompt
Review this data file: [file]. First report the meaning of the columns, data types and row count. Check for missing values, duplicates and inconsistent units. Summarize findings without changing the source. Explain the formula, filters and assumptions used in any calculation. Do not convert currencies or date formats based on guesses. Provide reproducible steps and questions that require verification.
Research
Ground research in sources
Match claims to dated, accessible sources.
Read prompt
Research this question: [question]. First define its scope and the information needed for the decision. Use current primary sources. Support every significant claim with the relevant source link. Distinguish the publication date from the event date. Explain differences when sources conflict. Separate your interpretation from information stated directly in a source. Do not invent information you cannot find. Finish with a short answer and the limitations that affect the decision.
Design
Review an interface
Identify priority fixes from the actual screen.
Read prompt
Review this interface using the provided screen or running application. First identify the user’s main task. Check hierarchy, readability, spacing, keyboard use, focus visibility and mobile layout. Prioritize problems actually visible on the screen. For each issue, explain where it occurs, how it affects the task and a concrete fix. Focus on improving the existing screen without adding a new section or feature.
Development
Reproduce a bug
Find the cause before fixing the symptom.
Read prompt
Investigate this bug: [symptoms and reproduction steps]. Read the relevant code, trace the call flow and list possible causes with evidence. If possible, reproduce the bug with a small example or test. Do not change the code until the root cause is clear. Then apply the narrowest change that fixes it. Check that the bug no longer occurs and the relevant workflow works. Report the cause, the changed behavior and the limits of the test.
Development
Review a code change
Check the change’s behavior and potential bugs.
Read prompt
Review this code change. First read the relevant files and calling code. Compare the new behavior with the existing behavior. Report only concrete bugs, security issues or backward incompatibilities. For each finding, identify the file, line, triggering condition and impact on the user. Present uncertain points as questions that need verification. Order findings by severity. If you find no issues, say so clearly and state which checks you did not perform.
Replace the bracketed fields with your own information. Prompts were written by shazeus.
How do you adapt a prompt to your work?
Choose the task you want to carry out, then replace the square brackets in the text with your own context. Add the code, text or data to be reviewed; clearly state the expected output format and any constraints.
For code reviews, explain the purpose of the change and the symptoms of the problem. For research, specify your source and date requirements. Check the accuracy of the response before using it; do not include secret keys or data you do not have permission to share.