docs: switch @org placeholder from @acme to @your-org

@acme is itself a live npm scope, so it still reads as a real handle a
reader might try to use. @your-org is self-describing: it literally tells
readers "replace this with your own scope". Same pattern GitHub, npm,
and AWS docs use for org placeholders.

Also cleans up two descriptions that read awkwardly after the rename —
"Full Acme Corp monorepo scaffold" → "Monorepo scaffold" — since
personifying the placeholder as a company name is unhelpful when the
whole point is that it's not a company.

Touched: the RFC, docs/guide/create.md, docs/config/create.md,
packages/cli/src/create/{bin.ts, define-config.ts}, all four org
snap-tests, and the three org unit test specs. Four snap outputs
regenerated; 263 unit tests still pass.

Author: fengmk2

docs/config/create.md

@@ -11,12 +11,12 @@ import { defineConfig } from 'vite-plus';
 
 export default defineConfig({
   create: {
-    defaultTemplate: '@acme',
+    defaultTemplate: '@your-org',
   },
 });
 ```
 
-Any value accepted by `vp create` as a first argument works here — `@acme` for an org picker, `@acme/web` for a direct manifest entry, `vite:application` for a built-in, etc.
+Any value accepted by `vp create` as a first argument works here — `@your-org` for an org picker, `@your-org/web` for a direct manifest entry, `vite:application` for a built-in, etc.
 
 ## Precedence
 

docs/guide/create.md

@@ -35,7 +35,7 @@ Vite+ ships with these built-in templates:
 
 - Use shorthand templates like `vite`, `@tanstack/start`, `svelte`, `next-app`, `nuxt`, `react-router`, and `vue`
 - Use full package names like `create-vite` or `create-next-app`
-- Use local templates such as `./tools/create-ui-component` or `@acme/generator-*`
+- Use local templates such as `./tools/create-ui-component` or `@your-org/generator-*`
 - Use remote templates such as `github:user/repo` or `https://github.com/user/template-repo`
 
 Run `vp create --list` to see the built-in templates and the common shorthand templates Vite+ recognizes.
@@ -94,11 +94,11 @@ An organization can publish a curated set of templates under a single npm scope
 ### Pick from an org
 
 ```bash
-# Open an interactive picker over @acme/create's manifest
-vp create @acme
+# Open an interactive picker over @your-org/create's manifest
+vp create @your-org
 
 # Run a specific manifest entry directly
-vp create @acme/web
+vp create @your-org/web
 
 # Set the org as the default for a repo (see create.defaultTemplate config)
 vp create
@@ -113,7 +113,7 @@ There are two common layouts. Pick the one that matches the org's template count
 **Bundled (recommended for most orgs).** All templates live as subdirectories of `@org/create` itself. Manifest entries use relative `./path` values. One repo, one publish, one versioning story — the same pattern used by `create-vite` and `create-next-app`.
 
 ```
-@acme/create/
+@your-org/create/
 ├── package.json              # "vp": { "templates": [{ "template": "./templates/web" }, ...] }
 ├── templates/
 │   ├── web/
@@ -126,8 +126,8 @@ There are two common layouts. Pick the one that matches the org's template count
 **Manifest-only.** When the org already publishes independent `@org/template-*` packages (or hosts them on GitHub), `@org/create` stays a thin index.
 
 ```
-@acme/create/
-├── package.json              # "vp": { "templates": [{ "template": "@acme/template-web" }, ...] }
+@your-org/create/
+├── package.json              # "vp": { "templates": [{ "template": "@your-org/template-web" }, ...] }
 └── README.md
 ```
 
@@ -141,20 +141,20 @@ The manifest lives at `vp.templates` in `@org/create`'s `package.json`:
 
 ```json
 {
-  "name": "@acme/create",
+  "name": "@your-org/create",
   "version": "1.0.0",
   "vp": {
     "templates": [
       {
         "name": "monorepo",
-        "description": "Full Acme Corp monorepo",
-        "template": "@acme/template-monorepo",
+        "description": "Monorepo",
+        "template": "@your-org/template-monorepo",
         "monorepo": true
       },
       {
         "name": "web",
         "description": "Web app template (Vite + React)",
-        "template": "@acme/template-web",
+        "template": "@your-org/template-web",
         "keywords": ["web", "react", "app"]
       },
       {
@@ -177,7 +177,7 @@ Each entry supports:
 | `keywords`    | no       | Filter terms for picker search.                                                                                                                                                                                                              |
 | `monorepo`    | no       | If `true`, marks this entry as a monorepo-creating template. Hidden from the picker when `vp create` runs inside an existing monorepo, mirroring the built-in `vite:monorepo` filter.                                                        |
 
-An invalid manifest is a hard error, not a silent fall-through — a maintainer who shipped a manifest should hear about the offending field, e.g. `@acme/create: vp.templates[2].template must be a non-empty string`.
+An invalid manifest is a hard error, not a silent fall-through — a maintainer who shipped a manifest should hear about the offending field, e.g. `@your-org/create: vp.templates[2].template must be a non-empty string`.
 
 ### Bundled subdirectory templates
 
@@ -191,11 +191,11 @@ Commit this in `vite.config.ts` at the project root:
 import { defineConfig } from 'vite-plus';
 
 export default defineConfig({
-  create: { defaultTemplate: '@acme' },
+  create: { defaultTemplate: '@your-org' },
 });
 ```
 
