docs: add create command in current directory (#1549)

* docs: add create command in current directory

* chore: double check existing docs

* chore: apply changes from code review

* chore: review docs

Author: marcossevilla

site/docs/commands/create.md

@@ -0,0 +1,83 @@
+---
+sidebar_position: 0
+---
+
+# Create 🚀
+
+Create a new Very Good project from a template with `very_good create`. Each
+template type has a corresponding subcommand.
+
+## Usage
+
+```sh
+Creates a new Very Good project in the specified directory.
+
+Usage: very_good create <subcommand> <project-name> [arguments]
+-h, --help    Print this usage information.
+
+Available subcommands:
+  app_ui_package    Generate a Very Good App UI package.
+  dart_cli          Generate a Very Good Dart CLI application.
+  dart_package      Generate a Very Good Dart package.
+  docs_site         Generate a Very Good documentation site.
+  flame_game        Generate a Very Good Flame game.
+  flutter_app       Generate a Very Good Flutter application.
+  flutter_package   Generate a Very Good Flutter package.
+  flutter_plugin    Generate a Very Good Flutter plugin.
+
+Run "very_good help" to see global options.
+```
+
+:::tip
+Use `-o` or `--output-directory` to specify a custom output directory for the
+generated project.
+:::
+
+## Creating in the current directory
+
+Instead of specifying a project name, you can pass `.` to create the project
+in your current directory. Very Good CLI derives the project name from your
+current directory's basename. This works with every template subcommand.
+
+For example, if your working directory is `/home/user/my_flutter_app`, the
+following command creates a Flutter app named `my_flutter_app` in place:
+
+```sh
+# Create a Flutter app named after the current directory
+very_good create flutter_app .
+```
+
+You can combine `.` with any other supported flags for that template:
+
+```sh
+# Create a Flutter app with a custom org name
+very_good create flutter_app . --org "com.company"
+
+# Create a Flutter app with a description
+very_good create flutter_app . --desc "My production Flutter app"
+
+# Create a publishable Dart package
+very_good create dart_package . --desc "My Dart package" --publishable
+
+# Create a Flutter plugin that supports specific platforms
+very_good create flutter_plugin . --desc "My plugin" --platforms android,ios,web
+```
+
+:::note
+You cannot combine `.` with `--output-directory`. Very Good CLI will exit with
+an error if you specify both.
+:::
+
+## Available templates
+
+Each subcommand maps to a specific project template. For detailed usage options
+and examples, see the individual template pages:
+
+- [Flutter Starter App](../templates/core.md) — `flutter_app`
+- [Dart CLI](../templates/dart_cli.md) — `dart_cli`
+- [Dart Package](../templates/dart_pkg.md) — `dart_package`
+- [Flutter Package](../templates/flutter_pkg.md) — `flutter_package`
+- [Flutter Federated Plugin](../templates/federated_plugin.md) — `flutter_plugin`
+- [Flame Game](../templates/flame_game.md) — `flame_game`
+- [App UI Package](../templates/app_ui_package.md) — `app_ui_package`
+- [Docs Site](../templates/docs_site.md) — `docs_site`

site/docs/commands/mcp.md

@@ -134,6 +134,8 @@ The MCP server exposes the following tools to AI assistants:
 
 Create new Dart or Flutter projects from any of the available [templates](/docs/category/templates).
 
+See the [create command](./create.md) for more details.
+
 ### `test`
 
 Run tests with optional coverage and optimization. Supports both `dart test` and `flutter test` via a `dart` parameter.

site/docs/commands/test.md

@@ -25,6 +25,8 @@ very_good test [arguments]
     --exclude-coverage                One or more space-separated globs which will be used to exclude files that match from the coverage (e.g. '**/*.g.dart **/*.freezed.dart').
 -x, --exclude-tags                    Run only tests that do not have the specified tags.
     --min-coverage                    Whether to enforce a minimum coverage percentage.
+    --show-uncovered                  Whether to show uncovered lines when coverage is below 100%.
+                                      Implicitly enables coverage collection when used alone.
     --test-randomize-ordering-seed    The seed to randomize the execution order of test cases within test files.
     --update-goldens                  Whether "matchesGoldenFile()" calls within your test methods should update the golden files.
     --force-ansi                      Whether to force ansi output. If not specified, it will maintain the default behavior based on stdout and stderr.
@@ -38,6 +40,10 @@ very_good test [arguments]
     --collect-coverage-from=<imports|all>
                                       Whether to collect coverage from imported files only or all files.
                                       (defaults to "imports")
+    --report-on=<lib/>                Optional file paths to report coverage information to.
+                                      This should be paths relative to the current working directory.
+                                      Can be passed multiple times.
+    --run-skipped                     Run skipped tests instead of skipping them.
     --flavor                          Build a custom app flavor as defined by platform-specific build setup. Supports the use of product flavors in Android Gradle scripts, and the use of custom Xcode schemes.
     --fail-fast                       Stop running tests after the first failure.
 

site/docs/overview.md

@@ -66,7 +66,10 @@ Run "very_good help" to see global options.
 ```
 
 :::tip
-You can use `.` as the project name to create the project in the current directory. The project will be named with the name of the current directory.
+Pass `.` as the project name to create the project in the current directory.
+Very Good CLI derives the project name from the current directory's basename.
+
+See the [create command docs](./commands/create.md) for more details.
 :::
 
 ### `very_good mcp`

site/docs/templates/federated_plugin.md

@@ -15,6 +15,9 @@ Use `-o` or `--output-directory` to specify a custom output directory for the ge
 ```sh
 # Create a new Flutter plugin named my_flutter_plugin (all platforms enabled)
 very_good create flutter_plugin my_flutter_plugin --desc "My new Flutter plugin"
+
+# Create a new Flutter plugin named my_flutter_plugin with a custom org
+very_good create flutter_plugin my_flutter_plugin --desc "My new Flutter plugin" --org "com.custom.org"
 ```
 
 ## Providing supported platforms

site/docs/templates/flame_game.md

@@ -42,6 +42,9 @@ Use `-o` or `--output-directory` to specify a custom output directory for the ge
 # Create a new Flame game named my_game
 very_good create flame_game my_game --desc "My new Flame game"
 
+# Create a new Flame game named my_game with a custom org
+very_good create flame_game my_game --desc "My new Flame game" --org "com.custom.org"
+
 # Create a new Flame game named with the name of the current directory
 very_good create flame_game . --desc "My new Flame game"