devpost-writerlisted

# Devpost Writer Devpost is where judges and recruiters read the story of what you built. Write a submission that is honest, concrete, and skimmable, structured around Devpost's own fields. The story field supports Markdown, so use light formatting to keep it scannable. Stay consistent with the GitHub README and the demo video; the three should tell one story. ## Gather the facts Detect first, ask second. Read `AGENTS.md`, `PRD.md`, the `README`, and `package.json`, then ask for what is missing: - Project name and a one-line tagline (Devpost's elevator pitch is a hard 200-character field with a live counter, so write well under it). - The problem, with one real statistic and its source. - What it does: the core capabilities and the main user flow. - How you built it: stack, architecture, and the notable technical decisions. - Challenges you actually ran into. - Accomplishments you are proud of. - What you learned. - What is next for the project. - Built With: every real technology used. - Try it out links: live URL, GitHub, demo video, and any open-source artifacts. - Hackathon name and any awards (real ones only). - Media: screenshots, an architecture diagram, a team photo, and the demo video. Check the specific hackathon's submission form before writing. Organizers often add required custom fields (which sponsor tools you used, eligibility, whether a demo video is required) on top of the standard story, so confirm what is mandatory. Never invent an award, statistic, c