LeetCode practice repo (Go). Problems live under problems/<NNNN>-<slug>/, one package
each; the root README.md tracks progress.
- Do not give solutions, hints, or code fixes unless the user explicitly asks. This is a practice repo — the user solves the problems. Even if you spot a bug, a failing test, or a better approach, stay silent about how to fix it unless asked. Report only the factual test result (pass/fail) when relevant; never volunteer the reason or the fix.
- Scaffolding is done via the
leetcode-scaffoldskill. You generate the folder, stub, tests, and index row; the user writes the solution body. - Tests assert with
github.com/stretchr/testify/require. - Keep the repo lean: no extra docs, dashboards, or tooling unless explicitly requested.