From c7a5c7cf5de1a6b636ef8222c38af0707ddb9cfd Mon Sep 17 00:00:00 2001
From: mshanemc <shane.mclaughlin@salesforce.com>
Date: Tue, 12 Dec 2023 16:31:16 -0600
Subject: [PATCH 1/3] chore: bump things

---
 package.json | 14 +++++-----
 yarn.lock    | 76 ++++++++++++++++++++++++++++++++++++++++++----------
 2 files changed, 69 insertions(+), 21 deletions(-)

diff --git a/package.json b/package.json
index 6e4f7e44..7a13b53d 100644
--- a/package.json
+++ b/package.json
@@ -5,17 +5,17 @@
   "author": "Salesforce",
   "bugs": "https://github.com/salesforcecli/plugin-templates/issues",
   "dependencies": {
-    "@oclif/core": "^3.11.0",
-    "@salesforce/core": "^6.2.2",
-    "@salesforce/sf-plugins-core": "^5.0.3",
-    "@salesforce/templates": "^59.0.2",
+    "@oclif/core": "^3.14.1",
+    "@salesforce/core": "^6.4.1",
+    "@salesforce/sf-plugins-core": "^5.0.8",
+    "@salesforce/templates": "^59.0.4",
     "yeoman-environment": "^3",
     "yeoman-generator": "^5"
   },
   "devDependencies": {
     "@oclif/plugin-command-snapshot": "^5.0.3",
     "@salesforce/cli-plugins-testkit": "^5.1.1",
-    "@salesforce/dev-scripts": "^8.1.0",
+    "@salesforce/dev-scripts": "^8.1.1",
     "@salesforce/plugin-command-reference": "^3.0.51",
     "@types/yeoman-assert": "^3.1.4",
     "@types/yeoman-environment": "^2.10.9",
@@ -23,8 +23,8 @@
     "eslint-plugin-sf-plugin": "^1.16.15",
     "oclif": "^4.0.4",
     "shx": "^0.3.4",
-    "ts-node": "^10.9.1",
-    "typescript": "^5.2.2",
+    "ts-node": "^10.9.2",
+    "typescript": "^5.3.3",
     "yeoman-assert": "^3.1.1",
     "yeoman-test": "^6.3.0"
   },
diff --git a/yarn.lock b/yarn.lock
index 20b19e37..4f19bf21 100644
--- a/yarn.lock
+++ b/yarn.lock
@@ -768,7 +768,7 @@
     wordwrap "^1.0.0"
     wrap-ansi "^7.0.0"
 
-"@oclif/core@^3.0.4", "@oclif/core@^3.10.8", "@oclif/core@^3.11.0", "@oclif/core@^3.13.1", "@oclif/core@^3.14.1", "@oclif/core@^3.3.1":
+"@oclif/core@^3.0.4", "@oclif/core@^3.10.8", "@oclif/core@^3.13.1", "@oclif/core@^3.14.1", "@oclif/core@^3.3.1":
   version "3.14.1"
   resolved "https://registry.yarnpkg.com/@oclif/core/-/core-3.14.1.tgz#634fc96124068e47b720d62f3b278d818a07495e"
   integrity sha512-HLFL2s45DFdqYI2CFjVS/CIQ4cQ4yZqH0XqO9nnwcRWYboz2rEW/vLmidjIYGDjh6xA/k5psiAL3O1KEjqSHuQ==
@@ -964,7 +964,7 @@
     strip-ansi "6.0.1"
     ts-retry-promise "^0.7.1"
 
-"@salesforce/core@^5.3.19", "@salesforce/core@^5.3.20":
+"@salesforce/core@^5.3.20":
   version "5.3.20"
   resolved "https://registry.yarnpkg.com/@salesforce/core/-/core-5.3.20.tgz#4e934d4551bb70423cb1c4115615bc41cffca41e"
   integrity sha512-y+O6O2c8OYFDrAy2qsG+pAcNxoyL14nmBXcBRRcYA7Huj8ikK+aLJK84PuVAYdQz+hNwImQF+69IWtDkpK4Irg==
@@ -1012,15 +1012,39 @@
     semver "^7.5.4"
     ts-retry-promise "^0.7.1"
 
+"@salesforce/core@^6.4.1":
+  version "6.4.1"
+  resolved "https://registry.yarnpkg.com/@salesforce/core/-/core-6.4.1.tgz#27edd083b62ee96d6270b60da6dfb959bff1a0a5"
+  integrity sha512-Bn/Pox5JLeVBg35zgSmtNU+f9wdOaa7a/hmCIvQibci1dpKtLGUmSpdHibWR6zHag8ZoRkueea7zuqEjYzECyA==
+  dependencies:
+    "@salesforce/kit" "^3.0.15"
+    "@salesforce/schemas" "^1.6.1"
+    "@salesforce/ts-types" "^2.0.9"
+    "@types/semver" "^7.5.6"
+    ajv "^8.12.0"
+    change-case "^4.1.2"
+    faye "^1.4.0"
+    form-data "^4.0.0"
+    js2xmlparser "^4.0.1"
+    jsforce "^2.0.0-beta.29"
+    jsonwebtoken "9.0.2"
+    jszip "3.10.1"
+    pino "^8.16.2"
+    pino-abstract-transport "^1.1.0"
+    pino-pretty "^10.2.3"
+    proper-lockfile "^4.1.2"
+    semver "^7.5.4"
+    ts-retry-promise "^0.7.1"
+
 "@salesforce/dev-config@^4.1.0":
   version "4.1.0"
   resolved "https://registry.yarnpkg.com/@salesforce/dev-config/-/dev-config-4.1.0.tgz#e529576466d074e7a5f1441236510fef123da01e"
   integrity sha512-2iDDepiIwjXHS5IVY7pwv8jMo4xWosJ7p/UTj+lllpB/gnJiYLhjJPE4Z3FCGFKyvfg5jGaimCd8Ca6bLGsCQA==
 
-"@salesforce/dev-scripts@^8.1.0":
-  version "8.1.0"
-  resolved "https://registry.yarnpkg.com/@salesforce/dev-scripts/-/dev-scripts-8.1.0.tgz#0310dc9fb4104637a237876161a40331dd382e9f"
-  integrity sha512-lA5uJMwfKKrbv+JMCxX8aOrwE1ihlmUfAy8SVCgBSaHNckRBDQP2zIM7S03zoXFSpUtebCndo1ODQxw+zVrK3g==
+"@salesforce/dev-scripts@^8.1.1":
+  version "8.1.1"
+  resolved "https://registry.yarnpkg.com/@salesforce/dev-scripts/-/dev-scripts-8.1.1.tgz#a54733057712706b08fc5abcdccad336be01fea3"
+  integrity sha512-pYf8eMhv/OLTUtQcNZkUXMioInQTwNnHuiePGbhcMb2KR41Ynk63sdLWZoGDSc82c1FX0cJfY4yrNMIMpEGQjw==
   dependencies:
     "@commitlint/cli" "^17.1.2"
     "@commitlint/config-conventional" "^17.1.0"
@@ -1043,7 +1067,7 @@
     shelljs "^0.8.5"
     sinon "10.0.0"
     source-map-support "^0.5.21"
-    ts-node "^10.9.1"
+    ts-node "^10.9.2"
     typedoc "^0.25.3"
     typedoc-plugin-missing-exports "0.23.0"
     typescript "^4.9.5"
@@ -1081,7 +1105,7 @@
   resolved "https://registry.yarnpkg.com/@salesforce/schemas/-/schemas-1.6.1.tgz#7d1c071e1e509ca9d2d8a6e48ac7447dd67a534d"
   integrity sha512-eVy947ZMxCJReKJdgfddUIsBIbPTa/i8RwQGwxq4/ss38H5sLOAeSTaun9V7HpJ1hkpDznWKfgzYvjsst9K6ig==
 
