StackForge

Starting a new application often means repeating the same setup work: choosing frameworks, creating frontend and backend folders, configuring environment files, connecting the database, adding Docker support, setting up tests, and writing the initial documentation. Existing scaffolding tools are usually focused on a single framework or a fixed stack. I wanted a tool that could generate frontend-only, backend-only, or full-stack projects from interchangeable providers while still producing a coherent project structure. StackForge was created to reduce that repetitive setup work and make it easier to begin with a practical, tested foundation rather than spending the first few hours connecting unrelated templates.

he first workflow to try is generating a full-stack TypeScript project with Next.js, Express, and PostgreSQL. Run: npx @mide6x/create-stackforge@next my-app Then select: Full Stack Next.js TypeScript Express PostgreSQL Users can also enable Docker and generated test suites. StackForge creates the frontend, backend, database integration, environment templates, documentation, development commands, and optional tests as one connected project rather than as separate unrelated templates.

StackForge uses a provider-driven architecture. Frontends, backends, databases, integrations, and test generators are separate modules that can be combined without placing every stack combination inside one large conditional generator. The main design goal is composability without sacrificing the quality of the generated result. StackForge does not simply place two templates next to each other; its integrations connect them, generate the correct environment variables, add dependencies, produce shared documentation, and provide commands for running the complete project. It also treats generated projects as real software rather than disposable examples. The repository includes generated-project tests, build smoke tests, Docker validation, path-safety protections, and a bundled CLI package that can be installed independently.

The next phase is focused on expanding integrations and improving the first-run experience. Planned work includes: additional frontend, backend, and database providers authentication integrations better local Supabase support, including migrations and seed files improved Python environment setup with automatic uv or standard venv support more generated end-to-end test combinations configurable deployment targets third-party provider support richer non-interactive CLI options for automation and CI workflows The broader direction is to make StackForge a reliable foundation for generating maintainable application stacks rather than only a collection of starter templates.