uleet2Spaced repetition for the LeetCode problems you actually want to remember.
A companion to LeetCode, not a mirror of it. You solve on leetcode.com; we decide what you re-solve, and when — on an FSRS schedule tuned for 30-minute problems.
Metadata only · FSRS scheduling
You'd recall this ~86% today
Rating — recall, not Accepted
Did the approach come back to you unaided? Leaning on the editorial counts as a Lapse.
How it works
Two steps, one loop: track it, then re-solve it.
Paste a link. Keep the metadata, never the statement.
Drop any LeetCode URL. We pull the title, difficulty, and tags into a Card — the problem statement stays on leetcode.com, where you solve it.
LeetCode link or slug
Fetched — metadata only
Title, difficulty, and tags — never the statement. You always solve on leetcode.com.
Cards come due on an FSRS schedule.
The scheduler runs server-side and picks what's slipping. You rate how well the approach came back unaided — not whether it was Accepted. Editorial-then-passing is a Lapse.
You'd recall this ~86% today
Rating — recall, not Accepted
Did the approach come back to you unaided? Leaning on the editorial counts as a Lapse.
Why it's different
Built to measure what you can retrieve, not what got Accepted.
Recall, not green checkmarks
A Rating measures unaided retrieval. Look up the editorial then pass, and it's logged as a Lapse — because that's what your memory did.
Metadata only
Title, difficulty, tags, slug — that's all we store. Statements are never copied here; every Card deep-links back to leetcode.com.
A companion, not a mirror
You keep solving on LeetCode. We decide what you re-solve, and when.
Stop re-forgetting the problems you already solved.
Sign in with GitHub and add your first problem in under a minute.
Not affiliated with, endorsed by, or sponsored by LeetCode. LeetCode is a trademark of its respective owner. Problem statements are never stored here — every problem links out to leetcode.com.