simple-module-cli 0.0.11__tar.gz → 0.0.12__tar.gz

{simple_module_cli-0.0.11 → simple_module_cli-0.0.12}/PKG-INFO

@@ -1,7 +1,7 @@
 Metadata-Version: 2.4
 Name: simple_module_cli
-Version: 0.0.11
-Summary: Standalone scaffolder for the SimpleModule framework — `sm new`, `sm create-module`, plugin host.
+Version: 0.0.12
+Summary: Standalone scaffolder for the SimpleModule framework — `smpy new`, `smpy create-module`, plugin host.
 Project-URL: Homepage, https://github.com/antosubash/simple_module_python
 Project-URL: Repository, https://github.com/antosubash/simple_module_python
 Project-URL: Issues, https://github.com/antosubash/simple_module_python/issues
@@ -34,7 +34,7 @@ pip install simple_module_cli
 # or, to keep the CLI in its own venv:
 pipx install simple_module_cli
 # or, to run it without installing:
-uvx --from simple_module_cli sm new my-app
+uvx --from simple_module_cli smpy new my-app
 ```
 
 The package depends only on `typer` and `tomlkit` — installing it does **not** pull in FastAPI, SQLModel, or any other framework runtime.
@@ -42,21 +42,21 @@ The package depends only on `typer` and `tomlkit` — installing it does **not**
 ## Usage
 
 ```bash
-sm new my-app                       # interactive wizard
-sm new my-app --yes --preset full   # all built-in modules + background jobs
-sm create-module my_feature         # scaffold a publishable module package
-sm create-host bare-host            # scaffold a bare host (no opinionated wiring)
+smpy new my-app                       # interactive wizard
+smpy new my-app --yes --preset full   # all built-in modules + background jobs
+smpy create-module my_feature         # scaffold a publishable module package
+smpy create-host bare-host            # scaffold a bare host (no opinionated wiring)
 ```
 
-Built-in commands: `sm new`, `sm create-host`, `sm create-module`.
+Built-in commands: `smpy new`, `smpy create-host`, `smpy create-module`.
 
 When other framework packages are installed, they contribute additional subcommands via the `simple_module_cli.cli_plugins` entry-point group:
 
 | Package | Commands |
 |---|---|
-| `simple_module_hosting` | `sm host gen-pages`, `sm host sync-js-deps` |
-| `simple_module_users`   | `sm users create-admin` |
-| `simple_module_settings` | `sm settings import-from-env` |
+| `simple_module_hosting` | `smpy host gen-pages`, `smpy host sync-js-deps` |
+| `simple_module_users`   | `smpy users create-admin` |
+| `simple_module_settings` | `smpy settings import-from-env` |
 
 ## License
 

{simple_module_cli-0.0.11 → simple_module_cli-0.0.12}/README.md

@@ -9,7 +9,7 @@ pip install simple_module_cli
 # or, to keep the CLI in its own venv:
 pipx install simple_module_cli
 # or, to run it without installing:
-uvx --from simple_module_cli sm new my-app
+uvx --from simple_module_cli smpy new my-app
 ```
 
 The package depends only on `typer` and `tomlkit` — installing it does **not** pull in FastAPI, SQLModel, or any other framework runtime.
@@ -17,21 +17,21 @@ The package depends only on `typer` and `tomlkit` — installing it does **not**
 ## Usage
 
 ```bash
-sm new my-app                       # interactive wizard
-sm new my-app --yes --preset full   # all built-in modules + background jobs
-sm create-module my_feature         # scaffold a publishable module package
-sm create-host bare-host            # scaffold a bare host (no opinionated wiring)
+smpy new my-app                       # interactive wizard
+smpy new my-app --yes --preset full   # all built-in modules + background jobs
+smpy create-module my_feature         # scaffold a publishable module package
+smpy create-host bare-host            # scaffold a bare host (no opinionated wiring)
 ```
 
-Built-in commands: `sm new`, `sm create-host`, `sm create-module`.
+Built-in commands: `smpy new`, `smpy create-host`, `smpy create-module`.
 
 When other framework packages are installed, they contribute additional subcommands via the `simple_module_cli.cli_plugins` entry-point group:
 
 | Package | Commands |
 |---|---|
-| `simple_module_hosting` | `sm host gen-pages`, `sm host sync-js-deps` |
-| `simple_module_users`   | `sm users create-admin` |
-| `simple_module_settings` | `sm settings import-from-env` |
+| `simple_module_hosting` | `smpy host gen-pages`, `smpy host sync-js-deps` |
+| `simple_module_users`   | `smpy users create-admin` |
+| `simple_module_settings` | `smpy settings import-from-env` |
 
 ## License
 

{simple_module_cli-0.0.11 → simple_module_cli-0.0.12}/pyproject.toml

@@ -1,7 +1,7 @@
 [project]
 name = "simple_module_cli"
-version = "0.0.11"
-description = "Standalone scaffolder for the SimpleModule framework — `sm new`, `sm create-module`, plugin host."
+version = "0.0.12"
+description = "Standalone scaffolder for the SimpleModule framework — `smpy new`, `smpy create-module`, plugin host."
 readme = "README.md"
 license = "MIT"
 license-files = ["LICENSE"]
@@ -25,7 +25,7 @@ dependencies = [
 ]
 
 [project.scripts]
