create-macostack 0.6.0 → 0.6.1

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 macobits
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -1,53 +1,99 @@
 # create-macostack
 
-Orquestador mínimo para crear ventures macostack desde templates privados.
+Scaffold a production-ready full-stack app from the macostack templates — a Bun + Hono + Postgres backend and a TanStack (React) web app — with a single command.
 
 ```bash
-export GITHUB_TOKEN="github_pat_..." # fine-grained, Contents: Read-only
-bun create macostack mi-tienda
+bun create macostack my-app
 ```
 
-Salida esperada:
+An interactive wizard walks you through the rest:
 
-```txt
-mi-tienda/
-    server/    # repo git propio
-    client/    # repo git propio
+1. **Pick the parts** your app needs — backend API, web app, or both.
+2. **Choose a deploy target and feature modules.** Each template declares its own questions; the CLI merges them so every feature is asked exactly once for the whole app.
+3. **Optionally prefill environment values** — your primary domain (CORS, cookie scope, and the web app's API URL) and a Resend API key for transactional email.
+
+The CLI then downloads each template without its git history, installs dependencies, runs each template's own setup (app name, fresh secrets, module wiring), and leaves every part as its own independent git repository, ready to push.
+
+## Requirements
+
+- [Bun](https://bun.sh) 1.x
+- GitHub access to the template repositories (they are private by default):
+
+```bash
+gh auth login
+# or
+export GITHUB_TOKEN=github_pat_…   # fine-grained token, Contents: Read-only
 ```
 
-La raíz no se inicializa como git. El CLI descarga tarballs privados, instala con
-`bun install`, delega `bun run setup` cuando existe, y asegura un repo git por
-mitad si el setup no lo creó.
+Access is verified before anything is written to disk — a typo'd repo or missing permission fails cleanly, with no half-created folders.
 
-## Desarrollo local
+## Usage
 
 ```bash
-bun install
-bun run dev mi-tienda
+bun create macostack my-app     # scaffold into ./my-app
+bun create macostack .          # scaffold into the current (empty) directory
 ```
 
-## Configuración
+Result:
 
-Defaults:
+```txt
+my-app/
+├── server/    # Bun + Hono + Postgres API — its own git repo
+└── client/    # TanStack web app — its own git repo
+```
 
-- owner: `macobits`
-- server repo: `macostack-server`
-- client repo: `macostack-client`
-- ref: `main`
+The root folder is intentionally **not** a git repository: server and client are designed to live and deploy as separate repos.
 
-Flags útiles:
+### Managing an existing app
+
+Run the CLI again inside an app it created to add the missing part or toggle feature modules on and off — it detects the existing setup and switches to manage mode:
 
 ```bash
-bun run dev mi-tienda --owner macobits --ref main
-bun run dev mi-api --server --skip-setup
-bun run dev mi-web --client --skip-install
+cd my-app
+bun create macostack .
 ```
 
-También puedes usar env vars:
+### Flags
+
+| Flag | Description |
+| --- | --- |
+| `--server` / `--client` | Scaffold only that part (default: interactive) |
+| `--yes` | Non-interactive: both parts, template defaults |
+| `--owner <org>` | GitHub owner of the template repos (default: `macobits`) |
+| `--ref <ref>` | Branch or tag to download (default: `main`) |
+| `--server-repo <name>` | Server template repo (default: `macostack-server`) |
+| `--client-repo <name>` | Client template repo (default: `macostack-client`) |
+| `--skip-install` | Skip `bun install` |
+| `--skip-setup` | Skip each template's setup wizard |
+| `--help` | Print usage |
+
+### Environment variables
+
+| Variable | Description |
+| --- | --- |
+| `GITHUB_TOKEN` / `GH_TOKEN` | Token used to download the templates (falls back to `gh auth token`) |
+| `MACOSTACK_GITHUB_OWNER` | Default template owner |
+| `MACOSTACK_SERVER_REPO` | Default server template repo |
+| `MACOSTACK_CLIENT_REPO` | Default client template repo |
+| `MACOSTACK_REF` | Default branch or tag |
+
+## Bring your own templates
+
+The orchestrator is deliberately template-agnostic: it never hardcodes which features exist. Point `--owner`, `--server-repo`, and `--client-repo` at your own repositories, and expose a `setup` script in each template's `package.json`:
+
+- `bun run setup --questions` prints a JSON spec of the questions the template supports (feature modules, optional deploy target).
+- `bun run setup --yes --name <app> [--modules a,b] [--runtime x] [--domain d]` applies the answers.
+
+Anything the template declares, the CLI renders — nothing more.
+
+## Development
 
 ```bash
-MACOSTACK_GITHUB_OWNER=macobits
-MACOSTACK_SERVER_REPO=macostack-server
-MACOSTACK_CLIENT_REPO=macostack-client
-GITHUB_TOKEN=github_pat_...
+bun install
+bun run dev my-app --skip-install   # run the CLI from source
+bun run typecheck
 ```
+
+## License
+
+[MIT](./LICENSE) © macobits

package/bin/create-macostack.ts

@@ -187,7 +187,7 @@ if (scaffoldHere) {
     }
 } else if (positional) {
     if (!validName(positional)) {
-        bail("App names use lowercase letters, digits and dashes — e.g. soccer-app");
+        bail("App names use lowercase letters, digits and dashes — e.g. my-app");
     }
     appName = positional;
 } else if (flags.yes) {
@@ -197,9 +197,9 @@ if (scaffoldHere) {
     appName = answered(
         await text({
             message: "What should we call your app?",
-            placeholder: "soccer-app",
+            placeholder: "my-app",
             validate: (v) =>
-                validName(v ?? "") ? undefined : "lowercase letters, digits and dashes — e.g. soccer-app",
+                validName(v ?? "") ? undefined : "lowercase letters, digits and dashes — e.g. my-app",
         }),
     );
 }

package/package.json

@@ -1,7 +1,22 @@
 {
     "name": "create-macostack",
-    "version": "0.6.0",
-    "description": "Private macostack scaffold orchestrator for detached server/client repos.",
+    "version": "0.6.1",
+    "description": "Scaffold a production-ready full-stack app from the macostack templates: Bun + Hono + Postgres backend and TanStack web app, each as its own git repo.",
+    "license": "MIT",
+    "repository": {
+        "type": "git",
+        "url": "git+https://github.com/macobits/create-macostack.git"
+    },
+    "keywords": [
+        "create",
+        "scaffold",
+        "template",
+        "bun",
+        "hono",
+        "tanstack",
+        "fullstack",
+        "macostack"
+    ],
     "type": "module",
     "bin": {
         "create-macostack": "./bin/create-macostack.ts"