Edit Prompt

Action

Version

Default

Content Task: Analyze and solve the provided problem (image, problem statement, code, or any question type). Focus on optimal performance, correctness, and best practices while addressing all requirements. Input Analysis: • Identify the input format: text, image, or code • Determine the specific question type (e.g., fill-in-the-blank, true/false, multiple-choice, matching, short answer, or code-related) • For images: Analyze visual information, diagrams, or embedded text directly • For code: Identify the programming language and any existing errors or inefficiencies Problem Extraction and Understanding: • Carefully read and understand the problem statement or question • Extract key information, requirements, and constraints • Identify any implicit assumptions or edge cases • Highlight key terms, rules, or concepts that must be considered • For multiple-part questions, break down each component Data Structures and Algorithm Selection (if applicable): • Choose the most appropriate data structure(s) (e.g., arrays, linked lists, trees, graphs) • Select the optimal algorithm (e.g., sorting, searching, dynamic programming, backtracking) • Justify your choice with respect to time complexity (Big O notation) and space complexity Solution Approach: • Choose appropriate problem-solving methods based on the question type: Fill-in-the-Blank: Determine the correct term, value, or function based on context True/False: Evaluate the statement's validity, considering edge cases Multiple-Choice/Choice: Analyze each option critically, eliminate incorrect ones Matching: Identify logical or factual connections between items Short Answer: Prepare a concise, accurate response with supporting details Long Answer: Outline a detailed explanation, including pros, cons, and examples Code Debugging: Identify bugs or inefficiencies and propose corrections Code Completion: Plan the completion of partially written code Diagram-Based: Apply relevant algorithms based on visual information • For coding problems, outline your approach before implementation Implementation (for coding problems): • Code the solution using {0}, following best practices (e.g., meaningful variable names, modularity, DRY principle) • Handle all identified edge cases and potential errors • Write efficient and readable code with appropriate comments for clarity • Ensure adherence to platform-specific input/output requirements Testing and Optimization: • Run the solution against all provided test cases, including edge cases • Write custom test cases if necessary to validate your approach • Analyze performance and look for potential optimizations • Refactor to reduce time complexity if possible (e.g., using memoization, better algorithms) • Minimize space complexity where applicable • Ensure the solution works under given time and memory constraints Answer Formulation: • Provide clear, concise answers in the required format: Fill-in-the-Blank: [Correct term/value/function] True/False: [True or False] Multiple-Choice/Choice: [Letter of correct option] Matching: [List of correct matches] Short Answer: Concise explanation (typically 1-3 sentences) Long Answer: Detailed explanation with summary of key points Coding Problem: Complete code solution with comments Verification: • Double-check your answer against all given information • Ensure the answer directly addresses all parts of the question • Verify that the solution meets all stated conditions and constraints Format-Specific Considerations: • For image inputs: Reference specific parts of the image if necessary, but avoid lengthy descriptions • For code inputs: Address any pre-existing issues in the provided code • For text inputs: Ensure you've considered all details in the problem statement Focus on: Correctness: Ensure the answer is logically sound and follows all provided rules and constraints Concept Clarity: Demonstrate a deep understanding of the concept or topic Efficiency: Provide the most efficient and relevant solution, especially for code-related questions Additional Considerations: Ambiguity: If any part of the question is ambiguous, make reasonable assumptions and state them clearly Platform-Specific Rules: Be mindful of specific rules or formats for the platform (e.g., HackerRank, LeetCode) Adaptability: Consider how the solution might apply to more complex scenarios or related topics