Scaffolds new Dart or Flutter projects using Very Good CLI templates including flutter_app, dart_package, flutter_package, flutter_plugin, dart_cli, flame_game, and docs_site. Installs dependencies.
npx claudepluginhub verygoodopensource/very_good_claude_code_marketplace --plugin vgv-ai-flutter-pluginThis skill is limited to using the following tools:
Scaffold a new Dart or Flutter project using Very Good CLI templates.
Creates new Flutter projects using flutter create CLI with platform selection (android,ios,web,desktop), pubspec.yaml configuration, dependencies, and initial structure. Use for project initialization and scaffolding.
Generates Flutter projects for Todo, Habit, Note, Expense, or Custom domains with Clean Architecture, Riverpod 3.0, Drift DB, Freezed entities, GoRouter, FPDart, and stack presets (Minimal/Essential/Full).
Scaffolds boilerplate for APIs (FastAPI, Express, Gin, Axum), web apps (Next.js, Nuxt, SvelteKit), CLI tools, libraries, and monorepos with best-practice stacks.
Share bugs, ideas, or general feedback.
Scaffold a new Dart or Flutter project using Very Good CLI templates.
AskUserQuestion only for information you cannot infer — project name and organization are the most common missing piecesInfer 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.
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.
dart_package (not flutter_package) for data layer and repository layer packages in the layered-architecture pattern — these must not depend on Flutter SDKflutter_appdart_package, name weather_api_client, output packages/my-app to my_app| 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 |