@bleedingdev/modern-js-create 3.2.0-ultramodern.3 → 3.2.0-ultramodern.30

package/README.md

@@ -12,6 +12,13 @@
 
 Please follow [Quick Start](https://modernjs.dev/en/guides/get-started/quick-start) to get started with Modern.js.
 
+For UltraModern.js, use the BleedingDev create package. It defaults to the
+canonical SuperApp workspace and published BleedingDev package aliases:
+
+```bash
+pnpm dlx @bleedingdev/modern-js-create my-super-app
+```
+
 ### Router Template
 
 You can scaffold a TanStack Router first template:
@@ -22,16 +29,17 @@ npx @modern-js/create my-app --router tanstack
 
 ### Tailwind Template
 
-You can scaffold Tailwind CSS v4 setup (PostCSS + starter utility classes):
+Tailwind CSS v4 setup is generated by default. Disable it explicitly when you
+need a plain CSS starter:
 
 ```bash
-npx @modern-js/create my-app --tailwind
+npx @modern-js/create my-app --no-tailwind
 ```
 
-You can combine both options:
+TanStack Router and Tailwind CSS work together without extra flags:
 
 ```bash
-npx @modern-js/create my-app --router tanstack --tailwind
+npx @modern-js/create my-app --router tanstack
 ```
 
 ### BFF Runtime Template
@@ -58,24 +66,24 @@ Generated starters expose `presetUltramodern(...)` as the public opinionated
 config wrapper when you want the full Ultramodern setup surface in
 `modern.config.ts`.
 
-You can combine TanStack Router + Tailwind + Effect BFF in one command:
+You can combine TanStack Router + default Tailwind + Effect BFF in one command:
 
 ```bash
-npx @modern-js/create my-app --router tanstack --tailwind --bff-runtime effect
+npx @modern-js/create my-app --router tanstack --bff-runtime effect
 ```
 
 ### Micro Vertical Workspace Recipes
 
-Use the existing create flags to scaffold packages inside a Micro Vertical
-workspace. The shell and remotes use TanStack Router; services use Effect by
-default, with Hono kept as an explicit compatibility lane.
+Use the workspace add flow from the UltraModern workspace root. It derives the
+package path, package name, port, Module Federation name, topology entry, local
+overlay, ownership entry, and root `dev:*` script from the requested name and
+kind.
 
 ```bash
-npx @modern-js/create apps/shell --router tanstack --tailwind --workspace --sub
-npx @modern-js/create apps/remotes/catalog --router tanstack --tailwind --workspace --sub
-npx @modern-js/create apps/remotes/design-system --router tanstack --tailwind --workspace --sub
-npx @modern-js/create services/catalog-api --bff-runtime effect --workspace --sub
-npx @modern-js/create services/legacy-api --bff-runtime hono --workspace --sub
+npx @modern-js/create catalog --microvertical remote
+npx @modern-js/create design-system --microvertical horizontal-remote
+npx @modern-js/create catalog-api --microvertical service
+npx @modern-js/create catalog-contracts --microvertical shared
 ```
 
 When a design system needs independent deployment, treat it as a horizontal
@@ -85,10 +93,20 @@ regular workspace packages for tokens, primitives, generated clients, or
 domain-neutral utilities. Keep feature composites and workflow logic owned by a
 shell, remote, or service package.
 
+The lower-level `--router`, `--workspace`, and `--sub` flags remain available
+for manual package scaffolding, but UltraModern MicroVertical additions should
+prefer `--microvertical` to avoid hand-writing workspace paths and topology
+metadata.
+
 See
 `docs/super-app-rfc-adr/WORKSPACE-0001-micro-vertical-workspace-scaffolding.md`
 for the canonical workspace topology and local orchestration model.
 
+The published `@bleedingdev/modern-js-create` package is the preferred
+UltraModern.js entrypoint. The lower-level `--ultramodern-*` flags remain
+available for release engineering and local package-source testing, but users
+should not need them for normal app creation.
+
 ### Local Monorepo Testing
 
 When testing unreleased Modern.js packages from a local monorepo checkout, use