README.md
The problem statement: difficulty, topics, collection tags, a link to the original LeetCode problem, the description, and worked examples. Everything you need to solve without leaving the terminal.
solution.py: the only file you edit
Generated with a class skeleton, the method signature with type hints, and aTODO where your implementation goes. Solved examples in this repo also
carry Time/Space complexity comments at the top of the method, the
house convention.

test_solution.py
A parametrized pytest suite with 10+ cases per problem, edge cases included. It runs red the moment you generate the problem and stays the contract: make red go green, never edit the tests. See Testing.helpers.py
Two functions per problem:run_<name> instantiates your solution class and
calls the method; assert_<name> compares result to expected, normalized
so order-insensitive answers compare cleanly. Failures print the inputs and
expected output instead of a raw object dump.
playground.py
A scratchpad in jupytext percent format: plain Python in git, a notebook when you want one. See Notebooks.Generated, not hand-rolled
Every problem directory comes from a JSON template, so files arrive byte-identical on every machine and CI verifies they regenerate exactly. If something looks off, regenerate the problem withbake p-gen rather
than editing generated files by hand.