rpr-cli 0.1.1__tar.gz → 0.1.2__tar.gz

{rpr_cli-0.1.1 → rpr_cli-0.1.2}/LICENSE

@@ -18,4 +18,4 @@ 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.
+SOFTWARE.

{rpr_cli-0.1.1 → rpr_cli-0.1.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: rpr-cli
-Version: 0.1.1
+Version: 0.1.2
 Summary: RPR CLI -- React Python Rust monorepo scaffolding orchestrator
 License-Expression: MIT
 License-File: LICENSE
@@ -53,17 +53,51 @@ uv add ../project-getting-started/dist/rpr_cli-*.whl
 
 ### 🚀 Scaffolding & Generation
 
-Scaffold a complete monorepo or add new apps and libraries.
+Create a new NX + UV monorepo, then add apps and packages as needed.
 
 ```bash
-rpr init my-app              # Scaffold a new monorepo (NX + UV)
-rpr generate domain my-app   # Add a domain package (shared logic & types)
+rpr init my-app              # Create/init my-app with root NX + UV tooling and AI instructions
+cd my-app
+rpr generate domain my-app   # Add a Python domain package
 rpr generate api my-app      # Add a FastAPI application
-rpr generate ui my-app       # Add a React UI library + application
+rpr generate ui my-app       # Add a React UI library and web app
 rpr generate engine my-app   # Add a Rust/PyO3 computation engine
 rpr generate storybook       # Add Storybook for UI component development
 ```
 
+`rpr init <project-name>` creates the project directory when it does not exist. If the directory already exists and is not an NX workspace, RPR initializes Git and runs `nx init` inside that directory.
+
+By default, `rpr init` scaffolds the root workspace and AI instructions only. To create project components during initialization, repeat `--scaffold`:
+
+```bash
+rpr init todo-list --scaffold domain
+rpr init todo-list --scaffold api --domain-migrations
+rpr init todo-list --scaffold api --scaffold web --domain-migrations
+```
+
+Available scaffolds are:
+
+- `instructions`: AI instruction files for Cursor, Copilot, Claude Code, and Gemini.
+- `domain`: Python DDD package at `packages/python/domain`.
+- `api`: FastAPI app at `apps/<name>-api`; also scaffolds `domain`.
+- `ui`: React UI library at `packages/node/<name>-ui`.
+- `web`: React web app at `apps/<name>-web`; also scaffolds `ui`.
+- `storybook`: Storybook host package; requires or scaffolds `ui`.
+- `engine`: Rust/PyO3 package at `packages/python/<name>-engine`.
+
+### Dependency Placement
+
+RPR keeps dependencies close to the package that uses them.
+
+- Root Python tooling such as Ruff, pytest, pyright, pre-commit, and maturin lives in the root `pyproject.toml`.
+- Domain runtime dependencies such as `sqlmodel`, `asyncpg`, `pydantic-settings`, and optional `alembic` are added to `packages/python/domain/pyproject.toml`.
+- API runtime dependencies such as `fastapi`, `uvicorn`, and the workspace domain package are added to `apps/<name>-api/pyproject.toml`.
+- Node dependencies are written to the relevant package-level `package.json` files, and `npm install` runs from the root workspace.
+
+Python dependency changes are made with `uv` so they are tracked in `pyproject.toml`. Node dependency changes are made through npm workspace package metadata and root `npm install`.
+
+The scaffold version manifest that powers generated dependency specs and the synced AI tech-stack overview lives in `src/rpr/dependency_manifest_data.py`. Refresh it from upstream registries with `rpr refresh manifest` when you want the repo-owned defaults to move forward.
+
 ### 🧠 AI Instructions & Code Templates
 
 Sync project context to your favorite AI tools and add common code patterns.
@@ -104,6 +138,7 @@ There is no separate `--tui` mode. The unified shell is the default chat experie
 Keep your project healthy and explore its structure.
 
 ```bash
+rpr refresh manifest         # Refresh the scaffold dependency manifest from npm, PyPI, and crates.io
 rpr check                    # Inspect project health and report setup status
 rpr map                      # Generate a structured code map of your project
 rpr settings                 # Inspect persisted shell settings
@@ -118,6 +153,8 @@ Persisted settings currently include:
 - `approval_mode`: default chat approval mode (`ask`, `auto-readonly`, `auto-all`)
 - `startup_help`: whether chat shows slash-command guidance on startup
 
+`rpr refresh manifest` is a repo-maintenance command. It rewrites `src/rpr/dependency_manifest_data.py`, which feeds scaffold dependency versions in `rpr generate ...` and the versioned overview text produced by `rpr sync rules`. Use `--dry-run` to preview the manifest rewrite without writing the file.
+
 ### ⚙️ Common Flags
 
 Most commands support these global flags:
@@ -128,9 +165,12 @@ Most commands support these global flags:
 Example:
 
 ```bash
+rpr init my-app --scaffold domain --dry-run
 rpr generate api my-app --dry-run
 ```
 
+Dry runs print the commands RPR would execute, the files/directories it would create or update, and the package dependencies it would add with their target scope.
+
 The `check` command also supports:
 
 - `--json`: Output machine-readable JSON for CI/CD integration.

{rpr_cli-0.1.1 → rpr_cli-0.1.2}/README.md

@@ -38,17 +38,51 @@ uv add ../project-getting-started/dist/rpr_cli-*.whl
 
 ### 🚀 Scaffolding & Generation
 
-Scaffold a complete monorepo or add new apps and libraries.
+Create a new NX + UV monorepo, then add apps and packages as needed.
 
 ```bash
-rpr init my-app              # Scaffold a new monorepo (NX + UV)
-rpr generate domain my-app   # Add a domain package (shared logic & types)
+rpr init my-app              # Create/init my-app with root NX + UV tooling and AI instructions
+cd my-app
+rpr generate domain my-app   # Add a Python domain package
 rpr generate api my-app      # Add a FastAPI application
-rpr generate ui my-app       # Add a React UI library + application
+rpr generate ui my-app       # Add a React UI library and web app
 rpr generate engine my-app   # Add a Rust/PyO3 computation engine
 rpr generate storybook       # Add Storybook for UI component development
 ```
 
+`rpr init <project-name>` creates the project directory when it does not exist. If the directory already exists and is not an NX workspace, RPR initializes Git and runs `nx init` inside that directory.
+
+By default, `rpr init` scaffolds the root workspace and AI instructions only. To create project components during initialization, repeat `--scaffold`:
+
+```bash
+rpr init todo-list --scaffold domain
+rpr init todo-list --scaffold api --domain-migrations
+rpr init todo-list --scaffold api --scaffold web --domain-migrations
+```
+
+Available scaffolds are:
+
+- `instructions`: AI instruction files for Cursor, Copilot, Claude Code, and Gemini.
+- `domain`: Python DDD package at `packages/python/domain`.
+- `api`: FastAPI app at `apps/<name>-api`; also scaffolds `domain`.
+- `ui`: React UI library at `packages/node/<name>-ui`.
+- `web`: React web app at `apps/<name>-web`; also scaffolds `ui`.
+- `storybook`: Storybook host package; requires or scaffolds `ui`.
+- `engine`: Rust/PyO3 package at `packages/python/<name>-engine`.
+
+### Dependency Placement
+
+RPR keeps dependencies close to the package that uses them.
+
+- Root Python tooling such as Ruff, pytest, pyright, pre-commit, and maturin lives in the root `pyproject.toml`.
+- Domain runtime dependencies such as `sqlmodel`, `asyncpg`, `pydantic-settings`, and optional `alembic` are added to `packages/python/domain/pyproject.toml`.
+- API runtime dependencies such as `fastapi`, `uvicorn`, and the workspace domain package are added to `apps/<name>-api/pyproject.toml`.
+- Node dependencies are written to the relevant package-level `package.json` files, and `npm install` runs from the root workspace.
+
+Python dependency changes are made with `uv` so they are tracked in `pyproject.toml`. Node dependency changes are made through npm workspace package metadata and root `npm install`.
+
+The scaffold version manifest that powers generated dependency specs and the synced AI tech-stack overview lives in `src/rpr/dependency_manifest_data.py`. Refresh it from upstream registries with `rpr refresh manifest` when you want the repo-owned defaults to move forward.
+
 ### 🧠 AI Instructions & Code Templates
 
 Sync project context to your favorite AI tools and add common code patterns.
@@ -89,6 +123,7 @@ There is no separate `--tui` mode. The unified shell is the default chat experie
 Keep your project healthy and explore its structure.
 
 ```bash
+rpr refresh manifest         # Refresh the scaffold dependency manifest from npm, PyPI, and crates.io
 rpr check                    # Inspect project health and report setup status
 rpr map                      # Generate a structured code map of your project
 rpr settings                 # Inspect persisted shell settings
@@ -103,6 +138,8 @@ Persisted settings currently include:
 - `approval_mode`: default chat approval mode (`ask`, `auto-readonly`, `auto-all`)
 - `startup_help`: whether chat shows slash-command guidance on startup
 
+`rpr refresh manifest` is a repo-maintenance command. It rewrites `src/rpr/dependency_manifest_data.py`, which feeds scaffold dependency versions in `rpr generate ...` and the versioned overview text produced by `rpr sync rules`. Use `--dry-run` to preview the manifest rewrite without writing the file.
+
 ### ⚙️ Common Flags
 
 Most commands support these global flags:
@@ -113,9 +150,12 @@ Most commands support these global flags:
 Example:
 
 ```bash
+rpr init my-app --scaffold domain --dry-run
 rpr generate api my-app --dry-run
 ```
 
+Dry runs print the commands RPR would execute, the files/directories it would create or update, and the package dependencies it would add with their target scope.
+
 The `check` command also supports:
 
 - `--json`: Output machine-readable JSON for CI/CD integration.