What it does Plain Rules Reader takes a competition or program rules page and answers four questions in short plain sentences: what it is, when it is due, whether it is free or carries a fee, and who can enter. You give it a web address, a saved page, or pasted text, and it reads the whole page and prints the four answers, quoting the page's own words as evidence. When an answer is not in the page, it says so plainly. It never guesses.
Who it is for I am legally blind. I work by voice. Every door I enter starts with a rules page, and a rules page is a long, dense document to listen to end to end. This tool answers the four questions I ask of every door, in seconds, in words I can hear and act on. It is for anyone who works by voice, or who has ever opened a rules page and wished it would just say the four things that matter.
What I learned I plan first. This build ran the full path: a scope, a product requirements document, and a technical spec, all written and approved before any code existed. I built by voice with a coding agent, the way I build everything: I set the concept and the rules, and I approved each step while the code was written and tested against real rules pages. The clearest lesson is an old one from my own work: a tool earns trust by saying what it does not know. This reader caught a real $25 entry fee hiding on a page that also advertises a $15,000 prize, and it says "I could not find it in this page" instead of inventing an answer. That honesty is the feature.
Log in or sign up for Devpost to join the conversation.