How we pick what goes on this site

Builds

A build has to exist. Public URL, repo, or a demo in the post. Launch threads with a waitlist and a mockup stay off the list. We write our own title and one-line description; the post itself is embedded from X so edits and deletions follow the original. When a model drop like Jev, Muse, Fable 5.1, Mythos, Gemini 3.7 or Grok Bot ships, those builds also live on a dedicated updates page. Jev has its own URL at /jev. Muse has its own URL at /muse. The pay-to-rank wave after outbid.lol has its own list at /outbid.

Featured builds are the ones we would send a friend tonight. Everyone else is still curated, just not on the rail.

Jobs

We prefer first-party hiring posts: a founder, an engineer on the team, or a company account. Aggregator accounts get through when the company and the role are specific. We skip “DM me for 50 jobs” and roles with no company.

Each role has its own page so search engines can treat it as a posting, not just a card in a grid. Apply still happens on the original post or the link in that post.

Reads

Some posts are not a product and not a job. They are a thread someone actually finished: an essay, a deep dive, a story. Those live on /reads. First-party writing only. We skip recaps of someone else’s essay, launch threads (those are builds), and hiring (those are jobs).

For agents

Start at /llms.txt. JSON is at /openapi.json. Send Accept: text/markdown or append .md. Full notes: Best X Builds developer resources.

Removals

If we listed your work and you want it gone, email polostudio.brand@gmail.com. We delete the entry and redeploy. Same if a post is deleted or protected: the embed falls back to a plain link, and we will remove the row if you ask.