Scaffolds Dart or Flutter projects from Very Good CLI templates (flutter_app, dart_package, flutter_package, flutter_plugin, dart_cli, flame_game, docs_site).
How this skill is triggered — by the user, by Claude, or both
Slash command
/vgv-ai-flutter-plugin:create-project [template] [project-name]When to use
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".
[template] [project-name]haikuThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Scaffold a new Dart or Flutter project using Very Good CLI templates.
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.
directory: '<path-to-created-project>' to packages_get so it runs against the new project, not the workspace rootdart_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_appdirectory: '<path-to-created-project>' to packages_get so it targets the new project| 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 |
npx claudepluginhub verygoodopensource/very-good-claude-code-marketplace --plugin vgv-ai-flutter-pluginScaffolds boilerplate for APIs (FastAPI, Express), web apps (Next.js, Nuxt, SvelteKit), CLI tools, libraries, monorepos with best-practice stacks and directory structures.
Routes project creation requests to the appropriate companion plugin's create skill. Scans recommendation files, matches user requests to plugins, and handles installation if needed.
Guides Flutter development for cross-platform iOS, Android, Web apps. Covers non-interactive CLI, project setup, state management, widgets, GoRouter navigation, platform channels, testing, CI/CD.