@nakedev/go-scaffold 0.3.0 → 0.3.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nakedev/go-scaffold",
-  "version": "0.3.0",
+  "version": "0.3.1",
   "description": "Scaffold Gin + GORM + Postgres Go backend projects with a consistent domain-module standard",
   "repository": {
     "type": "git",

package/templates/create/base/.claude/skills/go-scaffold/SKILL.md.hbs

@@ -46,12 +46,24 @@ missing AutoMigrate wiring, a `repository` interface out of sync with its
 Run from the project root:
 
 ```bash
-go-scaffold generate module <name> [--full] [--auth] [--permission <code>]
+go-scaffold generate module <name> --defaults [--full] [--auth] [--permission <code>]
 go-scaffold generate method <module> <name> --type <get|post|put|patch|delete> [--get-mode all|one] [--field <name>]
 go-scaffold generate migration <name>
-go-scaffold undo module <name> [-y]
+go-scaffold undo module <name> -y
 ```
 
+**Every value has to be a flag.** These commands prompt for whatever you
+leave out, and a prompt in a non-interactive shell exits 1 having written
+nothing — so a bare `generate module products` fails rather than taking the
+default. `--defaults` supplies the unasked-for answers (minimal, no auth);
+combine it with `--full`/`--auth`/`--permission` when you want those. The
+same applies to `--get-mode` (required with `--type get`) and `-y` on
+`undo module`. Every `add` command summarises what it will write and asks
+before writing: `-y` skips that confirmation, but `add auth` and `add worker`
+*also* ask which backing store to use — so those two need `--defaults`
+(or their own `--store`/`--queue` flag plus `-y`), while `add rbac -y` and
+`add observability -y` are enough.
+
 `<name>` for a module is a domain noun in whatever form reads naturally —
 singular or plural, any case, hyphens or underscores are all accepted and
 normalized (`products` → `product`, `Orders` → `order`, `order-item` →
@@ -79,7 +91,7 @@ is actually intended — otherwise prefer minimal plus explicit `generate method
 calls.
 
 `--auth` puts the module's routes behind a valid access token (requires
-`go-scaffold add auth` in this project first). `--permission <code>` also
+`go-scaffold add auth -y` in this project first). `--permission <code>` also
 requires that permission via `authz.Require` and seeds it in its own
 migration — it needs `add rbac`, and `--auth` must be passed alongside it.
 
@@ -114,7 +126,7 @@ domain decided against. Deletes `internal/app/<pkg>/`, the module's
 `migrations/<version>_create_<plural>.{up,down}.sql` pair, and reverses
 everything `generate module` wired up in `cmd/api/wiring.go` (and in
 `docs/openapi.yaml` + `docs/<plural>/` when OpenAPI is enabled). `-y` skips
-the confirmation prompt.
+the confirmation prompt, and is required in a non-interactive shell.
 
 The migration files go because `migrations/embed.go` is a `//go:embed *`: a
 typo's migration left behind runs on every database created from then on.

package/templates/create/base/AGENTS.md.hbs

@@ -11,14 +11,24 @@ package with its own model/handler/service/repository), or add a **new**
 endpoint to an existing one — stop and run the CLI instead:
 
 ```bash
-go-scaffold generate module <name>
+go-scaffold generate module <name> --defaults
 go-scaffold generate method <module> <name> --type <get|post|put|patch|delete>
 ```
 
+**Pass every value as a flag.** Run interactively, these commands ask for
+anything you left out — which has no answer in a non-interactive shell, so
+they exit 1 having written nothing. `--defaults` on `generate module` means
+"minimal, no auth, ask nothing"; add `--full`/`--auth`/`--permission` to it
+when you want those. Same rule elsewhere: `--get-mode` is required with
+`--type get`, and `undo module` needs `-y`. Every `add` command confirms
+before writing — `-y` skips that, but `add auth`/`add worker` also ask which
+backing store to use, so those two want `--defaults` (or `--store`/`--queue`
+plus `-y`).
+
 This applies **even when the request doesn't say "module"/"method" or name
 the CLI at all**. Recognize indirect asks as generation work, for example:
 
-- "add a products feature" → a new domain (`generate module products`)
+- "add a products feature" → a new domain (`generate module products --defaults`)
 - "let admins approve orders" → a new method on an existing module
   (`generate method orders approve --type patch`)
 - "we need an endpoint that lists overdue invoices" → a new `get` method
@@ -45,7 +55,7 @@ hand-rolling anything that looks like scaffolding.
 
 ## Command quick reference
 
-- `go-scaffold generate module <name>` — safe minimal model + errors +
+- `go-scaffold generate module <name> --defaults` — safe minimal model + errors +
   repository + service/handler plumbing, wired into `cmd/api/wiring.go` and
   appended to `migrations/`. Add endpoints one at a time with `generate
   method`, or pass `--full` to opt into a CRUD skeleton with TODO DTO fields
@@ -55,7 +65,7 @@ hand-rolling anything that looks like scaffolding.
   with the same name — pick a different one if it collides. With OpenAPI
   enabled it also writes a valid TODO path document and wires the index;
   replace placeholder schemas while implementing the method
-- `go-scaffold undo module <name>` — takes back a `generate module` that
+- `go-scaffold undo module <name> -y` — takes back a `generate module` that
   shouldn't have happened (typo'd name, domain decided against): deletes the
   package, un-wires main.go/OpenAPI, and deletes the module's migration files.
   It refuses if those migrations are committed to git or already applied to