-"@salesforce/sf-plugins-core@^5.0.3", "@salesforce/sf-plugins-core@^5.0.5":
+"@salesforce/sf-plugins-core@^5.0.5", "@salesforce/sf-plugins-core@^5.0.8":
   version "5.0.8"
   resolved "https://registry.yarnpkg.com/@salesforce/sf-plugins-core/-/sf-plugins-core-5.0.8.tgz#af023ba5c9182ab277d738e6836267aa874a4dcb"
   integrity sha512-NvG3E61dVzORn86bPUh9cOPCmNZPfqzjS/ShMpyu2Cpjwr3zLYAlXSqH4kg0hQUW1D/M5sAck6XcUhwMpHh5yQ==
@@ -1094,12 +1118,12 @@
     chalk "^4"
     inquirer "^8.2.5"
 
-"@salesforce/templates@^59.0.2":
-  version "59.0.2"
-  resolved "https://registry.yarnpkg.com/@salesforce/templates/-/templates-59.0.2.tgz#4a0864ecde135d5b4bb0c71c5acad4ce238d761a"
-  integrity sha512-vCiRJS8q8XMn4gCCVQEyxIaeQ34MSpDsy6lCnSwJOqx5e9doxK+53BxAbzdFH+iy4Ze6bOESjx4xNZg0AtT8KA==
+"@salesforce/templates@^59.0.4":
+  version "59.0.4"
+  resolved "https://registry.yarnpkg.com/@salesforce/templates/-/templates-59.0.4.tgz#65cf640d528c244de2c98aafcd4224fb59726435"
+  integrity sha512-4Z4c01WjMLU+4y3zL1XoeJWtUARAqNsQ3GxvTp5u0AnKuIqGFKh/SXyibs6YoYcBfI8sW7zFXfM2NRyKYeeUOg==
   dependencies:
-    "@salesforce/core" "^5.3.19"
+    "@salesforce/core" "^5.3.20"
     "@salesforce/kit" "^3.0.15"
     got "^11.8.2"
     hpagent "^1.2.0"
@@ -7593,6 +7617,25 @@ ts-node@^10.8.1, ts-node@^10.9.1:
     v8-compile-cache-lib "^3.0.1"
     yn "3.1.1"
 
+ts-node@^10.9.2:
+  version "10.9.2"
+  resolved "https://registry.yarnpkg.com/ts-node/-/ts-node-10.9.2.tgz#70f021c9e185bccdca820e26dc413805c101c71f"
+  integrity sha512-f0FFpIdcHgn8zcPSbf1dRevwt047YMnaiJM3u2w2RewrB+fob/zePZcrOyQoLMMO7aBIddLcQIEK5dYjkLnGrQ==
+  dependencies:
+    "@cspotcode/source-map-support" "^0.8.0"
+    "@tsconfig/node10" "^1.0.7"
+    "@tsconfig/node12" "^1.0.7"
+    "@tsconfig/node14" "^1.0.0"
+    "@tsconfig/node16" "^1.0.2"
+    acorn "^8.4.1"
+    acorn-walk "^8.1.1"
+    arg "^4.1.0"
+    create-require "^1.1.0"
+    diff "^4.0.1"
+    make-error "^1.1.1"
+    v8-compile-cache-lib "^3.0.1"
+    yn "3.1.1"
+
 ts-retry-promise@^0.7.1:
   version "0.7.1"
   resolved "https://registry.yarnpkg.com/ts-retry-promise/-/ts-retry-promise-0.7.1.tgz#176d6eee6415f07b6c7c286d3657355e284a6906"
@@ -7744,7 +7787,7 @@ typedoc@^0.25.3:
     minimatch "^9.0.3"
     shiki "^0.14.1"
 
-"typescript@^4.6.4 || ^5.2.2", typescript@^5.2.2, typescript@~5.2.2:
+"typescript@^4.6.4 || ^5.2.2", typescript@~5.2.2:
   version "5.2.2"
   resolved "https://registry.yarnpkg.com/typescript/-/typescript-5.2.2.tgz#5ebb5e5a5b75f085f22bc3f8460fba308310fa78"
   integrity sha512-mI4WrpHsbCIcwT9cF4FZvr80QUeKvsUsUvKDoR+X/7XHQH98xYD8YHZg7ANtz2GtZt/CBq2QJ0thkGJMHfqc1w==
@@ -7754,6 +7797,11 @@ typescript@^4.9.5:
   resolved "https://registry.yarnpkg.com/typescript/-/typescript-4.9.5.tgz#095979f9bcc0d09da324d58d03ce8f8374cbe65a"
   integrity sha512-1FXk9E2Hm+QzZQ7z+McJiHL4NW1F2EzMu9Nq9i3zAaGqibafqYwCVU6WyWAuyQRRzOlxou8xZSyXLEN8oKj24g==
 
+typescript@^5.3.3:
+  version "5.3.3"
+  resolved "https://registry.yarnpkg.com/typescript/-/typescript-5.3.3.tgz#b3ce6ba258e72e6305ba66f5c9b452aaee3ffe37"
+  integrity sha512-pXWcraxM0uxAS+tN0AG/BF2TyqmHO014Z070UsJ+pFvYuRSq8KH8DmWpnbXe0pEPDHXZV3FcAbJkijJ5oNEnWw==
+
 uglify-js@^3.1.4:
   version "3.17.4"
   resolved "https://registry.yarnpkg.com/uglify-js/-/uglify-js-3.17.4.tgz#61678cf5fa3f5b7eb789bb345df29afb8257c22c"

From 2723809945798ce62a704efb848134f8ba56cd0f Mon Sep 17 00:00:00 2001
From: mshanemc <shane.mclaughlin@salesforce.com>
Date: Tue, 12 Dec 2023 16:32:05 -0600
Subject: [PATCH 2/3] chore: lockfile

---
 yarn.lock | 63 +++++++++----------------------------------------------
 1 file changed, 10 insertions(+), 53 deletions(-)

diff --git a/yarn.lock b/yarn.lock
index 4f19bf21..0035ce08 100644
--- a/yarn.lock
+++ b/yarn.lock
@@ -988,31 +988,7 @@
     semver "^7.5.4"
     ts-retry-promise "^0.7.1"
 
-"@salesforce/core@^6.2.2", "@salesforce/core@^6.4.0":
-  version "6.4.0"
-  resolved "https://registry.yarnpkg.com/@salesforce/core/-/core-6.4.0.tgz#09e856194c8dad5bd0d86e271e84c3c47304f508"
-  integrity sha512-zbUuOll6RnaOyO6vHGjaO6mv2SBimu2JzInubBrbx+bgw5KFVT0y+OrN0gEhBPS94VoC9/N6ZRKve+vQ82zmmA==
-  dependencies:
-    "@salesforce/kit" "^3.0.15"
-    "@salesforce/schemas" "^1.6.1"
-    "@salesforce/ts-types" "^2.0.9"
-    "@types/semver" "^7.5.6"
-    ajv "^8.12.0"
-    change-case "^4.1.2"
-    faye "^1.4.0"
-    form-data "^4.0.0"
-    js2xmlparser "^4.0.1"
-    jsforce "^2.0.0-beta.29"
-    jsonwebtoken "9.0.2"
-    jszip "3.10.1"
-    pino "^8.16.2"
-    pino-abstract-transport "^1.1.0"
-    pino-pretty "^10.2.3"
-    proper-lockfile "^4.1.2"
-    semver "^7.5.4"
-    ts-retry-promise "^0.7.1"
-
-"@salesforce/core@^6.4.1":
+"@salesforce/core@^6.2.2", "@salesforce/core@^6.4.0", "@salesforce/core@^6.4.1":
   version "6.4.1"
   resolved "https://registry.yarnpkg.com/@salesforce/core/-/core-6.4.1.tgz#27edd083b62ee96d6270b60da6dfb959bff1a0a5"
   integrity sha512-Bn/Pox5JLeVBg35zgSmtNU+f9wdOaa7a/hmCIvQibci1dpKtLGUmSpdHibWR6zHag8ZoRkueea7zuqEjYzECyA==
