The latest articles on DEV Community by Filza Rahman (@filza_rahman). https://dev.to/filza_rahman https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4006739%2F71f963a1-a0bf-4fd0-bca5-d0452f53722f.png https://dev.to/filza_rahman en Filza Rahman Sun, 28 Jun 2026 16:42:38 +0000 https://dev.to/filza_rahman/i-built-an-ai-tool-that-rewrites-one-idea-for-twitter-linkedin-and-reddit-for-the-h0hackathon-1c60 https://dev.to/filza_rahman/i-built-an-ai-tool-that-rewrites-one-idea-for-twitter-linkedin-and-reddit-for-the-h0hackathon-1c60 <p>I created this piece for the purposes of entering the AWS x Vercel H0 Hackathon. #H0Hackathon</p> <h2> What I built </h2> <p>I built Cast Wide, a tool that takes one idea and rewrites it for different platforms like Twitter, LinkedIn, and Reddit.</p> <p>The important part is that it does not just paraphrase. It actually changes the structure, tone, and writing style so the content feels natural on each platform.</p> <p>For example:</p> <ul> <li>LinkedIn output is more structured and professional</li> <li>Twitter output is short and direct</li> <li>Reddit output is more conversational and context-heavy</li> </ul> <p>You enter one idea and get three different versions that are ready to post.</p> <h2> How it works </h2> <p>The system is built with Next.js and deployed on Vercel.</p> <p>When a user submits an idea, the backend API does three things:</p> <p>First, it takes the input idea and creates three separate prompts, one for each platform.</p> <p>Second, it sends all three requests to Groq at the same time using Promise.all so nothing runs one after another.</p> <p>Third, it collects all responses and sends them back to the frontend in one response.</p> <p>This keeps the experience fast even though we are generating three full outputs.</p> <h2> Data storage </h2> <p>Every generation is saved in AWS DynamoDB.</p> <p>Each record stores:</p> <ul> <li>the original idea</li> <li>selected platforms</li> <li>generated outputs</li> <li>timestamp and user id</li> </ul> <p>The table uses userId as the partition key and createdAt as the sort key. This makes it easy to fetch a user’s history in order without complex queries.</p> <h2> What I learned </h2> <p>The hardest part was not the UI or the API calls. It was making sure each platform output actually felt different.</p> <p>At first, the model kept giving similar answers with small wording changes. The fix was fully separating prompts per platform and removing shared instructions that caused overlap.</p> <p>Once I did that, the outputs became much more distinct and useful.</p> <h2> Built for </h2> <p>AWS x Vercel H0 Hackathon<br> This project was built solo.<br> Try it out: <a href="https://cast-wide.vercel.app/" rel="noopener noreferrer">https://cast-wide.vercel.app/</a></p> <h1> H0Hackathon </h1> aws dynamodb webdev