## Build & Development Commands
Alway Suggest standard project layout (src/, tests/, README.md) if the project grows.
## Testing Guidelines
Cover normal, edge, and failure cases.
Avoid capturing errors inside the code unless specifically instructed; allow exceptions to propagate during testing.
Target at least functional correctness, with a focus on early bug detection.
## Code Style & Guidelines
Follow PEP-8 compliance
Maintain consistent import ordering: standard library, third-party, local.
Avoid redundant or duplicate methods; reuse or refactor if similar functionality exists.
Structure code into small, focused functions (less than 50 lines when possible).
Use clear, descriptive, professional names for all identifiers.
Use immutable types (e.g., tuples) when data does not need mutation.
Prefer context managers (with statements) for file or resource handling.
## Documentation Guidelines
Provide structured docstrings for all public classes, methods, and modules following Google style.
Each function docstring must explain the purpose, arguments, return type, and exceptions raised.
Class docstrings must describe responsibilities and usage.
Module-level docstrings should describe the file’s overall purpose if non-trivial.
Write only necessary inline comments; avoid redundant comments.
Mark unfinished functions clearly using NotImplementedError.