-sm = "simple_module_cli.cli:main"
+smpy = "simple_module_cli.cli:main"
 simple-module = "simple_module_cli.cli:main"
 
 [project.urls]

{simple_module_cli-0.0.11 → simple_module_cli-0.0.12}/simple_module_cli/app_project.py

@@ -195,7 +195,7 @@ def _seed_static_dist_placeholder(static_dist: Path) -> None:
 def _pin_sample_module_deps(sample_dest: Path) -> None:
     """Replace the module template's future-API range pins with exact pins.
 
-    The shared ``sm create-module`` template ships ``>=1.0,<2.0`` against the
+    The shared ``smpy create-module`` template ships ``>=1.0,<2.0`` against the
     framework's eventual stable line, but the workspace-bundled sample has to
     resolve against whatever the framework version actually is today (``==X``
     in pre-1.0). Without rewriting, ``uv sync`` can't satisfy the workspace.

{simple_module_cli-0.0.11 → simple_module_cli-0.0.12}/simple_module_cli/cli.py

@@ -1,13 +1,13 @@
-"""Root `sm` Typer app — scaffolders + plugin mount.
+"""Root `smpy` Typer app — scaffolders + plugin mount.
 
 Built-in commands:
-  sm new
-  sm create-host
-  sm create-module
-  sm skills add / list / update
+  smpy new
+  smpy create-host
+  smpy create-module
+  smpy skills add / list / update
 
 Plugins discovered via the ``simple_module_cli.cli_plugins`` entry-point
-group are mounted as named subgroups (e.g. ``sm host gen-pages``).
+group are mounted as named subgroups (e.g. ``smpy host gen-pages``).
 """
 
 from __future__ import annotations
@@ -101,7 +101,7 @@ discover_and_mount(app)
 
 
 def main() -> None:
-    """Entry point for the `sm` console script."""
+    """Entry point for the `smpy` console script."""
     app()
 
 

{simple_module_cli-0.0.11 → simple_module_cli-0.0.12}/simple_module_cli/new.py

@@ -1,4 +1,4 @@
-"""``sm new`` Typer command — flag-driven or interactive scaffolder."""
+"""``smpy new`` Typer command — flag-driven or interactive scaffolder."""
 
 from __future__ import annotations
 

{simple_module_cli-0.0.11 → simple_module_cli-0.0.12}/simple_module_cli/package_update.py

@@ -1,4 +1,4 @@
-"""``sm package-update`` — bump simple_module_* deps to latest PyPI versions.
+"""``smpy package-update`` — bump simple_module_* deps to latest PyPI versions.
 
 Walks the project's ``pyproject.toml`` (and any ``[tool.uv.workspace]`` members),
 finds every dependency whose distribution name starts with ``simple_module_`` /

{simple_module_cli-0.0.11 → simple_module_cli-0.0.12}/simple_module_cli/plugins.py

@@ -1,11 +1,11 @@
-"""Plugin discovery for ``sm`` via the ``simple_module_cli.cli_plugins`` group.
+"""Plugin discovery for ``smpy`` via the ``simple_module_cli.cli_plugins`` group.
 
 Each entry-point's value (``module:attr``) must resolve to a
 :class:`typer.Typer` instance. The entry-point name becomes the
-subcommand namespace under ``sm`` (e.g. ``sm host gen-pages``).
+subcommand namespace under ``smpy`` (e.g. ``smpy host gen-pages``).
 
 Failed loads (broken import, wrong type) print one line to stderr and
-are skipped — ``sm`` keeps working with whatever else loads.
+are skipped — ``smpy`` keeps working with whatever else loads.
 """
 
 from __future__ import annotations

{simple_module_cli-0.0.11 → simple_module_cli-0.0.12}/simple_module_cli/recipes.py

@@ -1,6 +1,6 @@
 """Per-module post-scaffold recipes.
 
-A recipe is invoked by ``sm new`` after the base host scaffold lands. It
+A recipe is invoked by ``smpy new`` after the base host scaffold lands. It
 performs module-specific actions (write helper scripts, append Make
 targets, drop a docker-compose stack). The framework layer is kept free
 of devex concerns — recipes know about Makefiles and compose, framework
@@ -68,7 +68,7 @@ class BackgroundTasksRecipe:
             if path.exists():
                 raise FileExistsError(
                     f"{path} already exists — refusing to clobber. "
-                    "Remove the file or run `sm new` against an empty directory."
+                    "Remove the file or run `smpy new` against an empty directory."
                 )
 
         run_worker_dest.parent.mkdir(parents=True, exist_ok=True)

{simple_module_cli-0.0.11 → simple_module_cli-0.0.12}/simple_module_cli/skills/README.md

