The interesting technical challenge was handling business rules safely. Instead of using LLMs to write execute-only code (which is dangerous), I use Llama 3 to translate natural language rules into "JSON Logic". This creates a portable logic layer that runs on both the Frontend (for instant UI feedback) and Backend (for Zod validation), without using eval().
It is currently in Public Beta. The output is a standard ZIP file.
I would love your feedback on the generated folder structure and the developer experience.
trsthales•2h ago
I built StackForge because I was tired of the "Day 1" problem: setting up Auth, Stripe, Prisma, and Docker configurations for every new SaaS idea.
Most low-code tools lock you into their ecosystem. I wanted an "accelerator" that outputs standard, clean code that I can eject and host anywhere.
The Stack: - Frontend: React 19 + Vite 7 (Tailwind) - Backend: Node.js + Express 5 - ORM: Prisma (with auto-generated schemas) - DB: PostgreSQL (via Docker Compose)
The interesting technical challenge was handling business rules safely. Instead of using LLMs to write execute-only code (which is dangerous), I use Llama 3 to translate natural language rules into "JSON Logic". This creates a portable logic layer that runs on both the Frontend (for instant UI feedback) and Backend (for Zod validation), without using eval().
It is currently in Public Beta. The output is a standard ZIP file.
I would love your feedback on the generated folder structure and the developer experience.