Projx

Projx

[](https://www.npmjs.com/package/create-projx) [](https://github.com/ukanhaupa/projx/actions/workflows/ci.yml) [](https://github.com/ukanhaupa/projx) [](https://opensource.org/licenses/MIT)

**Go from blank folder to production-ready project in 30 seconds.** Backend-only API, AI/ML app, mobile, full-stack, infra setup — pick what you need and get it wired with auth, database, Docker, CI/CD, hooks, and tests. All optional. All yours.


npx create-projx my-app

No SDK lock-in. No runtime dependency on Projx. Just clean code in your repo that you own forever.

---

You've done this a hundred times

Every new project starts with the same week of plumbing:

• Wire up auth (again).
• Configure the database and migrations (again).
• Write the Dockerfile and docker-compose.yml (again).
• Set up CI, linting, formatting, pre-commit hooks (again).
• Build the same login + CRUD scaffolding (again).
• Realize at 11pm that something's broken and you don't remember why (again).

You ship features two weeks late because the first two weeks were boilerplate.

Or your AI does it badly

Ask an LLM to "scaffold a full-stack app" and you get 50 files of plausible-looking code that breaks on first run. Wrong import paths. Outdated package versions. Auth that doesn't actually authenticate. You end up debugging machine-generated boilerplate, which is worse than writing it yourself.

What if you just… didn't?

npx create-projx my-app       # interactive — pick exactly what you need
cd my-app
./scripts/setup.sh            # installs everything you picked

Pick any combination of components — they're all optional:

# AI/ML backend only
npx create-p