-Now `vp create` (with no argument) drops straight into the `@acme` picker. See [`create.defaultTemplate`](/config/create) for details.
+Now `vp create` (with no argument) drops straight into the `@your-org` picker. See [`create.defaultTemplate`](/config/create) for details.
 
 The picker always appends a trailing **Vite+ built-in templates** entry so `vite:monorepo` / `vite:application` / `vite:library` / `vite:generator` stay reachable from the picker — selecting it routes to the standard built-in flow. For scripts and CI, explicit specifiers (`vp create vite:library`) bypass the configured default.
 
@@ -204,16 +204,16 @@ The picker always appends a trailing **Vite+ built-in templates** entry so `vite
 `vp create @org --no-interactive` prints a stable, fixed-column table of the manifest (name, description, resolved template specifier) and exits 1. The output is machine-parseable, so scripts and AI agents can recover the list without a separate `--list` flag:
 
 ```
-error: vp create @acme requires a template selection in non-interactive mode.
+error: vp create @your-org requires a template selection in non-interactive mode.
 
-available templates from @acme/create:
+available templates from @your-org/create:
 
   NAME     DESCRIPTION                          TEMPLATE
-  web      Web app template (Vite + React)      @acme/template-web
-  library  TypeScript library template          @acme/template-library
+  web      Web app template (Vite + React)      @your-org/template-web
+  library  TypeScript library template          @your-org/template-library
   demo     Bundled demo template                ./templates/demo
 
