got feedback that the readme sounded too AI-generated. stripped it down, rewrote it in first person, added a screenshot, trimmed features to 6 bullets. removed the corporate FAQ, the exhaustive tech stack list, everything that felt like a template. readme now sounds like i actually wrote it instead of a marketing team approving it. added a “how it works” section that tells the real build story instead of listing libraries. shipped it.

Devlog — Killed the Grok API Dependency

clarification questions were broken. Grok API wasn’t recognizing any model names (grok-2, grok-beta, grok — all failed). spent 15 minutes debugging dead ends.

gave up on the api. switched to hardcoded template questions instead. built question templates for each category: research gets different questions than business, different from writing, etc.

now when user hits execute → instant questions pop up → no api calls, no latency, no failures. just works.

same feature. actually reliable. 🚀

OneShot Dashboard Redesign

Spent the week tearing down the OneShot dashboard and rebuilding it with a clean black/white aesthetic. Text was disappearing, colors were fighting each other, and the whole thing felt half-baked.

Went through five pages and standardized the color system: solid white for primary text, opacity variants for secondary, and proper contrast everywhere. Same features, completely different vibe.

The real win? Design isn’t decoration. When a page is polished, users assume the engineering is solid. Now it actually looks like I care about the details.

Ship first, perfect later.

I improved the UI to make the project look more polished and intentional, with cleaner spacing, better visual hierarchy, and a smoother overall experience. I also rewrote the README so it felt more human and easier to understand, instead of sounding like a wall of technical notes. On top of that, I added a few new features that make the app feel more complete, more useful, and closer to something people would actually want to keep using.

built an AI execution engine. you describe what you need, it gives you professional results in seconds. rewrote the README to sound human (last one looked AI-generated). fixed UI readability, added progress bars, implemented retry logic for API stability. it’s live at oneshot-chi-nine.vercel.app and actually works. and my vercel kept deploying my old deployments so fixing that took me a long time i also added a progress bar feature so users dont get stuck on the screen showing nothing and yea some of the previous buttons weren’t working or were glitched so i fixed those too.

added supabase integration so tasks actually persist. implemented rate limiting (5 req/min per IP) to prevent abuse. built out an 8-template system with optimized prompts for common workflows (business plans, landing pages, marketing strategies, etc). added keyboard shortcuts (Cmd+K to open quick task search) because power users deserve fast access. implemented result modal for viewing full results without scrolling. settings now persist to localStorage so user preferences stick around. updated all dashboard pages to pull real data from the database instead of hardcoded samples. everything still works without a database configured, it just gracefully degrades.the app went from “works but doesn’t persist anything” to “production-grade SaaS with templates, shortcuts, and data persistence.” still under 10kb of production bundle js. no bloat. everything has a reason for existing.

spent the session debugging task execution flow - users were getting stuck on the “executing” page. turned out to be a routing issue after the api call completed. fixed the navigation and now tasks flow through smoothly from submission to results. also deployed the whole thing to vercel so it’s actually live and working with real results. copy and download buttons are fully functional. ready for people to start using it.

okay so we shipped the whole dashboard. like actually shipped it. all 7 pages, interactive examples modal, task execution timeline, templates, the whole thing. UI is clean and professional, no jank.built it on next.js 15, deployed on vercel, live right now at oneshot-chi-nine.vercel.app. github repo is up too: github.com/nadellasripad11/oneshot honestly the UI part was pretty smooth. typescript caught bugs, tailwind made styling easy. but the REAL challenge is gonna be the LLM integration. we’re thinking either open source models or building something lightweight since API costs would kill us.that’s basically it!!! everything works, it looks good, and we’re ready for the next phase. hope people actually use this lmao. thanks!!!!

I basically worked making the whole roadmap of the whole project. main components were the UI, systems and appealing to the customers. I also figured using API keys to make our prompts better would take too much money, so im gonna make my own LLM or use a free one. and that’s it thanks!!!!!! hope i got a lot of engagements on this