Problem Finder¶

Use this page when you want one searchable view across both:

You can filter by topic, difficulty, source, bucket, and content type without hopping between multiple index pages.

If you want the fastest way to narrow a practice set, start here first. Use the static indexes afterward when you want a full inventory view.

This page is best when you treat it like a practice control panel, not just a search box:

Status is the repo-note training log: todo, attempted, solved, reviewed
Kind splits internal notes from fresh external follow-up
session presets are meant to answer what do I do right now?, not only what exists?
Session size turns a long filtered list into one concrete queue for the current block
Queue board tells you whether you should resume, review, or leave the repo for fresh reps

Best Use Cases¶

Use this page when:

you know the weak topic but not the next good problem
you want to build a short ladder for one subtopic
a mixed round or contest exposed a weak slot and you want the next follow-up set quickly
you want to assemble a short Codeforces-style rep block by filtering Source = Codeforces and then jumping into the right playbook or drill
you want to resume attempted notes or build a light review queue without scanning the whole repo

Do not stay here forever. After you narrow the list, jump into a real workflow.

If you found...	Go next
one weak subtopic	Practice hub or the corresponding ladder
one weak `Codeforces` round skill such as shipping, anti-hack, or upsolve discipline	Codeforces Playbook or Codeforces Short Round 01
one weak contest skill	Contest Playbooks
one weak retrieval family	Notebook
one weak implementation family	Build Kit

Use repo-note statuses consistently so this page becomes a real training system:

todo: selected, but not honestly attempted yet
attempted: you tried it and want a clean return path
solved: you finished it once, but it is still live material for review
reviewed: you reopened it deliberately and no longer need it in the first review queue

External problems do not use repo-note status. Treat them as fresh follow-up reps after the topic is already mostly trusted.

These presets are meant to answer common training questions fast. Use them first, then narrow by topic or difficulty.

Problem	Topic	Kind	Status	Difficulty	Source	Bucket	Links