As I have mentioned in other threads, I am working on redoing my app and am developing a details specification to do this. I think I am close so I ran it through Claude. One of its comments was to specify the stack (see below), however I am not over the technology well enough to feel comfortable in doing tis myself but had been happy to let Agent select it based on my requirements. What are people’s thoughts?
1. Technology Stack Specification
Add a section specifying:
Frontend: React with TypeScript, Tailwind CSS
Backend: Node.js/Express with TypeScript
Database: PostgreSQL
Authentication: Firebase Auth
File Upload: Consider specifying (AWS S3, Firebase Storage, etc.)
Deployment: Specify platform (Vercel, Railway, etc.)
I have recently requested (from the Agent) a recommended/updated tech stack for a major revision I’m planning. However when I went through the process of pressing the Agent to dig deeper into the details of the functional revision, conflicts and technical obstacles arose with the use of its recommended tech stack. My suggestion is to stress-test the details of your specification with the Agent to ensure that as many obstacles get surfaced before the Agent starts coding. One technique I use is to start a fresh chat and ask the same questions all over again (always referring back to the specification doc). The loss of chat context can help get you a fresh perspective as long as you have a spec document to use as the reference for the questions.
I’m don’t have a technical background either but I’ve found the constant questioning of the Agent logic can help you learn where the risks lie.
1 Like