Search problems

Find a problem by LeetCode number, title, topic or statement text.

About

Flashcards for the LeetCode problems Google asked in the last six months. Read the problem, name its topics, then check the approach.

How a card works

Pick the topics you think the problem uses, open the hint if you are stuck, then show the answer. The card scores your guess against LeetCode's tags and shows a short approach. Grade yourself Visit again, Got it or Visit less often; the grade decides when the card returns and which list it joins.

Enter
Show the answer
H
Show the hint (costs a quarter of the topic score)
S
Skip the card for an hour
1
Visit again: back in 10 minutes
2
Got it: next box (1, 3, 7, 16, 35, 90 days)
3
Visit less often: two boxes up, double wait
B
Back to the previous card
← →
Turn the pages of a long statement
/ or ⌘K
Search by number, title, topic or text

Scoring

Each graded card scores half its topic guess (F1 against the tags, less a quarter per hint) and half your grade. Mastery fades with time since the last review. Readiness weights mastery by how often Google asks each problem.

Approaches and hints

Claude wrote every approach and hint in ASD-STE100 Simplified Technical English. Claude agents reviewed each approach against the problem and the doocs/leetcode reference solution. Codex CLI gave an independent second opinion on every approach and most hints; a separate Claude reviewer covered the hints Codex could not reach. Every disagreement was settled by hand. Hints never name the technique you are guessing. They can still be wrong; check the LeetCode editorial when something looks off.

API

The app serves JSON under /api: GET /api/search?q=, GET /api/problems, GET /api/problems/:slug, GET /api/deck, POST /api/attempts, DELETE /api/progress and GET /api/report.

Sources

Problem list, frequency and topics: liquidslr/leetcode-company-wise-problems (Google, six months). Statements: doocs/leetcode, CC BY-SA 4.0. Premium statements are not included.