@@ -7598,26 +7574,7 @@ ts-json-schema-generator@^1.4.0:
     safe-stable-stringify "^2.4.3"
     typescript "~5.2.2"
 
-ts-node@^10.8.1, ts-node@^10.9.1:
-  version "10.9.1"
-  resolved "https://registry.yarnpkg.com/ts-node/-/ts-node-10.9.1.tgz#e73de9102958af9e1f0b168a6ff320e25adcff4b"
-  integrity sha512-NtVysVPkxxrwFGUUxGYhfux8k78pQB3JqYBXlLRZgdGUqTO5wU/UyHop5p70iEbGhB7q5KmiZiU0Y3KlJrScEw==
-  dependencies:
-    "@cspotcode/source-map-support" "^0.8.0"
-    "@tsconfig/node10" "^1.0.7"
-    "@tsconfig/node12" "^1.0.7"
-    "@tsconfig/node14" "^1.0.0"
-    "@tsconfig/node16" "^1.0.2"
-    acorn "^8.4.1"
-    acorn-walk "^8.1.1"
-    arg "^4.1.0"
-    create-require "^1.1.0"
-    diff "^4.0.1"
-    make-error "^1.1.1"
-    v8-compile-cache-lib "^3.0.1"
-    yn "3.1.1"
-
-ts-node@^10.9.2:
+ts-node@^10.8.1, ts-node@^10.9.1, ts-node@^10.9.2:
   version "10.9.2"
   resolved "https://registry.yarnpkg.com/ts-node/-/ts-node-10.9.2.tgz#70f021c9e185bccdca820e26dc413805c101c71f"
   integrity sha512-f0FFpIdcHgn8zcPSbf1dRevwt047YMnaiJM3u2w2RewrB+fob/zePZcrOyQoLMMO7aBIddLcQIEK5dYjkLnGrQ==
@@ -7787,20 +7744,20 @@ typedoc@^0.25.3:
     minimatch "^9.0.3"
     shiki "^0.14.1"
 
-"typescript@^4.6.4 || ^5.2.2", typescript@~5.2.2:
-  version "5.2.2"
-  resolved "https://registry.yarnpkg.com/typescript/-/typescript-5.2.2.tgz#5ebb5e5a5b75f085f22bc3f8460fba308310fa78"
-  integrity sha512-mI4WrpHsbCIcwT9cF4FZvr80QUeKvsUsUvKDoR+X/7XHQH98xYD8YHZg7ANtz2GtZt/CBq2QJ0thkGJMHfqc1w==
+"typescript@^4.6.4 || ^5.2.2", typescript@^5.3.3:
+  version "5.3.3"
+  resolved "https://registry.yarnpkg.com/typescript/-/typescript-5.3.3.tgz#b3ce6ba258e72e6305ba66f5c9b452aaee3ffe37"
+  integrity sha512-pXWcraxM0uxAS+tN0AG/BF2TyqmHO014Z070UsJ+pFvYuRSq8KH8DmWpnbXe0pEPDHXZV3FcAbJkijJ5oNEnWw==
 
 typescript@^4.9.5:
   version "4.9.5"
   resolved "https://registry.yarnpkg.com/typescript/-/typescript-4.9.5.tgz#095979f9bcc0d09da324d58d03ce8f8374cbe65a"
   integrity sha512-1FXk9E2Hm+QzZQ7z+McJiHL4NW1F2EzMu9Nq9i3zAaGqibafqYwCVU6WyWAuyQRRzOlxou8xZSyXLEN8oKj24g==
 
-typescript@^5.3.3:
-  version "5.3.3"
-  resolved "https://registry.yarnpkg.com/typescript/-/typescript-5.3.3.tgz#b3ce6ba258e72e6305ba66f5c9b452aaee3ffe37"
-  integrity sha512-pXWcraxM0uxAS+tN0AG/BF2TyqmHO014Z070UsJ+pFvYuRSq8KH8DmWpnbXe0pEPDHXZV3FcAbJkijJ5oNEnWw==
+typescript@~5.2.2:
+  version "5.2.2"
+  resolved "https://registry.yarnpkg.com/typescript/-/typescript-5.2.2.tgz#5ebb5e5a5b75f085f22bc3f8460fba308310fa78"
+  integrity sha512-mI4WrpHsbCIcwT9cF4FZvr80QUeKvsUsUvKDoR+X/7XHQH98xYD8YHZg7ANtz2GtZt/CBq2QJ0thkGJMHfqc1w==
 
 uglify-js@^3.1.4:
   version "3.17.4"

From ee573d240bad0731a40077ebe48d52c063df3138 Mon Sep 17 00:00:00 2001
From: mshanemc <shane.mclaughlin@salesforce.com>
Date: Tue, 12 Dec 2023 18:13:10 -0600
Subject: [PATCH 3/3] chore: update readme for broken links

---
 README.md | 804 ++++++++++++++++++++++++++++++++++++++----------------
 1 file changed, 569 insertions(+), 235 deletions(-)

diff --git a/README.md b/README.md
index fb488974..df1cfcd0 100644
--- a/README.md
+++ b/README.md
@@ -116,396 +116,730 @@ Congrats, you are debugging!
 
 # Commands
 
-A list of the available commands
+<!-- commands -->
 
