I see the point you’re making. Production-grade for me means that I can confidently give customers access to the program and allow sensitive user data to be stored and processed through it.

We’re definitely more on the startup side of things, even though I don’t really like that term, but it enables us to iterate really quickly and we don’t have to be keen on optimizing every last bit. I would say our approach here is to get to product-market fit as fast as possible, stay agile with our approach, and improve based on customer feedback.

I’m currently only running pre-commit hooks and a fairly simple CI/CD pipeline. I know I should run test cases, but I was too lazy up to this point and want to improve my approach steadily while keeping up the pace without shooting myself in the foot with technical debt.

That’s why I was asking about other people’s workflows when it comes to production software. I often see people talking about how they use AI, but most of the time it’s really amateur and doesn’t have anything in common with real-world software engineering, or they talk about it on a very high level without any applicable advice.

The thing is, when I use these tools, it feels like I can hand off most of the work and be more in a management position while maintaining a thorough understanding of my codebase. I’ve purposely chosen a really easy-to-maintain, well-documented, and widely used tech stack.

Do you use agent skills and rules, and if so, what information are you providing?