@@ -6,22 +6,22 @@ Agent skills for working in a [simple_module_python](https://github.com/antosuba
 
 There are two install paths — pick whichever fits your project.
 
-### Option A — `sm skills` (recommended for `simple_module_cli` users)
+### Option A — `smpy skills` (recommended for `simple_module_cli` users)
 
-Every project produced by `sm new` already depends on `simple_module_cli`, which ships these skills inside its wheel. From the project root:
+Every project produced by `smpy new` already depends on `simple_module_cli`, which ships these skills inside its wheel. From the project root:
 
 ```bash
-sm skills list                                          # see what's available
-sm skills add                                           # install ALL skills into ./.claude/skills/
-sm skills add simple-module-creating                    # install just one
-sm skills add -g                                        # install into ~/.claude/skills (machine-wide)
-sm skills add --dest agents/skills                      # custom target dir
-sm skills add --symlink                                 # symlink to the bundled source (good for skill devs)
-sm skills update                                        # re-pull updates for skills already installed
-sm skills update simple-module-doctor                   # explicit re-pull (force-overwrites)
+smpy skills list                                          # see what's available
+smpy skills add                                           # install ALL skills into ./.claude/skills/
+smpy skills add simple-module-creating                    # install just one
+smpy skills add -g                                        # install into ~/.claude/skills (machine-wide)
+smpy skills add --dest agents/skills                      # custom target dir
+smpy skills add --symlink                                 # symlink to the bundled source (good for skill devs)
+smpy skills update                                        # re-pull updates for skills already installed
+smpy skills update simple-module-doctor                   # explicit re-pull (force-overwrites)
 ```
 
-`sm skills` resolves the bundled set against whatever version of `simple_module_cli` is installed, so upgrading the CLI ships skill updates the next time you run `sm skills update`.
+`smpy skills` resolves the bundled set against whatever version of `simple_module_cli` is installed, so upgrading the CLI ships skill updates the next time you run `smpy skills update`.
 
 ### Option B — `npx skills` (no Python install needed)
 
@@ -38,7 +38,7 @@ The CLI is [vercel-labs/skills](https://github.com/vercel-labs/skills); see its
 
 | Skill | Use when |
 |---|---|
-| [simple-module-cli](./simple-module-cli/SKILL.md) | Invoking the `sm` CLI — `sm new`, `sm create-host`, `sm create-module`, `sm host gen-pages`, `sm users create-admin`, etc. |
+| [simple-module-cli](./simple-module-cli/SKILL.md) | Invoking the `smpy` CLI — `smpy new`, `smpy create-host`, `smpy create-module`, `smpy host gen-pages`, `smpy users create-admin`, etc. |
 | [simple-module-creating](./simple-module-creating/SKILL.md) | Adding a new feature package — scaffolding, entry-point, `ModuleMeta` |
 | [simple-module-conventions](./simple-module-conventions/SKILL.md) | Writing or reviewing module code — the invariant list (SQLModel everywhere, settings layout, framework→plugin direction, etc.) |
 | [simple-module-database](./simple-module-database/SKILL.md) | Adding SQLModel tables, picking a mixin, or debugging session/transaction behavior |

simple_module_cli-0.0.12/simple_module_cli/skills/simple-module-cli/SKILL.md

@@ -0,0 +1,170 @@
+---
+name: simple-module-cli
+description: Use when invoking the `smpy` CLI for a simple_module_python project — starting a new app, scaffolding a host or a publishable module, regenerating the Inertia page manifest, importing settings overrides from env, creating an admin user, or installing the bundled agent skills. Triggers on "smpy new", "smpy create-host", "smpy create-module", "smpy host gen-pages", "smpy users create-admin", "smpy skills add", or any unfamiliar `smpy` subcommand.
+---
+
+# simple_module_python: the `smpy` CLI
+
+The `smpy` command is provided by `simple_module_cli` (installed as a dep of `simple_module_hosting`). It groups four kinds of operations: scaffolding new things, project-time helpers for the host, admin shortcuts for the bundled modules, and installing the bundled agent skills.
+
+## Top-level commands
+
+| Command | When to use |
+|---|---|
+| `smpy new <name>` | Greenfield: scaffold a complete app (host + selected modules) in one shot, with an interactive wizard for DB / tenancy / module preset |
+| `smpy create-host <name>` | You want just a bare host project; you'll add modules later by `pip install`-ing them |
+| `smpy create-module <name>` | You're authoring a publishable module package (separate repo, distributed via PyPI) |
+| `smpy skills …` | Install / update the bundled agent-skill packs into a project (`add`, `list`, `update`) |
+| `smpy host …` | Project-time helpers run from inside a host directory (page manifest, JS dep sync) |
+| `smpy settings …` | Settings-module admin — currently `import-from-env` |
+| `smpy users …` | Users-module admin — currently `create-admin` |
+
+## `smpy new <name>` — the wizard
+
+The fastest way from zero to a working app. It calls `create-host` under the hood, then installs and wires up the modules you pick.
+
+```bash
+# Interactive (asks for DB, tenancy, preset, module list)
+smpy new MyApp
+
+# Non-interactive: take all defaults (sqlite, no tenancy, standard preset)
+smpy new MyApp --yes
+
+# Pick a preset and add extras
+smpy new MyApp --preset full --tenancy --db postgres
+smpy new MyApp --preset minimal --with background_tasks,file_storage --yes
+
+# Scaffold only — skip uv sync / npm install / alembic upgrade head
+smpy new MyApp --no-install
+```
+
+**Module presets:**
+
+| Preset | Modules included |
+|---|---|
+| `minimal` | `users` (and `auth` as a dep) |
+| `standard` (default) | `users`, `dashboard`, `permissions` (+ deps) |
+| `full` | every module in the catalog |
+| `custom` | interactive — pick each module yes/no |
+
+`--with` accepts a comma-separated list of catalog keys (`auth, users, permissions, products, dashboard, settings, feature_flags, file_storage, background_tasks, …`). Transitive `requires` are auto-added; the wizard prints `Added X (required by Y)` so you can see what got pulled in.
+
+**Options summary:**
+
+| Flag | Default | Meaning |
+|---|---|---|
+| `--dest <PATH>` | `./<name>` | Where to write the project |
+| `--db sqlite\|postgres` | `sqlite` | Backend configured in `.env.example` |
+| `--tenancy / --no-tenancy` | `--no-tenancy` | Enable the multi-tenant middleware |
+| `--preset minimal\|standard\|full` | wizard asks | Module bundle |
+| `--with <names>` | none | Extra catalog keys beyond the preset |
+| `--yes / -y` | off | Skip prompts; accept defaults |
+| `--no-install` | off | Skip `uv sync` / `npm install` / `alembic upgrade head` |
+
+## `smpy create-host <name>` — bare host
+
+```bash
+smpy create-host MyApp                       # empty host, no modules declared
+smpy create-host MyApp --with Auth,Products  # declare module deps in pyproject.toml
+smpy create-host MyApp --dest ./apps/myapp   # custom destination
+```
+
+`--with` takes **PascalCase module names** (matching `ModuleMeta.name`), not catalog keys. Use this when you want to drive the build yourself rather than via `smpy new`'s wizard.
+
+## `smpy create-module <name>` — module package
+
+For module authors publishing to PyPI. Scaffolds a standalone repo containing one module.
+
+```bash
+smpy create-module orders                    # writes ./simple_module_orders/
+smpy create-module orders --dest ./packages/orders
+```
+
+The result is a complete package: `pyproject.toml` with the entry point declared, `module.py` with `ModuleBase`/`ModuleMeta` skeleton, `models.py`, `contracts/`, `endpoints/{api,views}.py`, `pages/`, `locales/en.json`, plus a tests directory wired up with `simple_module_test` fixtures.
+
+`<name>` accepts any case — `orders`, `Orders`, `ORDERS`, `blog_posts` all work. The CLI lowercases it for the directory and PascalCases it for `ModuleMeta.name`.
+
+For the post-scaffold steps (entry point, Inertia namespace, etc.) see **simple-module-creating**.
+
+## `smpy skills` — install the bundled agent skills
+
+`simple_module_cli` ships a set of [SKILL.md](https://agentskills.io/specification) packs (the ones in this directory). Drop them into any project so Claude Code / Cursor / Codex / etc. find them automatically.
+
+```bash
+smpy skills list                                          # see what's available
+smpy skills add                                           # install ALL skills into ./.claude/skills/
+smpy skills add simple-module-creating simple-module-cli  # specific ones only
+smpy skills add -g                                        # ~/.claude/skills (machine-wide)
+smpy skills add --dest agents/skills                      # explicit target dir
+smpy skills add --symlink                                 # symlink to bundled source (good when iterating on the skills themselves)
+smpy skills update                                        # re-pull whatever is already installed at the dest
+smpy skills update simple-module-doctor                   # explicitly re-pull one (always force-overwrites)
+```
+
+**Without `--force`, `smpy skills add` skips skills that already exist at the destination** — so re-running it is safe. Use `--force` (or `smpy skills update`) to overwrite.
+
+The bundle resolves against your installed `simple_module_cli`. To get newer skills, upgrade the CLI (`uv sync` or `pip install -U simple_module_cli`) and re-run `smpy skills update`.
+
+## `smpy host gen-pages` — regenerate the Inertia manifest
+
+Run from a host project. Scans every installed module's `pages/*.tsx`, writes `client_app/modules.{manifest.json,generated.ts,generated.css}`, and extends Vite's `server.fs.allow`.
+
+```bash
+smpy host gen-pages                              # uses ./client_app
+smpy host gen-pages --host-dir=apps/web/client_app
+```
+
+`smpy new` runs this at scaffold time; you only need to call it manually after adding/renaming `.tsx` files mid-session, or after `pip install`-ing a new module that ships pages.
+
+## `smpy host sync-js-deps` — install module JS deps
+
+Wheel-installed modules ship `package.json` declarations that need to land in the host's `client_app/node_modules`. This command does that. **In-repo workspace modules don't need it** — npm workspaces resolve them automatically.
+
+```bash
+smpy host sync-js-deps                           # uses ./client_app
+smpy host sync-js-deps --host-client-app=apps/web/client_app
+```
+
+Run after `pip install <module>` if the new module ships frontend code.
+
+## `smpy settings import-from-env`
+
+Walks the live environment for every `SM_<PREFIX>_<FIELD>` variable matching a registered settings dataclass and writes a SYSTEM-tier override into the settings module's store. Useful when promoting from environment-driven config (typical in Docker) to in-DB overrides (manageable in the admin UI) without re-keying values by hand.
+
+```bash
+smpy settings import-from-env
+```
+
+## `smpy users create-admin`
+
+Bootstraps the first admin user, or rotates an existing admin's password.
+
+```bash
+smpy users create-admin -e admin@example.com -p hunter2
+smpy users create-admin -e admin@example.com -p new-password --force      # rotate
+smpy users create-admin -e admin@example.com -p hunter2 --full-name "Admin"
+```
+
+| Flag | Meaning |
+|---|---|
+| `-e, --email` (required) | Admin email |
+| `-p, --password` (required) | Initial password (or new password with `--force`) |
+| `--full-name` | Display name |
+| `--force` | Update the password if the admin already exists; without it, the command exits if the email is taken |
+
+Don't bake `--password` literals into a script you commit; use a secrets store and pass via shell expansion.
+
+## Pitfalls
+
+- **Wrong shell for `--with`.** `smpy new` `--with auth,users` (catalog keys, lowercase). `smpy create-host` `--with Auth,Users` (`ModuleMeta.name`, PascalCase). They're not interchangeable.
+- **Ran `smpy new` inside an existing project.** The default `--dest ./<name>` creates a sibling directory. If the directory already exists and is non-empty, the command errors out — pass `--dest` explicitly to disambiguate.
+- **Ran `smpy host gen-pages` from outside the host directory.** Defaults to `./client_app`; pass `--host-dir` from elsewhere.
+- **Forgot `smpy host sync-js-deps` after `pip install`-ing a module with pages.** Vite resolves module imports against `client_app/node_modules`; the new module's JS deps won't land until you sync.
+- **Used `smpy create-module` to add a module to an existing host.** That command is for **publishable** packages, intended to live in their own repo. To add a module to an existing host: install it (`pip install simple_module_<name>` or add to `pyproject.toml` and `uv sync`), then autogenerate a migration. See **simple-module-creating** + **simple-module-migrations**.
+- **Calling `smpy create-admin` before migrations have run.** The users tables don't exist yet; the command will error. Run `alembic upgrade head` first (or use `smpy new` which does it for you when `--no-install` isn't set).
+
+## Related skills
+
+- **simple-module-creating** — what `smpy create-module` produces and the post-scaffold contract
+- **simple-module-inertia-pages** — what `smpy host gen-pages` regenerates and why
+- **simple-module-migrations** — the `alembic upgrade head` step `smpy new` runs

{simple_module_cli-0.0.11 → simple_module_cli-0.0.12}/simple_module_cli/skills/simple-module-creating/SKILL.md

@@ -12,13 +12,13 @@ description: Use when adding a new feature package to a simple_module_python app
 ```bash
 # scaffold a publishable module package in ./orders (run in a fresh repo or
 # inside a host's modules/ directory)
-sm create-module orders
+smpy create-module orders
 
 # install the new package into the host environment
 uv sync   # or: pip install -e ./orders
 
 # if you added a frontend page, regenerate the Inertia manifest
-sm host gen-pages --host-dir=client_app
+smpy host gen-pages --host-dir=client_app
 
 # if you added SQLModel tables, autogenerate + apply a migration
 uv run alembic revision --autogenerate -m "add orders module"

{simple_module_cli-0.0.11 → simple_module_cli-0.0.12}/simple_module_cli/skills/simple-module-inertia-pages/SKILL.md

@@ -15,12 +15,12 @@ description: Use when adding or debugging an Inertia.js page in a simple_module_
 | Module page (snake-case dir) | `inertia.render("BlogPosts/Index", ...)` | `<module_pkg>/blog_posts/pages/Index.tsx` |
 | Host page | `inertia.render("Landing", ...)` | `<host>/client_app/pages/Landing.tsx` |
 
-The namespace is **PascalCase of the module's directory name**, not the file system path. Directory `blog_posts` → `BlogPosts`. The framework's manifest generator (`sm host gen-pages`) wires up Vite's `import.meta.glob` to resolve these keys at runtime.
+The namespace is **PascalCase of the module's directory name**, not the file system path. Directory `blog_posts` → `BlogPosts`. The framework's manifest generator (`smpy host gen-pages`) wires up Vite's `import.meta.glob` to resolve these keys at runtime.
 
 After adding or renaming a `.tsx`, regenerate the manifest:
 
 ```bash
-sm host gen-pages --host-dir=client_app
+smpy host gen-pages --host-dir=client_app
 ```
 
 Boot regenerates it too; mid-session adds need the manual call before HMR sees them.

{simple_module_cli-0.0.11 → simple_module_cli-0.0.12}/simple_module_cli/skills/simple-module-migrations/SKILL.md

@@ -23,7 +23,7 @@ my_host/                       # the host project
 
 ## How autogenerate sees every module
 
-The host's `migrations/env.py` (scaffolded by `sm create-host`) calls:
+The host's `migrations/env.py` (scaffolded by `smpy create-host`) calls:
 
 ```python
 from simple_module_db import build_module_metadata, make_include_object

{simple_module_cli-0.0.11 → simple_module_cli-0.0.12}/simple_module_cli/skills/simple-module-testing/SKILL.md

@@ -84,7 +84,7 @@ modules/orders/
     └── test_service.py      # imports orders.service
 ```
 
-The directory must be listed in the root `pyproject.toml` under `[tool.pytest.ini_options].testpaths` for `make test` to pick it up. `sm create-module` adds this entry; if you scaffolded a module by hand, add it.
+The directory must be listed in the root `pyproject.toml` under `[tool.pytest.ini_options].testpaths` for `make test` to pick it up. `smpy create-module` adds this entry; if you scaffolded a module by hand, add it.
 
 ## Pitfalls
 

{simple_module_cli-0.0.11 → simple_module_cli-0.0.12}/simple_module_cli/skills_cmd.py

@@ -1,4 +1,4 @@
-"""``sm skills`` — install or update agent skill packs in a target project.
+"""``smpy skills`` — install or update agent skill packs in a target project.
 
 Bundles the SKILL.md packs shipped under ``simple_module_cli/skills/`` and
 materialises them into a project directory (default ``.claude/skills``) so any
@@ -7,9 +7,9 @@ can pick them up.
 
 Three subcommands:
 
-* ``sm skills list``    — show every bundled skill and its description.
-* ``sm skills add``     — copy (or symlink) skills into the destination.
-* ``sm skills update``  — re-copy skills that are already installed at the
+* ``smpy skills list``    — show every bundled skill and its description.
+* ``smpy skills add``     — copy (or symlink) skills into the destination.
+* ``smpy skills update``  — re-copy skills that are already installed at the
                           destination, overwriting them.
 """
 

{simple_module_cli-0.0.11 → simple_module_cli-0.0.12}/simple_module_cli/templates/host/client_app/pages.ts

@@ -2,7 +2,7 @@
  * Inertia page resolver.
  *
  * Module pages are discovered via a generated file (modules.generated.ts)
- * emitted by the Python host at boot, or manually via `sm gen-pages`. Each
+ * emitted by the Python host at boot, or manually via `smpy gen-pages`. Each
  * installed module contributes an import.meta.glob() call with an absolute
  * path, so pages shipped inside pip-installed module wheels resolve.
  *

{simple_module_cli-0.0.11 → simple_module_cli-0.0.12}/simple_module_cli/templates/host/main.py

@@ -1,6 +1,6 @@
 """Host application entry point.
 
-This file was generated by `sm create-host`. Modules are discovered at boot
+This file was generated by `smpy create-host`. Modules are discovered at boot
 via entry_points; add them to this host's pyproject.toml to install them.
 """
 

{simple_module_cli-0.0.11 → simple_module_cli-0.0.12}/simple_module_cli/wizard.py

@@ -1,4 +1,4 @@
-"""Interactive prompt sequence for ``sm new``."""
+"""Interactive prompt sequence for ``smpy new``."""
 
 from __future__ import annotations
 

{simple_module_cli-0.0.11 → simple_module_cli-0.0.12}/tests/test_build_packaging.py

@@ -40,7 +40,7 @@ def built_artifacts(tmp_path_factory) -> tuple[Path, Path]:
 
 
 def test_wheel_contains_bundled_skills(built_artifacts: tuple[Path, Path]) -> None:
-    """The wheel must ship the agent skill packs that ``sm skills`` depends on.
+    """The wheel must ship the agent skill packs that ``smpy skills`` depends on.
 
     Regression: ``[tool.hatch.build.targets.wheel.force-include]`` with
     ``../../skills`` made the wheel re-build from sdist crash with
@@ -61,7 +61,7 @@ def test_wheel_contains_bundled_skills(built_artifacts: tuple[Path, Path]) -> No
 
 
 def test_wheel_contains_templates(built_artifacts: tuple[Path, Path]) -> None:
-    """``sm new`` reads from ``simple_module_cli/templates`` — must ship in the wheel."""
+    """``smpy new`` reads from ``simple_module_cli/templates`` — must ship in the wheel."""
     _, wheel = built_artifacts
     with zipfile.ZipFile(wheel) as zf:
         names = zf.namelist()

{simple_module_cli-0.0.11 → simple_module_cli-0.0.12}/tests/test_cli_new.py

@@ -1,4 +1,4 @@
-"""Tests for the `sm new` / `simple-module new` CLI subcommand."""
+"""Tests for the `smpy new` / `simple-module new` CLI subcommand."""
 
 from __future__ import annotations
 

{simple_module_cli-0.0.11 → simple_module_cli-0.0.12}/tests/test_cli_new_regressions.py

@@ -1,4 +1,4 @@
-"""Regression tests for ``sm new`` scaffold bugs filed against released wheels.
+"""Regression tests for ``smpy new`` scaffold bugs filed against released wheels.
 
 Each test pins a specific issue's repro so the bug can't sneak back in
 without a CI failure pointing at the fix.

{simple_module_cli-0.0.11 → simple_module_cli-0.0.12}/tests/test_cli_package_update.py

@@ -1,4 +1,4 @@
-"""Tests for `sm package-update`."""
+"""Tests for `smpy package-update`."""
 
 from __future__ import annotations
 

{simple_module_cli-0.0.11 → simple_module_cli-0.0.12}/tests/test_cli_wizard.py

@@ -1,4 +1,4 @@
-"""Tests for the `sm new` interactive wizard."""
+"""Tests for the `smpy new` interactive wizard."""
 
 from __future__ import annotations
 

{simple_module_cli-0.0.11 → simple_module_cli-0.0.12}/tests/test_scaffolding_host.py

@@ -1,4 +1,4 @@
-"""Tests for the module-pages manifest and `sm create-host` scaffolding."""
+"""Tests for the module-pages manifest and `smpy create-host` scaffolding."""
 
 from __future__ import annotations
 
@@ -154,7 +154,7 @@ class TestCreateHost:
         assert "for mod in modules:" not in env_py
 
     async def test_cli_create_host_runs_end_to_end(self, tmp_path):
-        """The Click `sm create-host` command produces a working scaffold."""
+        """The Click `smpy create-host` command produces a working scaffold."""
         from simple_module_cli.cli import app
         from typer.testing import CliRunner
 

{simple_module_cli-0.0.11 → simple_module_cli-0.0.12}/tests/test_scaffolding_module.py

@@ -1,4 +1,4 @@
-"""Tests for `sm create-module` scaffolding: module package, CI, static bundling."""
+"""Tests for `smpy create-module` scaffolding: module package, CI, static bundling."""
 
 from __future__ import annotations
 
@@ -74,7 +74,7 @@ class TestCreateModule:
             create_module(dest, name="MyFeature")
 
     async def test_cli_create_module_runs_end_to_end(self, tmp_path):
-        """The Click `sm create-module` command produces a working scaffold."""
+        """The Click `smpy create-module` command produces a working scaffold."""
         from simple_module_cli.cli import app
         from typer.testing import CliRunner
 

{simple_module_cli-0.0.11 → simple_module_cli-0.0.12}/tests/test_skills_cmd.py

@@ -1,4 +1,4 @@
-"""Tests for the ``sm skills`` subcommand group."""
+"""Tests for the ``smpy skills`` subcommand group."""
 
 from __future__ import annotations
 

simple_module_cli-0.0.11/simple_module_cli/skills/simple-module-cli/SKILL.md

@@ -1,170 +0,0 @@
----
-name: simple-module-cli
-description: Use when invoking the `sm` CLI for a simple_module_python project — starting a new app, scaffolding a host or a publishable module, regenerating the Inertia page manifest, importing settings overrides from env, creating an admin user, or installing the bundled agent skills. Triggers on "sm new", "sm create-host", "sm create-module", "sm host gen-pages", "sm users create-admin", "sm skills add", or any unfamiliar `sm` subcommand.
----
-
-# simple_module_python: the `sm` CLI
-
-The `sm` command is provided by `simple_module_cli` (installed as a dep of `simple_module_hosting`). It groups four kinds of operations: scaffolding new things, project-time helpers for the host, admin shortcuts for the bundled modules, and installing the bundled agent skills.
-
-## Top-level commands
-
-| Command | When to use |
-|---|---|
-| `sm new <name>` | Greenfield: scaffold a complete app (host + selected modules) in one shot, with an interactive wizard for DB / tenancy / module preset |
-| `sm create-host <name>` | You want just a bare host project; you'll add modules later by `pip install`-ing them |
-| `sm create-module <name>` | You're authoring a publishable module package (separate repo, distributed via PyPI) |
-| `sm skills …` | Install / update the bundled agent-skill packs into a project (`add`, `list`, `update`) |
-| `sm host …` | Project-time helpers run from inside a host directory (page manifest, JS dep sync) |
-| `sm settings …` | Settings-module admin — currently `import-from-env` |
-| `sm users …` | Users-module admin — currently `create-admin` |
-
-## `sm new <name>` — the wizard
-
-The fastest way from zero to a working app. It calls `create-host` under the hood, then installs and wires up the modules you pick.
-
-```bash
-# Interactive (asks for DB, tenancy, preset, module list)
-sm new MyApp
-
-# Non-interactive: take all defaults (sqlite, no tenancy, standard preset)
-sm new MyApp --yes
-
-# Pick a preset and add extras
-sm new MyApp --preset full --tenancy --db postgres
-sm new MyApp --preset minimal --with background_tasks,file_storage --yes
-
-# Scaffold only — skip uv sync / npm install / alembic upgrade head
-sm new MyApp --no-install
-```
-
-**Module presets:**
-
-| Preset | Modules included |
-|---|---|
-| `minimal` | `users` (and `auth` as a dep) |
-| `standard` (default) | `users`, `dashboard`, `permissions` (+ deps) |
-| `full` | every module in the catalog |
-| `custom` | interactive — pick each module yes/no |
-
-`--with` accepts a comma-separated list of catalog keys (`auth, users, permissions, products, dashboard, settings, feature_flags, file_storage, background_tasks, …`). Transitive `requires` are auto-added; the wizard prints `Added X (required by Y)` so you can see what got pulled in.
-
-**Options summary:**
-
-| Flag | Default | Meaning |
-|---|---|---|
-| `--dest <PATH>` | `./<name>` | Where to write the project |
-| `--db sqlite\|postgres` | `sqlite` | Backend configured in `.env.example` |
-| `--tenancy / --no-tenancy` | `--no-tenancy` | Enable the multi-tenant middleware |
-| `--preset minimal\|standard\|full` | wizard asks | Module bundle |
-| `--with <names>` | none | Extra catalog keys beyond the preset |
-| `--yes / -y` | off | Skip prompts; accept defaults |
-| `--no-install` | off | Skip `uv sync` / `npm install` / `alembic upgrade head` |
-
-## `sm create-host <name>` — bare host
-
-```bash
-sm create-host MyApp                       # empty host, no modules declared
-sm create-host MyApp --with Auth,Products  # declare module deps in pyproject.toml
-sm create-host MyApp --dest ./apps/myapp   # custom destination
-```
-
-`--with` takes **PascalCase module names** (matching `ModuleMeta.name`), not catalog keys. Use this when you want to drive the build yourself rather than via `sm new`'s wizard.
-
-## `sm create-module <name>` — module package
-
-For module authors publishing to PyPI. Scaffolds a standalone repo containing one module.
-
-```bash
-sm create-module orders                    # writes ./simple_module_orders/
-sm create-module orders --dest ./packages/orders
-```
-
-The result is a complete package: `pyproject.toml` with the entry point declared, `module.py` with `ModuleBase`/`ModuleMeta` skeleton, `models.py`, `contracts/`, `endpoints/{api,views}.py`, `pages/`, `locales/en.json`, plus a tests directory wired up with `simple_module_test` fixtures.
-
-`<name>` accepts any case — `orders`, `Orders`, `ORDERS`, `blog_posts` all work. The CLI lowercases it for the directory and PascalCases it for `ModuleMeta.name`.
-
-For the post-scaffold steps (entry point, Inertia namespace, etc.) see **simple-module-creating**.
-
-## `sm skills` — install the bundled agent skills
-
-`simple_module_cli` ships a set of [SKILL.md](https://agentskills.io/specification) packs (the ones in this directory). Drop them into any project so Claude Code / Cursor / Codex / etc. find them automatically.
-
-```bash
-sm skills list                                          # see what's available
-sm skills add                                           # install ALL skills into ./.claude/skills/
-sm skills add simple-module-creating simple-module-cli  # specific ones only
-sm skills add -g                                        # ~/.claude/skills (machine-wide)
-sm skills add --dest agents/skills                      # explicit target dir
-sm skills add --symlink                                 # symlink to bundled source (good when iterating on the skills themselves)
-sm skills update                                        # re-pull whatever is already installed at the dest
-sm skills update simple-module-doctor                   # explicitly re-pull one (always force-overwrites)
-```
-
-**Without `--force`, `sm skills add` skips skills that already exist at the destination** — so re-running it is safe. Use `--force` (or `sm skills update`) to overwrite.
-
-The bundle resolves against your installed `simple_module_cli`. To get newer skills, upgrade the CLI (`uv sync` or `pip install -U simple_module_cli`) and re-run `sm skills update`.
-
-## `sm host gen-pages` — regenerate the Inertia manifest
-
-Run from a host project. Scans every installed module's `pages/*.tsx`, writes `client_app/modules.{manifest.json,generated.ts,generated.css}`, and extends Vite's `server.fs.allow`.
-
-```bash
-sm host gen-pages                              # uses ./client_app
-sm host gen-pages --host-dir=apps/web/client_app
-```
-
-`sm new` runs this at scaffold time; you only need to call it manually after adding/renaming `.tsx` files mid-session, or after `pip install`-ing a new module that ships pages.
-
-## `sm host sync-js-deps` — install module JS deps
-
-Wheel-installed modules ship `package.json` declarations that need to land in the host's `client_app/node_modules`. This command does that. **In-repo workspace modules don't need it** — npm workspaces resolve them automatically.
-
-```bash
-sm host sync-js-deps                           # uses ./client_app
-sm host sync-js-deps --host-client-app=apps/web/client_app
-```
-
-Run after `pip install <module>` if the new module ships frontend code.
-
-## `sm settings import-from-env`
-
-Walks the live environment for every `SM_<PREFIX>_<FIELD>` variable matching a registered settings dataclass and writes a SYSTEM-tier override into the settings module's store. Useful when promoting from environment-driven config (typical in Docker) to in-DB overrides (manageable in the admin UI) without re-keying values by hand.
-
-```bash
-sm settings import-from-env
-```
-
-## `sm users create-admin`
-
-Bootstraps the first admin user, or rotates an existing admin's password.
-
-```bash
-sm users create-admin -e admin@example.com -p hunter2
-sm users create-admin -e admin@example.com -p new-password --force      # rotate
-sm users create-admin -e admin@example.com -p hunter2 --full-name "Admin"
-```
-
-| Flag | Meaning |
-|---|---|
-| `-e, --email` (required) | Admin email |
-| `-p, --password` (required) | Initial password (or new password with `--force`) |
-| `--full-name` | Display name |
-| `--force` | Update the password if the admin already exists; without it, the command exits if the email is taken |
-
-Don't bake `--password` literals into a script you commit; use a secrets store and pass via shell expansion.
-
-## Pitfalls
-
-- **Wrong shell for `--with`.** `sm new` `--with auth,users` (catalog keys, lowercase). `sm create-host` `--with Auth,Users` (`ModuleMeta.name`, PascalCase). They're not interchangeable.
-- **Ran `sm new` inside an existing project.** The default `--dest ./<name>` creates a sibling directory. If the directory already exists and is non-empty, the command errors out — pass `--dest` explicitly to disambiguate.
-- **Ran `sm host gen-pages` from outside the host directory.** Defaults to `./client_app`; pass `--host-dir` from elsewhere.
-- **Forgot `sm host sync-js-deps` after `pip install`-ing a module with pages.** Vite resolves module imports against `client_app/node_modules`; the new module's JS deps won't land until you sync.
-- **Used `sm create-module` to add a module to an existing host.** That command is for **publishable** packages, intended to live in their own repo. To add a module to an existing host: install it (`pip install simple_module_<name>` or add to `pyproject.toml` and `uv sync`), then autogenerate a migration. See **simple-module-creating** + **simple-module-migrations**.
-- **Calling `sm create-admin` before migrations have run.** The users tables don't exist yet; the command will error. Run `alembic upgrade head` first (or use `sm new` which does it for you when `--no-install` isn't set).
-
-## Related skills
-
-- **simple-module-creating** — what `sm create-module` produces and the post-scaffold contract
-- **simple-module-inertia-pages** — what `sm host gen-pages` regenerates and why
-- **simple-module-migrations** — the `alembic upgrade head` step `sm new` runs