-#### `sfdx force:apex:class:create`
+- [`sf analytics generate template`](#sf-analytics-generate-template)
+- [`sf apex generate class`](#sf-apex-generate-class)
+- [`sf apex generate trigger`](#sf-apex-generate-trigger)
+- [`sf lightning generate app`](#sf-lightning-generate-app)
+- [`sf lightning generate component`](#sf-lightning-generate-component)
+- [`sf lightning generate event`](#sf-lightning-generate-event)
+- [`sf lightning generate interface`](#sf-lightning-generate-interface)
+- [`sf lightning generate test`](#sf-lightning-generate-test)
+- [`sf project generate`](#sf-project-generate)
+- [`sf static-resource generate`](#sf-static-resource-generate)
+- [`sf visualforce generate component`](#sf-visualforce-generate-component)
+- [`sf visualforce generate page`](#sf-visualforce-generate-page)
 
-create an Apex class
+## `sf analytics generate template`
+
+Generate a simple Analytics template.
 
 ```
 USAGE
-  $ sfdx force:apex:class:create -n <string> [-d <string>] [-t <string>] [--apiversion <string>] [--json] [--loglevel
-  trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
+  $ sf analytics generate template -n <value> [--json] [-d <value>] [--api-version <value>]
 
-OPTIONS
-  -d, --outputdir=outputdir                                                         folder for saving the created files
+FLAGS
+  -d, --output-dir=<value>   [default: .] Directory for saving the created files.
+  -n, --name=<value>         (required) Name of the Analytics template.
+      --api-version=<value>  Override the api version used for api requests made by this command
 
-  -n, --classname=classname(required)                                               name of the generated Apex class
+GLOBAL FLAGS
+  --json  Format output as json.
 
-  -t, --template=ApexException|ApexUnitTest|DefaultApexClass|InboundEmailService    [default: DefaultApexClass] template
-                                                                                    to use for file creation
+DESCRIPTION
+  Generate a simple Analytics template.
 
-  --apiversion=apiversion                                                           override the api version used for
-                                                                                    api requests made by this command
+  The metadata files associated with the Analytics template must be contained in a parent directory called
+  "waveTemplates" in your package directory. Either run this command from an existing directory of this name, or use the
+  --output-dir flag to generate one or point to an existing one.
 
-  --json                                                                            format output as json
+ALIASES
+  $ sf force analytics template create
 
-  --loglevel=(trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL)  [default: warn] logging level for
-                                                                                    this command invocation
+EXAMPLES
+  Generate the metadata files for a simple Analytics template file called myTemplate in the
+  force-app/main/default/waveTemplates directory:
 
-DESCRIPTION
-  If not supplied, the apiversion, template, and outputdir use default values.
-  The outputdir can be an absolute path or relative to the current working directory.
+    $ sf analytics generate template --name myTemplate --output-dir force-app/main/default/waveTemplates
 
-EXAMPLES
-  $ sfdx force:apex:class:create -n MyClass
-  $ sfdx force:apex:class:create -n MyClass -d classes
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory for saving the created files.
+
+    The location can be an absolute path or relative to the current working directory. The default is the current
+    directory.
 ```
 
-_See code: [src/commands/force/apex/class/create.ts](https://github.com/salesforcecli/plugin-templates/blob/master/src/commands/force/apex/class/create.ts)_
+_See code: [src/commands/analytics/generate/template.ts](https://github.com/salesforcecli/plugin-templates/blob/main/src/commands/analytics/generate/template.ts)_
 
-#### `sfdx force:apex:trigger:create`
+## `sf apex generate class`
 
-create an Apex trigger
+Generate an Apex class.
 
 ```
 USAGE
-  $ sfdx force:apex:trigger:create -n <string> [-d <string>] [-e <string>] [-s <string>] [-t <string>] [--apiversion
-  <string>] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
+  $ sf apex generate class -n <value> [--json] [-t ApexException|ApexUnitTest|DefaultApexClass|InboundEmailService] [-d
+    <value>] [--api-version <value>]
 
-OPTIONS
-  -d, --outputdir=outputdir                                                           folder for saving the created files
+FLAGS
+  -d, --output-dir=<value>   [default: .] Directory for saving the created files.
+  -n, --name=<value>         (required) Name of the generated Apex class.
+  -t, --template=<option>    [default: DefaultApexClass] Template to use for file creation.
+                             <options: ApexException|ApexUnitTest|DefaultApexClass|InboundEmailService>
+      --api-version=<value>  Override the api version used for api requests made by this command
 
-  -e, --triggerevents=before insert|before update|before delete|after insert|after update|after delete|after undelete
-                                                                                      [default: before insert] events that                                                                                            fire the trigger
+GLOBAL FLAGS
+  --json  Format output as json.
 
-  -n, --triggername=triggername                                                       (required) name of the generated Apex                                                                                          trigger
+DESCRIPTION
+  Generate an Apex class.
 
-  -s, --sobject=sobject                                                               [default: SOBJECT] sObject to create a                                                                                          trigger on
+  Generates the Apex *.cls file and associated metadata file. These files must be contained in a parent directory called
+  "classes" in your package directory. Either run this command from an existing directory of this name, or use the
+  --output-dir flag to generate one or point to an existing one.
 
-  -t, --template=ApexTrigger                                                          [default: ApexTrigger] template to use                                                                                          for file creation
+ALIASES
+  $ sf force apex class create
 
-  --apiversion=apiversion                                                             override the api version used for api                                                                                         requests made by this command
+EXAMPLES
+  Generate two metadata files associated with the MyClass Apex class (MyClass.cls and MyClass.cls-meta.xml) in the
+  current directory:
 
-  --json                                                                              format output as json
+    $ sf apex generate class --name MyClass
 
-  --loglevel=(trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL)    [default: warn] logging level for this                                                                                          command invocation
+  Similar to previous example, but generates the files in the "force-app/main/default/classes" directory:
 
-DESCRIPTION
-  If not supplied, the apiversion, template, and outputdir use default values.
-  The outputdir can be an absolute path or relative to the current working directory.
+    $ sf apex generate class --name MyClass --output-dir force-app/main/default/classes
 
-EXAMPLES
-  $ sfdx force:apex:trigger:create -n MyTrigger
-  $ sfdx force:apex:trigger:create -n MyTrigger -s Account -e 'before insert, after upsert'
-  $ sfdx force:apex:trigger:create -n MyTrigger -d triggers
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory for saving the created files.
+
+    The location can be an absolute path or relative to the current working directory. The default is the current
+    directory.
+
+  -n, --name=<value>  Name of the generated Apex class.
+
+    The name can be up to 40 characters and must start with a letter.
+
+  -t, --template=ApexException|ApexUnitTest|DefaultApexClass|InboundEmailService  Template to use for file creation.
+
+    Supplied parameter values or default values are filled into a copy of the template.
 ```
 
-_See code: [src/commands/force/apex/trigger/create.ts](https://github.com/salesforcecli/plugin-templates/blob/master/src/commands/force/apex/trigger/create.ts)_
+_See code: [src/commands/apex/generate/class.ts](https://github.com/salesforcecli/plugin-templates/blob/main/src/commands/apex/generate/class.ts)_
 
-#### `sfdx force:lightning:app:create`
+## `sf apex generate trigger`
 
-create a Lightning app
+Generate an Apex trigger.
 
 ```
 USAGE
-  $ sfdx force:lightning:app:create -n <string> [-d <string>] [-t <string>] [--apiversion <string>] [--json] [--loglevel
-  trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
+  $ sf apex generate trigger -n <value> [--json] [-t ApexTrigger] [-d <value>] [--api-version <value>] [-s <value>] [-e
+    before insert|before update|before delete|after insert|after update|after delete|after undelete]
+
+FLAGS
+  -d, --output-dir=<value>   [default: .] Directory for saving the created files.
+  -e, --event=<option>...    [default: before insert] Events that fire the trigger.
+                             <options: before insert|before update|before delete|after insert|after update|after
+                             delete|after undelete>
+  -n, --name=<value>         (required) Name of the generated Apex trigger
+  -s, --sobject=<value>      [default: SOBJECT] Salesforce object to generate a trigger on.
+  -t, --template=<option>    [default: ApexTrigger] Template to use for file creation.
+                             <options: ApexTrigger>
+      --api-version=<value>  Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --json  Format output as json.
 
-OPTIONS
-  -d, --outputdir=outputdir                                                         folder for saving the created files
+DESCRIPTION
+  Generate an Apex trigger.
 
-  -n, --appname=appname                                                             (required) name of the generated
-                                                                                    Lightning app
+  Generates the Apex trigger *.trigger file and associated metadata file. These files must be contained in a parent
+  directory called "triggers" in your package directory. Either run this command from an existing directory of this
+  name, or use the --output-dir flag to generate one or point to an existing one.
 
-  -t, --template=DefaultLightningApp                                                [default: DefaultLightningApp]
-                                                                                    template to use for file creation
+  If you don't specify the --sobject flag, the .trigger file contains the generic placeholder SOBJECT; replace it with
+  the Salesforce object you want to generate a trigger for. If you don't specify --event, "before insert" is used.
 
-  --apiversion=apiversion                                                           override the api version used for
-                                                                                    api requests made by this command
+ALIASES
+  $ sf force apex trigger create
 
-  --json                                                                            format output as json
+EXAMPLES
+  Generate two files associated with the MyTrigger Apex trigger (MyTrigger.trigger and MyTrigger.trigger-meta.xml) in
+  the current directory:
 
-  --loglevel=(trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL)  [default: warn] logging level for
-                                                                                    this command invocation
+    $ sf apex generate trigger --name MyTrigger
 
-DESCRIPTION
-  If not supplied, the apiversion, template, and outputdir use default values.
-  The outputdir can be an absolute path or relative to the current working directory.
-  If you don’t specify an outputdir, we create a subfolder in your current working directory with the name of your
-  bundle. For example, if the current working directory is force-app and your Lightning bundle is called myBundle, we
-  create force-app/myBundle/ to store the files in the bundle.
+  Similar to the previous example, but generate the files in the "force-app/main/default/triggers" directory:
 
-EXAMPLES
-  $ sfdx force:lightning:app:create -n myapp
-  $ sfdx force:lightning:app:create -n myapp -d aura
+    $ sf apex generate trigger --name MyTrigger --output-dir force-app/main/default/triggers
+
+  Generate files for a trigger that fires on the Account object before and after an insert:
+
+    $ sf apex generate trigger --name MyTrigger --sobject Account --event "before insert,after insert"
+
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory for saving the created files.
+
+    The location can be an absolute path or relative to the current working directory. The default is the current
+    directory.
+
+  -n, --name=<value>  Name of the generated Apex trigger
+
+    The name can be up to 40 characters and must start with a letter.
+
+  -t, --template=ApexTrigger  Template to use for file creation.
+
+    Supplied parameter values or default values are filled into a copy of the template.
 ```
 
-_See code: [src/commands/force/lightning/app/create.ts](https://github.com/salesforcecli/plugin-templates/blob/master/src/commands/force/lightning/app/create.ts)_
+_See code: [src/commands/apex/generate/trigger.ts](https://github.com/salesforcecli/plugin-templates/blob/main/src/commands/apex/generate/trigger.ts)_
 
-#### `sfdx force:lightning:component:create`
+## `sf lightning generate app`
 
-create a bundle for an Aura component or a Lightning web component
+Generate a Lightning App.
 
 ```
 USAGE
-  $ sfdx force:lightning:component:create -n <string> [-d <string>] [-t <string>] [--type <string>] [--apiversion
-  <string>] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
+  $ sf lightning generate app -n <value> [--json] [-t DefaultLightningApp] [-d <value>] [--api-version <value>]
 
-OPTIONS
-  -d, --outputdir=outputdir                                                         folder for saving the created files
+FLAGS
+  -d, --output-dir=<value>   [default: .] Directory for saving the created files.
+  -n, --name=<value>         (required) Name of the generated Lightning App.
+  -t, --template=<option>    [default: DefaultLightningApp] Template to use for file creation.
+                             <options: DefaultLightningApp>
+      --api-version=<value>  Override the api version used for api requests made by this command
 
-  -n, --componentname=componentname                                                 (required) name of the generated
-                                                                                    Lightning component
+GLOBAL FLAGS
+  --json  Format output as json.
 
-  -t, --template=                                                                   [default: DefaultLightningCmp]
-                                                                                    template to use for file creation
+DESCRIPTION
+  Generate a Lightning App.
 
-  --apiversion=apiversion                                                           override the api version used for
-                                                                                    api requests made by this command
+  Generates a Lightning App bundle in the specified directory or the current working directory. The bundle consists of
+  multiple files in a folder with the designated name.
 
-  --json                                                                            format output as json
+ALIASES
+  $ sf force lightning app create
 
-  --loglevel=(trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL)  [default: warn] logging level for
-                                                                                    this command invocation
+EXAMPLES
+  Generate the metadata files for a Lightning app bundle called "myapp" in the current directory:
 
-  --type=aura|lwc                                                                   [default: aura] type of the
-                                                                                    Lightning component
+    $ sf lightning generate app --name myapp
 
-DESCRIPTION
-  If not supplied, the apiversion, template, and outputdir use default values.
-  The outputdir can be an absolute path or relative to the current working directory.
-  If you don’t specify an outputdir, we create a subfolder in your current working directory with the name of your
-  bundle. For example, if the current working directory is force-app and your Lightning bundle is called myBundle, we
-  create force-app/myBundle/ to store the files in the bundle.
-  To create a Lightning web component, pass --type lwc to the command. If you don’t include a --type value, Salesforce
-  CLI creates an Aura component by default.
+  Similar to the previous example, but generate the files in the "force-app/main/default/aura" directory:
 
-EXAMPLES
-  $ sfdx force:lightning:component:create -n mycomponent
-  $ sfdx force:lightning:component:create -n mycomponent --type lwc
-  $ sfdx force:lightning:component:create -n mycomponent -d aura
-  $ sfdx force:lightning:component:create -n mycomponent --type lwc -d lwc
-```
+    $ sf lightning generate app --name myapp --output-dir force-app/main/default/aura
+
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory for saving the created files.
 
-_See code: [src/commands/force/lightning/component/create.ts](https://github.com/salesforcecli/plugin-templates/blob/master/src/commands/force/lightning/component/create.ts)_
+    The location can be an absolute path or relative to the current working directory. The default is the current
+    directory.
 
-#### `sfdx force:lightning:event:create`
+  -n, --name=<value>  Name of the generated Lightning App.
 
-create a Lightning event
+    The name can be up to 40 characters and must start with a letter.
 
+  -t, --template=DefaultLightningApp  Template to use for file creation.
+
+    Supplied parameter values or default values are filled into a copy of the template.
 ```
-USAGE
-  $ sfdx force:lightning:event:create -n <string> [-d <string>] [-t <string>] [--apiversion <string>] [--json]
-  [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
 
-OPTIONS
-  -d, --outputdir=outputdir                                                         folder for saving the created files
+_See code: [src/commands/lightning/generate/app.ts](https://github.com/salesforcecli/plugin-templates/blob/main/src/commands/lightning/generate/app.ts)_
 
-  -n, --eventname=eventname                                                         (required) name of the generated
-                                                                                    Lightning event
+## `sf lightning generate component`
 
-  -t, --template=DefaultLightningEvt                                                [default: DefaultLightningEvt]
-                                                                                    template to use for file creation
+Generate a bundle for an Aura component or a Lightning web component.
 
-  --apiversion=apiversion                                                           override the api version used for
-                                                                                    api requests made by this command
+```
+USAGE
+  $ sf lightning generate component -n <value> [--json] [-t default|analyticsDashboard|analyticsDashboardWithStep] [-d <value>]
+    [--api-version <value>] [--type aura|lwc]
 
-  --json                                                                            format output as json
+FLAGS
+  -d, --output-dir=<value>   [default: .] Directory for saving the created files.
+  -n, --name=<value>         (required) Name of the generated Lightning Component.
+  -t, --template=<option>    [default: default] Template to use for file creation.
+                             <options: default|analyticsDashboard|analyticsDashboardWithStep>
+      --api-version=<value>  Override the api version used for api requests made by this command
+      --type=<option>        [default: aura] Type of the component bundle.
+                             <options: aura|lwc>
 
-  --loglevel=(trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL)  [default: warn] logging level for
-                                                                                    this command invocation
+GLOBAL FLAGS
+  --json  Format output as json.
 
 DESCRIPTION
-  If not supplied, the apiversion, template, and outputdir use default values.
-  The outputdir can be an absolute path or relative to the current working directory.
-  If you don’t specify an outputdir, we create a subfolder in your current working directory with the name of your
-  bundle. For example, if the current working directory is force-app and your Lightning bundle is called myBundle, we
-  create force-app/myBundle/ to store the files in the bundle.
+  Generate a bundle for an Aura component or a Lightning web component.
+
+  Generates the bundle in the specified directory or the current working directory. The bundle consists of multiple
+  files in a directory with the designated name. Lightning web components are contained in the directory with name
+  "lwc", Aura components in "aura".
+
+  To generate a Lightning web component, pass "--type lwc" to the command. If you don’t specify --type, Salesforce CLI
+  generates an Aura component by default.
+
+ALIASES
+  $ sf force lightning component create
 
 EXAMPLES
-  $ sfdx force:lightning:app:create -n myevent
-  $ sfdx force:lightning:event:create -n myevent -d aura
-```
+  Generate the metadata files for an Aura component bundle in the current directory:
+
+    $ sf lightning generate component --name mycomponent
+
+  Generate a Lightning web component bundle in the current directory:
+
+    $ sf lightning generate component --name mycomponent --type lwc
+
+  Generate an Aura component bundle in the "force-app/main/default/aura" directory:
+
+    $ sf lightning generate component --name mycomponent --output-dir force-app/main/default/aura
+
+  Generate a Lightning web component bundle in the "force-app/main/default/lwc" directory:
+
+    $ sf lightning generate component --name mycomponent --type lwc --output-dir force-app/main/default/lwc
+
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory for saving the created files.
+
+    The location can be an absolute path or relative to the current working directory. The default is the current
+    directory.
 
-_See code: [src/commands/force/lightning/event/create.ts](https://github.com/salesforcecli/plugin-templates/blob/master/src/commands/force/lightning/event/create.ts)_
+  -n, --name=<value>  Name of the generated Lightning Component.
 
-#### `sfdx force:lightning:interface:create`
+    The name can be up to 40 characters and must start with a letter.
 
-create a Lightning interface
+  -t, --template=default|analyticsDashboard|analyticsDashboardWithStep  Template to use for file creation.
 
+    Supplied parameter values or default values are filled into a copy of the template.
 ```
-USAGE
-  $ sfdx force:lightning:interface:create -n <string> [-d <string>] [-t <string>] [--apiversion <string>] [--json]
-  [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
 
-OPTIONS
-  -d, --outputdir=outputdir                                                         folder for saving the created files
+_See code: [src/commands/lightning/generate/component.ts](https://github.com/salesforcecli/plugin-templates/blob/main/src/commands/lightning/generate/component.ts)_
 
-  -n, --interfacename=interfacename                                                 (required) name of the generated
-                                                                                    Lightning interface
+## `sf lightning generate event`
 
-  -t, --template=DefaultLightningIntf                                               [default: DefaultLightningIntf]
-                                                                                    template to use for file creation
+Generate a Lightning Event.
 
-  --apiversion=apiversion                                                           override the api version used for
-                                                                                    api requests made by this command
+```
+USAGE
+  $ sf lightning generate event -n <value> [--json] [-t DefaultLightningEvt] [-d <value>] [--api-version <value>]
 
-  --json                                                                            format output as json
+FLAGS
+  -d, --output-dir=<value>   [default: .] Directory for saving the created files.
+  -n, --name=<value>         (required) Name of the generated Lightning Event.
+  -t, --template=<option>    [default: DefaultLightningEvt] Template to use for file creation.
+                             <options: DefaultLightningEvt>
+      --api-version=<value>  Override the api version used for api requests made by this command
 
-  --loglevel=(trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL)  [default: warn] logging level for
-                                                                                    this command invocation
+GLOBAL FLAGS
+  --json  Format output as json.
 
 DESCRIPTION
-  If not supplied, the apiversion, template, and outputdir use default values.
-  The outputdir can be an absolute path or relative to the current working directory.
-  If you don’t specify an outputdir, we create a subfolder in your current working directory with the name of your
-  bundle. For example, if the current working directory is force-app and your Lightning bundle is called myBundle, we
-  create force-app/myBundle/ to store the files in the bundle.
+  Generate a Lightning Event.
+
+  Generates a Lightning Event bundle in the specified directory or the current working directory. The bundle consists of
+  multiple files in a folder with the designated name.
+
+ALIASES
+  $ sf force lightning event create
 
 EXAMPLES
-  $ sfdx force:lightning:interface:create -n myinterface
-  $ sfdx force:lightning:interface:create -n myinterface -d aura
+  Generate the metadata files for a Lightning event bundle called "myevent" in the current directory:
+
+    $ sf lightning generate event --name myevent
+
+  Similar to previous example, but generate the files in the "force-app/main/default/aura" directory:
+
+    $ sf lightning generate event --name myevent --output-dir force-app/main/default/aura
+
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory for saving the created files.
+
+    The location can be an absolute path or relative to the current working directory. The default is the current
+    directory.
+
+  -n, --name=<value>  Name of the generated Lightning Event.
+
+    The name can be up to 40 characters and must start with a letter.
+
+  -t, --template=DefaultLightningEvt  Template to use for file creation.
+
+    Supplied parameter values or default values are filled into a copy of the template.
 ```
 
-_See code: [src/commands/force/lightning/interface/create.ts](https://github.com/salesforcecli/plugin-templates/blob/master/src/commands/force/lightning/interface/create.ts)_
+_See code: [src/commands/lightning/generate/event.ts](https://github.com/salesforcecli/plugin-templates/blob/main/src/commands/lightning/generate/event.ts)_
 
-#### `sfdx force:lightning:test:create`
+## `sf lightning generate interface`
 
-create a Lightning test
+Generate a Lightning Interface.
 
 ```
 USAGE
-  $ sfdx force:lightning:test:create -n <string> [-d <string>] [-t <string>] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
+  $ sf lightning generate interface -n <value> [--json] [-t DefaultLightningIntf] [-d <value>] [--api-version <value>]
+
+FLAGS
+  -d, --output-dir=<value>   [default: .] Directory for saving the created files.
+  -n, --name=<value>         (required) Name of the generated Lightning Interface.
+  -t, --template=<option>    [default: DefaultLightningIntf] Template to use for file creation.
+                             <options: DefaultLightningIntf>
+      --api-version=<value>  Override the api version used for api requests made by this command
 
-OPTIONS
-  -d, --outputdir=outputdir                                                         folder for saving the created files
-  -n, --testname=testname                                                           (required) name of the generated Lightning test
-  -t, --template=DefaultLightningTest                                               [default: DefaultLightningTest] template to use for file creation
-  --json                                                                            format output as json
-  --loglevel=(trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL)  [default: warn] logging level for this command invocation
+GLOBAL FLAGS
+  --json  Format output as json.
 
 DESCRIPTION
-  The outputdir can be an absolute path or relative to the current working directory.
+  Generate a Lightning Interface.
+
+  Generates a Lightning Interface bundle in the specified directory or the current working directory. The bundle
+  consists of multiple files in a folder with the designated name.
+
+ALIASES
+  $ sf force lightning interface create
 
 EXAMPLES
-  $ sfdx force:lightning:test:create -n MyLightningTest
-  $ sfdx force:lightning:test:create -n MyLightningTest -d lightningTests
+  Generate the metadata files for a Lightning interface bundle called "myinterface" in the current directory:
+
+    $ sf lightning generate interface --name myinterface
+
+  Similar to the previous example but generate the files in the "force-app/main/default/aura" directory:
+
+    $ sf lightning generate interface --name myinterface --output-dir force-app/main/default/aura
+
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory for saving the created files.
+
+    The location can be an absolute path or relative to the current working directory. The default is the current
+    directory.
+
+  -n, --name=<value>  Name of the generated Lightning Interface.
+
+    The name can be up to 40 characters and must start with a letter.
+
+  -t, --template=DefaultLightningIntf  Template to use for file creation.
+
+    Supplied parameter values or default values are filled into a copy of the template.
 ```
 
-_See code: [src/commands/force/lightning/test/create.ts](https://github.com/salesforcecli/plugin-templates/blob/master/src/commands/force/lightning/test/create.ts)_
+_See code: [src/commands/lightning/generate/interface.ts](https://github.com/salesforcecli/plugin-templates/blob/main/src/commands/lightning/generate/interface.ts)_
 
-#### `sfdx force:project:create`
+## `sf lightning generate test`
 
-create a Salesforce DX project
+Generate a Lightning test.
 
 ```
 USAGE
-  $ sfdx force:project:create -n <string> [-d <string>] [-p <string>] [-s <string>] [-t <string>] [-x] [--json]
-  [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
+  $ sf lightning generate test -n <value> [--json] [-t DefaultLightningTest] [-d <value>] [--api-version <value>]
 
-OPTIONS
-  -d, --outputdir=outputdir                                                         folder for saving the created files
+FLAGS
+  -d, --output-dir=<value>   [default: .] Directory for saving the created files.
+  -n, --name=<value>         (required) Name of the generated Lightning Test.
+  -t, --template=<option>    [default: DefaultLightningTest] Template to use for file creation.
+                             <options: DefaultLightningTest>
+      --api-version=<value>  Override the api version used for api requests made by this command
 
-  -n, --projectname=projectname                                                     (required) name of the generated
-                                                                                    project
+GLOBAL FLAGS
+  --json  Format output as json.
 
-  -p, --defaultpackagedir=defaultpackagedir                                         [default: force-app] default package
-                                                                                    directory name
+DESCRIPTION
+  Generate a Lightning test.
 
-  -s, --namespace=namespace                                                         project associated namespace
+  Generates the test in the specified directory or the current working directory. The .resource file and associated
+  metadata file are generated.
 
-  -t, --template=standard|empty|analytics                                           [default: standard] template to use
-                                                                                    for file creation
+ALIASES
+  $ sf force lightning test create
 
-  -x, --manifest                                                                    generate a manifest (package.xml)
-                                                                                    for change-set based development
+EXAMPLES
+  Generate the metadata files for the Lightning test called MyLightningTest in the current directory:
 
-  --json                                                                            format output as json
+    $ sf lightning generate test --name MyLightningTest
 
-  --loglevel=(trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL)  [default: warn] logging level for
-                                                                                    this command invocation
+  Similar to the previous example but generate the files in the "force-app/main/default/lightningTests" directory:
 
-DESCRIPTION
-  Default values are used if the template, namespace, defaultpackagedir, and outputdir aren’t supplied.
-  The outputdir can be an absolute path or relative to the current working directory.
+    $ sf lightning generate test --name MyLightningTest --output-dir force-app/main/default/lightningTests
 
-EXAMPLES
-  $ sfdx force:project:create --projectname mywork
-  $ sfdx force:project:create --projectname mywork --defaultpackagedir myapp
-  $ sfdx force:project:create --projectname mywork --defaultpackagedir myapp --manifest
-  $ sfdx force:project:create --projectname mywork --template empty
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory for saving the created files.
+
+    The location can be an absolute path or relative to the current working directory. The default is the current
+    directory.
+
+  -n, --name=<value>  Name of the generated Lightning Test.
+
+    Name of the new Lightning test; can be up to 40 characters and must start with a letter.
+
+  -t, --template=DefaultLightningTest  Template to use for file creation.
+
+    Supplied parameter values or default values are filled into a copy of the template.
 ```
 
-_See code: [src/commands/force/project/create.ts](https://github.com/salesforcecli/plugin-templates/blob/master/src/commands/force/project/create.ts)_
+_See code: [src/commands/lightning/generate/test.ts](https://github.com/salesforcecli/plugin-templates/blob/main/src/commands/lightning/generate/test.ts)_
 
-#### `sfdx force:visualforce:component:create`
+## `sf project generate`
 
-create a Visualforce component
+Generate a Salesforce DX project.
 
 ```
 USAGE
-  $ sfdx force:visualforce:component:create -n <string> -l <string> [-d <string>] [-t <string>] [--apiversion <string>]
-  [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
+  $ sf project generate -n <value> [--json] [-t standard|empty|analytics] [-d <value>] [-s <value>] [-p <value>] [-x]
+    [--api-version <value>]
+
+FLAGS
+  -d, --output-dir=<value>           [default: .] Directory for saving the created files.
+  -n, --name=<value>                 (required) Name of the generated project.
+  -p, --default-package-dir=<value>  [default: force-app] Default package directory name.
+  -s, --namespace=<value>            Namespace associated with this project and any connected scratch orgs.
+  -t, --template=<option>            [default: standard] Template to use for project creation.
+                                     <options: standard|empty|analytics>
+  -x, --manifest                     Generate a manifest (package.xml) for change-set based development.
+      --api-version=<value>          Will set this version as sourceApiVersion in the sfdx-project.json file
+
+GLOBAL FLAGS
+  --json  Format output as json.
+
+DESCRIPTION
+  Generate a Salesforce DX project.
+
+  A Salesforce DX project has a specific structure and a configuration file (sfdx-project.json) that identifies the
+  directory as a Salesforce DX project. This command generates the necessary configuration files and directories to get
+  you started.
+
+  By default, the generated sfdx-project.json file sets the sourceApiVersion property to the default API version
+  currently used by Salesforce CLI. To specify a different version, set the apiVersion configuration variable. For
+  example: "sf config set apiVersion=57.0 --global".
+
+ALIASES
+  $ sf force project create
+
+EXAMPLES
+  Generate a project called "mywork":
+
+    $ sf project generate --name mywork
+
+  Similar to previous example, but generate the files in a directory called "myapp":
+
+    $ sf project generate --name mywork --default-package-dir myapp
+
+  Similar to prevoius example, but also generate a default package.xml manifest file:
+
+    $ sf project generate --name mywork --default-package-dir myapp --manifest
+
+  Generate a project with the minimum files and directories:
+
+    $ sf project generate --name mywork --template empty
+
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory for saving the created files.
 
-OPTIONS
-  -d, --outputdir=outputdir                                                         folder for saving the created files
+    The location can be an absolute path or relative to the current working directory. The default is the current
+    directory.
 
-  -l, --label=label                                                                 (required) Visualforce component
-                                                                                    label
+  -n, --name=<value>  Name of the generated project.
 
-  -n, --componentname=componentname                                                 (required) name of the generated
-                                                                                    Visualforce component
+    Generates a project directory with this name; any valid directory name is accepted. Also sets the "name" property in
+    the sfdx-project.json file to this name.
 
-  -t, --template=DefaultVFComponent                                                 [default: DefaultVFComponent]
-                                                                                    template to use for file creation
+  -p, --default-package-dir=<value>  Default package directory name.
 
-  --apiversion=apiversion                                                           override the api version used for
-                                                                                    api requests made by this command
+    Metadata items such as classes and Lightning bundles are placed inside this folder.
 
-  --json                                                                            format output as json
+  -t, --template=standard|empty|analytics  Template to use for project creation.
 
-  --loglevel=(trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL)  [default: warn] logging level for
-                                                                                    this command invocation
+    The template determines the sample configuration files and directories that this command generates. For example, the
+    empty template provides these files and directory to get you started.
+
+    - .forceignore
+    - config/project-scratch-def.json
+    - sfdx-project.json
+    - package.json
+    - force-app (basic source directory structure)
+
+    The standard template provides a complete force-app directory structure so you know where to put your source. It
+    also provides additional files and scripts, especially useful when using Salesforce Extensions for VS Code. For
+    example:
+
+    - .gitignore: Use Git for version control.
+    - .prettierrc and .prettierignore: Use Prettier to format your Aura components.
+    - .vscode/extensions.json: When launched, Visual Studio Code, prompts you to install the recommended extensions for
+    your project.
+    - .vscode/launch.json: Configures Replay Debugger.
+    - .vscode/settings.json: Additional configuration settings.
+
+    The analytics template provides similar files and the force-app/main/default/waveTemplates directory.
+
+  -x, --manifest  Generate a manifest (package.xml) for change-set based development.
+
+    Generates a default manifest (package.xml) for fetching Apex, Visualforce, Lightning components, and static
+    resources.
+
+  --api-version=<value>  Will set this version as sourceApiVersion in the sfdx-project.json file
+
+    Override the api version used for api requests made by this command
+```
+
+_See code: [src/commands/project/generate.ts](https://github.com/salesforcecli/plugin-templates/blob/main/src/commands/project/generate.ts)_
+
+## `sf static-resource generate`
+
+Generate a static resource.
+
+```
+USAGE
+  $ sf static-resource generate -n <value> [--json] [--type <value>] [-d <value>] [--api-version <value>]
+
+FLAGS
+  -d, --output-dir=<value>   [default: .] Directory for saving the created files.
+  -n, --name=<value>         (required) Name of the generated static resource.
+      --api-version=<value>  Override the api version used for api requests made by this command
+      --type=<value>         [default: application/zip] Content type (mime type) of the generated static resource.
+
+GLOBAL FLAGS
+  --json  Format output as json.
 
 DESCRIPTION
-  If not supplied, the apiversion, template, and outputdir use default values.
-  The outputdir can be an absolute path or relative to the current working directory.
-  Name and label are required.
+  Generate a static resource.
+
+  Generates the metadata resource file in the specified directory or the current working directory. Static resource
+  files must be contained in a parent directory called "staticresources" in your package directory. Either run this
+  command from an existing directory of this name, or use the --output-dir flag to create one or point to an existing
+  one.
+
+ALIASES
+  $ sf force staticresource create
 
 EXAMPLES
-  $ sfdx force:visualforce:component:create -n mycomponent -l mylabel
-  $ sfdx force:visualforce:component:create -n mycomponent -l mylabel -d components
+  Generate the metadata file for a static resource called MyResource in the current directory:
+
+    $ sf static-resource generate --name MyResource
+
+  Similar to previous example, but specifies a MIME type of application/json:
+
+    $ sf static-resource generate --name MyResource --type application/json
+
+  Generate the resource file in the "force-app/main/default/staticresources" directory:
+
+    $ sf static-resource generate --name MyResource --output-dir force-app/main/default/staticresources
+
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory for saving the created files.
+
+    The location can be an absolute path or relative to the current working directory. The default is the current
+    directory.
+
+  -n, --name=<value>  Name of the generated static resource.
+
+    This name can contain only underscores and alphanumeric characters, and must be unique in your org. It must begin
+    with a letter, not include spaces, not end with an underscore, and not contain two consecutive underscores.
+
+  --type=<value>  Content type (mime type) of the generated static resource.
+
+    Must be a valid MIME type such as application/json, application/javascript, application/zip, text/plain, text/css,
+    etc.
 ```
 
-_See code: [src/commands/force/visualforce/component/create.ts](https://github.com/salesforcecli/plugin-templates/blob/master/src/commands/force/visualforce/component/create.ts)_
+_See code: [src/commands/static-resource/generate.ts](https://github.com/salesforcecli/plugin-templates/blob/main/src/commands/static-resource/generate.ts)_
 
-#### `sfdx force:visualforce:page:create`
+## `sf visualforce generate component`
 
-create a Visualforce page
+Generate a Visualforce Component.
 
 ```
 USAGE
-  $ sfdx force:visualforce:page:create -n <string> -l <string> [-d <string>] [-t <string>] [--apiversion <string>]
-  [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
+  $ sf visualforce generate component -n <value> -l <value> [--json] [-t DefaultVFComponent] [-d <value>] [--api-version
+  <value>]
 
-OPTIONS
-  -d, --outputdir=outputdir                                                         folder for saving the created files
+FLAGS
+  -d, --output-dir=<value>   [default: .] Directory for saving the created files.
+  -l, --label=<value>        (required) Visualforce Component label.
+  -n, --name=<value>         (required) Name of the generated Visualforce Component.
+  -t, --template=<option>    [default: DefaultVFComponent] Template to use for file creation.
+                             <options: DefaultVFComponent>
+      --api-version=<value>  Override the api version used for api requests made by this command
 
-  -l, --label=label                                                                 (required) Visualforce page label
+GLOBAL FLAGS
+  --json  Format output as json.
 
-  -n, --pagename=pagename                                                           (required) name of the generated
-                                                                                    Visualforce page
+DESCRIPTION
+  Generate a Visualforce Component.
+
+  The command generates the .Component file and associated metadata file in the specified directory or the current
+  working directory by default.
+
+ALIASES
+  $ sf force visualforce component create
+
+EXAMPLES
+  Generate the metadata files for a Visualforce component in the current directory:
 
-  -t, --template=DefaultVFPage                                                      [default: DefaultVFPage] template to
-                                                                                    use for file creation
+    $ sf visualforce generate component --name mycomponent --label mylabel
 
-  --apiversion=apiversion                                                           override the api version used for
-                                                                                    api requests made by this command
+  Similar to previous example, but generate the files in the directory "force-app/main/default/components":
 
-  --json                                                                            format output as json
+    $ sf visualforce generate component --name mycomponent --label mylabel --output-dir components
 
-  --loglevel=(trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL)  [default: warn] logging level for
-                                                                                    this command invocation
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory for saving the created files.
+
+    The location can be an absolute path or relative to the current working directory. The default is the current
+    directory.
+
+  -n, --name=<value>  Name of the generated Visualforce Component.
+
+    The name can be up to 40 characters and must start with a letter.
+
+  -t, --template=DefaultVFComponent  Template to use for file creation.
+
+    Supplied parameter values or default values are filled into a copy of the template.
+```
+
+_See code: [src/commands/visualforce/generate/component.ts](https://github.com/salesforcecli/plugin-templates/blob/main/src/commands/visualforce/generate/component.ts)_
+
+## `sf visualforce generate page`
+
+Generate a Visualforce Page.
+
+```
+USAGE
+  $ sf visualforce generate page -n <value> -l <value> [--json] [-d <value>] [--api-version <value>]
+
+FLAGS
+  -d, --output-dir=<value>   [default: .] Directory for saving the created files.
+  -l, --label=<value>        (required) Visualforce Page label.
+  -n, --name=<value>         (required) Name of the generated Visualforce Page.
+      --api-version=<value>  Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --json  Format output as json.
 
 DESCRIPTION
-  If not supplied, the apiversion, template, and outputdir use default values.
-  If not supplied, the apiversion, template, and outputdir use default values.
-  Name and label are required.
+  Generate a Visualforce Page.
+
+  The command generates the .Page file and associated metadata file in the specified directory or the current working
+  directory by default.
+
+ALIASES
+  $ sf force visualforce page create
 
 EXAMPLES
-  $ sfdx force:visualforce:page:create -n mypage -l mylabel
-  $ sfdx force:visualforce:page:create -n mypage -l mylabel -d pages
+  Generate the metadata files for a Visualforce page in the current directory:
+
+    $ sf visualforce generate page --name mypage --label mylabel
+
+  Similar to previous example, but generate the files in the directory "force-app/main/default/pages":
+
+    $ sf visualforce generate page --name mypage --label mylabel --output-dir pages
+
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory for saving the created files.
+
+    The location can be an absolute path or relative to the current working directory. The default is the current
+    directory.
+
+  -n, --name=<value>  Name of the generated Visualforce Page.
+
+    The name can be up to 40 characters and must start with a letter.
 ```
 
-_See code: [src/commands/force/visualforce/page/create.ts](https://github.com/salesforcecli/plugin-templates/blob/master/src/commands/force/visualforce/page/create.ts)_
+_See code: [src/commands/visualforce/generate/page.ts](https://github.com/salesforcecli/plugin-templates/blob/main/src/commands/visualforce/generate/page.ts)_
+
+<!-- commandsstop -->