Find problems that fit your skills

Describe what you can build and what kind of work interests you. This matches on meaning, not keywords, so you will surface opportunities that never use your vocabulary — and it only returns themes that at least two people reported independently, so a match is a product rather than one person’s bad day.

Getting better results

Describe the domain, not the stack. The corpus is indexed by what is broken in someone’s job, and nobody complaining about their rota mentions React. “Scheduling and shift swaps for shift workers” beats “TypeScript, tRPC, Postgres”.
Say what you will not do. Constraints are signal: “solo, no sales calls” or “consumer only” genuinely changes the ranking.
Follow the workarounds. Once something looks interesting, open it and read what people do manually today. That is the specification.

Also available as POST /api/v1/match — see the API reference. Once you have picked one, hand it to the spec builder.