-hint: rerun with an explicit selection, e.g. `vp create @acme/web`,
+hint: rerun with an explicit selection, e.g. `vp create @your-org/web`,
       or use a Vite+ built-in template like `vp create vite:application`.
 ```
 

packages/cli/snap-tests-global/command-create-help/snap.txt

@@ -9,6 +9,9 @@ Arguments:
             - Remote: vite, @tanstack/start, create-next-app,
               create-nuxt, github:user/repo, https://github.com/user/template-repo, etc.
             - Local: @company/generator-*, ./tools/create-ui-component
+            - Org scope: @your-org → picker from @your-org/create's vp.templates manifest
+            - Org entry: @your-org/web → manifest entry "web" (falls back to @your-org/create-web)
+            When omitted, uses `create.defaultTemplate` from vite.config.ts if set.
 
 Options:
   --directory DIR         Target directory for the generated project.
@@ -49,6 +52,10 @@ Examples:
   vp create github:user/repo
   vp create https://github.com/user/template-repo
 
+  # Pick from an org that publishes @scope/create with vp.templates
+  vp create @your-org # interactive picker
+  vp create @your-org/web # direct selection
+
 Documentation: https://viteplus.dev/guide/create
 
 
@@ -63,6 +70,9 @@ Arguments:
             - Remote: vite, @tanstack/start, create-next-app,
               create-nuxt, github:user/repo, https://github.com/user/template-repo, etc.
             - Local: @company/generator-*, ./tools/create-ui-component
+            - Org scope: @your-org → picker from @your-org/create's vp.templates manifest
+            - Org entry: @your-org/web → manifest entry "web" (falls back to @your-org/create-web)
+            When omitted, uses `create.defaultTemplate` from vite.config.ts if set.
 
 Options:
   --directory DIR         Target directory for the generated project.
@@ -103,6 +113,10 @@ Examples:
   vp create github:user/repo
   vp create https://github.com/user/template-repo
 
+  # Pick from an org that publishes @scope/create with vp.templates
+  vp create @your-org # interactive picker
+  vp create @your-org/web # direct selection
+
 Documentation: https://viteplus.dev/guide/create
 
 
@@ -117,6 +131,9 @@ Arguments:
             - Remote: vite, @tanstack/start, create-next-app,
               create-nuxt, github:user/repo, https://github.com/user/template-repo, etc.
             - Local: @company/generator-*, ./tools/create-ui-component
+            - Org scope: @your-org → picker from @your-org/create's vp.templates manifest
+            - Org entry: @your-org/web → manifest entry "web" (falls back to @your-org/create-web)
+            When omitted, uses `create.defaultTemplate` from vite.config.ts if set.
 
 Options:
   --directory DIR         Target directory for the generated project.
@@ -157,5 +174,9 @@ Examples:
   vp create github:user/repo
   vp create https://github.com/user/template-repo
 
+  # Pick from an org that publishes @scope/create with vp.templates
+  vp create @your-org # interactive picker
+  vp create @your-org/web # direct selection
+
 Documentation: https://viteplus.dev/guide/create
 

packages/cli/snap-tests-global/new-check/snap.txt

@@ -9,6 +9,9 @@ Arguments:
             - Remote: vite, @tanstack/start, create-next-app,
               create-nuxt, github:user/repo, https://github.com/user/template-repo, etc.
             - Local: @company/generator-*, ./tools/create-ui-component
+            - Org scope: @your-org → picker from @your-org/create's vp.templates manifest
+            - Org entry: @your-org/web → manifest entry "web" (falls back to @your-org/create-web)
+            When omitted, uses `create.defaultTemplate` from vite.config.ts if set.
 
 Options:
   --directory DIR         Target directory for the generated project.
@@ -49,6 +52,10 @@ Examples:
   vp create github:user/repo
   vp create https://github.com/user/template-repo
 
+  # Pick from an org that publishes @scope/create with vp.templates
+  vp create @your-org # interactive picker
+  vp create @your-org/web # direct selection
+
 Documentation: https://viteplus.dev/guide/create
 
 

packages/cli/snap-tests/create-org-bundled/mock-manifest.json

@@ -1,12 +1,12 @@
 {
-  "@acme/create": {
-    "name": "@acme/create",
+  "@your-org/create": {
+    "name": "@your-org/create",
     "dist-tags": { "latest": "1.0.0" },
     "versions": {
       "1.0.0": {
         "version": "1.0.0",
         "dist": {
-          "tarball": "{REGISTRY}/@acme/create/-/create-1.0.0.tgz",
+          "tarball": "{REGISTRY}/@your-org/create/-/create-1.0.0.tgz",
           "integrity": "sha512-h4Q9x+aUa2RUJGBe7JCZnWpGMyd8VHXPfL9+EBxrA2EWRV8rlmMCP45B3woZ8xA2fmkE/jUy1W7OM2GCjoPWQA=="
         },
         "vp": {

packages/cli/snap-tests/create-org-bundled/mock-server.mjs

@@ -1,6 +1,6 @@
 // Minimal mock npm registry used by `create-org-*` snap-tests.
 //
-// Reads `./mock-manifest.json` (keyed by URL path, e.g. `"@acme/create"`) and
+// Reads `./mock-manifest.json` (keyed by URL path, e.g. `"@your-org/create"`) and
 // optionally serves `.tgz` tarballs from `./tarballs/<name>`. Picks an
 // ephemeral port, sets `NPM_CONFIG_REGISTRY` on the child environment, spawns
 // the wrapped command, and tears down when the child exits.

packages/cli/snap-tests/create-org-bundled/snap.txt

@@ -1,6 +1,6 @@
-> node mock-server.mjs -- vp create @acme/demo --no-interactive --directory my-demo-app # bundled template: extract tarball, copy subdir
+> node mock-server.mjs -- vp create @your-org/demo --no-interactive --directory my-demo-app # bundled template: extract tarball, copy subdir
 
-selected 'demo' from @acme/create
+selected 'demo' from @your-org/create
 ◇ Scaffolded my-demo-app
 • Node <semver>  pnpm <semver>
 → Next: cd my-demo-app && vp run

packages/cli/snap-tests/create-org-bundled/steps.json

@@ -1,6 +1,6 @@
 {
   "commands": [
-    "node mock-server.mjs -- vp create @acme/demo --no-interactive --directory my-demo-app # bundled template: extract tarball, copy subdir",
+    "node mock-server.mjs -- vp create @your-org/demo --no-interactive --directory my-demo-app # bundled template: extract tarball, copy subdir",
     "cat my-demo-app/package.json # verify package.json name was rewritten",
     "cat my-demo-app/src/index.ts # verify bundled source copied",
     "ls my-demo-app/README.md # verify README copied"

packages/cli/snap-tests/create-org-invalid-manifest/mock-manifest.json

@@ -1,12 +1,12 @@
 {
-  "@acme/create": {
-    "name": "@acme/create",
+  "@your-org/create": {
+    "name": "@your-org/create",
     "dist-tags": { "latest": "1.0.0" },
     "versions": {
       "1.0.0": {
         "version": "1.0.0",
         "dist": {
-          "tarball": "{REGISTRY}/@acme/create/-/create-1.0.0.tgz",
+          "tarball": "{REGISTRY}/@your-org/create/-/create-1.0.0.tgz",
           "integrity": "sha512-fake"
         },
         "vp": {

packages/cli/snap-tests/create-org-invalid-manifest/mock-server.mjs

@@ -1,6 +1,6 @@
 // Minimal mock npm registry used by `create-org-*` snap-tests.
 //
-// Reads `./mock-manifest.json` (keyed by URL path, e.g. `"@acme/create"`) and
+// Reads `./mock-manifest.json` (keyed by URL path, e.g. `"@your-org/create"`) and
 // optionally serves `.tgz` tarballs from `./tarballs/<name>`. Picks an
 // ephemeral port, sets `NPM_CONFIG_REGISTRY` on the child environment, spawns
 // the wrapped command, and tears down when the child exits.