Prompt Editor

Refine, edit, and optimize your generated prompt.

Ready for your AI model

Generate three distinct and comprehensive Python coding challenges. Each challenge must focus on practical application, emphasize robust code design, and cover different core Python concepts.

For each challenge, provide the following structured details:

1.  **`Challenge Title:`** A concise, descriptive title.
2.  **`Problem Description:`** A clear and unambiguous statement of the programming task.
3.  **`Input Specification:`** Define expected input types, formats, and any valid constraints (e.g., data ranges, valid characters, list lengths). Explicitly state if multiple inputs are expected.
4.  **`Output Specification:`** Define the expected output type, format, and content for a correct solution.
5.  **`Core Requirements & Constraints:`** List specific technical requirements (e.g., 'must be O(n) time complexity', 'no external libraries', 'handle non-numeric input gracefully') and any functional constraints.
6.  **`Edge Cases to Consider:`** Detail at least two specific, non-trivial edge cases that a robust solution should explicitly handle (e.g., empty inputs, maximum/minimum values, specific error conditions).
7.  **`Recommended Best Practices:`** Specify Pythonic best practices to apply, such as type hinting (PEP 484), clear function signatures, docstrings (PEP 257), effective error handling, modularity, or algorithmic efficiency considerations.
8.  **`Example Test Case:`** Provide one distinct example input and its corresponding expected output, illustrating the problem requirements and ideally one edge case if applicable.

Metadata

Target Engine

Claude 4 Opus

Prompt Editor

Refine, edit, and optimize your generated prompt.

Ready for your AI model

Generate three distinct and comprehensive Python coding challenges. Each challenge must focus on practical application, emphasize robust code design, and cover different core Python concepts.

For each challenge, provide the following structured details:

1.  **`Challenge Title:`** A concise, descriptive title.
2.  **`Problem Description:`** A clear and unambiguous statement of the programming task.
3.  **`Input Specification:`** Define expected input types, formats, and any valid constraints (e.g., data ranges, valid characters, list lengths). Explicitly state if multiple inputs are expected.
4.  **`Output Specification:`** Define the expected output type, format, and content for a correct solution.
5.  **`Core Requirements & Constraints:`** List specific technical requirements (e.g., 'must be O(n) time complexity', 'no external libraries', 'handle non-numeric input gracefully') and any functional constraints.
6.  **`Edge Cases to Consider:`** Detail at least two specific, non-trivial edge cases that a robust solution should explicitly handle (e.g., empty inputs, maximum/minimum values, specific error conditions).
7.  **`Recommended Best Practices:`** Specify Pythonic best practices to apply, such as type hinting (PEP 484), clear function signatures, docstrings (PEP 257), effective error handling, modularity, or algorithmic efficiency considerations.
8.  **`Example Test Case:`** Provide one distinct example input and its corresponding expected output, illustrating the problem requirements and ideally one edge case if applicable.

Metadata

Target Engine

Claude 4 Opus

CatalystPrompt Studio

Prompt Editor

Metadata

CatalystPrompt Studio

Prompt Editor

Metadata