feat: add create-project skill (#40)

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: ryzizub

.claude-plugin/plugin.json

@@ -18,6 +18,7 @@
     "bloc",
     "bloc-test",
     "code-quality",
+    "create-project",
     "dart",
     "deep-linking",
     "flutter",

CLAUDE.md

@@ -18,6 +18,7 @@ hooks/
     analyze.sh         # Runs dart analyze on modified .dart files
     format.sh          # Runs dart format on modified .dart files
 skills/
+  create-project/SKILL.md
   accessibility/SKILL.md
   accessibility/reference.md
   bloc/SKILL.md

README.md

@@ -45,6 +45,7 @@ You should see `very-good-ai-flutter-plugin` in the output.
 
 | Skill | Description |
 | ----- | ----------- |
+| [**Create Project**](skills/create-project/SKILL.md) | Scaffold new Dart/Flutter projects from Very Good CLI templates — `flutter_app`, `dart_package`, `flutter_plugin`, `dart_cli`, `flame_game`, and more |
 | [**Accessibility**](skills/accessibility/SKILL.md) | WCAG 2.1 AA compliance — semantics, screen reader support, touch targets, focus management, color contrast, text scaling, and motion sensitivity |
 | [**Testing**](skills/testing/SKILL.md) | Unit, widget, and golden testing — `mocktail` mocking, `pumpApp` helpers, test structure & naming, coverage patterns, and `dart_test.yaml` configuration |
 | [**Navigation**](skills/navigation/SKILL.md) | GoRouter routing — `@TypedGoRoute` type-safe routes, deep linking, redirects, shell routes, and widget testing with `MockGoRouter` |
@@ -82,6 +83,7 @@ For example:
 You can also invoke skills directly as slash commands:
 
 ```bash
+/vgv-create-project
 /vgv-accessibility
 /vgv-bloc
 /vgv-internationalization

skills/create-project/SKILL.md

@@ -0,0 +1,99 @@
+---
+name: vgv-create-project
+description: Scaffold a new Dart or Flutter project from a Very Good CLI template. Use when user says "create a new project", "start a new flutter app", "scaffold a package", "initialize a dart cli", "new flame game", or "generate a plugin". Supports flutter_app, dart_package, flutter_package, flutter_plugin, dart_cli, flame_game, and docs_site templates.
+allowed-tools: mcp__very-good-cli__create,mcp__very-good-cli__packages_get
+argument-hint: "[template] [project-name]"
+---
+
+# Create Project
+
+Scaffold a new Dart or Flutter project using Very Good CLI templates.
+
+---
+
+## Core Standards
+
+- **Use the Very Good CLI MCP server** to scaffold projects and install dependencies
+- **Infer the template from context** — determine the right template based on what the user wants to build, not by asking them to pick a subcommand name
+- **Use `AskUserQuestion` only for information you cannot infer** — project name and organization are the most common missing pieces
+- **Install dependencies after creation**
+
+---
+
+## Workflow
+
+### Step 1: Understand What the User Wants to Build
+
+Infer the subcommand from the user's description — the available subcommands and their descriptions are defined by the Very Good CLI MCP server. Do NOT ask users to pick a subcommand name — figure it out from context.
+
+If the intent is ambiguous, use `AskUserQuestion` to clarify with a high-level question about what they're building — not which subcommand they want.
+
+### Step 2: Gather Missing Parameters
+
+Use `AskUserQuestion` to collect only what you cannot infer. Batch questions into a single call when possible. Do NOT ask for optional parameters (description, output directory, application ID, etc.) unless the user brings them up.
+
+### Step 3: Create and Set Up
+
+1. Create the project using the Very Good CLI MCP server
+2. Install dependencies using the Very Good CLI MCP server
+
+---
+
+## Key Domain Knowledge
+
+- Use `dart_package` (not `flutter_package`) for data layer and repository layer packages in the **layered-architecture** pattern — these must not depend on Flutter SDK
+- If a user provides a project name with dashes, convert to underscores — Dart package names only allow lowercase letters, numbers, and underscores
+- Templates that produce apps, plugins, or games require an organization name — do not skip this or it defaults to a placeholder value
+
+---
+
+## Examples
+
+### User says "Create a new Flutter app"
+
+1. Infer: `flutter_app`
+2. Ask for project name and organization
+3. Create and install dependencies
+
+### User says "I need a package for my weather API client, put it in packages/"
+
+1. Infer: "API client" → pure Dart → `dart_package`, name `weather_api_client`, output `packages/`
+2. Everything is clear — no questions needed
+3. Create and install dependencies
+
+### User says "I want to build something for iOS and Android with bluetooth"
+
+1. Ambiguous: app or plugin? Ask to clarify
+2. Gather remaining parameters based on answer
+3. Create and install dependencies
+
+### User says "Create a new package"
+
+1. Ambiguous: Flutter or pure Dart? Ask to clarify
+2. Ask for project name
+3. Create and install dependencies
+
+---
+
+## Troubleshooting
+
+### Invalid project name error
+
+- Names must be valid Dart package names: lowercase letters, numbers, underscores only
+- Dashes are not allowed — convert `my-app` to `my_app`
+
+### Dependencies fail to install after creation
+
+- Verify the Dart SDK is installed and on PATH
+- Try running from the project root directory
+
+---
+
+## Anti-Patterns
+
+| Anti-Pattern | Problem | Correct Approach |
+| --- | --- | --- |
+| Asking user to pick a template name | Users think in terms of what they're building, not CLI subcommands | Infer the template from context |
+| Over-asking for optional parameters | Slows down the workflow | Only ask for what you cannot infer |
+| Using `flutter_package` for a data layer | Adds unnecessary Flutter SDK dependency | Use `dart_package` for data and repository layer packages |
+| Skipping organization name for apps/plugins | Defaults to a placeholder value | Ask when the template requires it |