flutter-stack-menulisted

# flutter-stack-menu Return the templates the `flutter` plugin offers on vwf's `project` axis, per the stack-adapter contract. **Return the payload and nothing else** — no prose, no recommendation, no comparison. Choosing is the user's job and presenting the choice is vwf's. > **`invocation` must stay `both`.** A `user` skill is removed from the model's > context entirely and cannot be invoked programmatically — vwf does not get an > error, it gets an empty menu. ## How to answer 1. List `${CLAUDE_PLUGIN_ROOT}/stacks/project/*.md` — **flat**, with no role directory, since format 22. Each file is one template: its **slug** is the filename without `.md`, its **platforms** are that file's `platforms:` frontmatter key (a **list** — one template may serve several, and this plugin's does), and its `name` comes from the same frontmatter. Read no further into the file than the frontmatter and its opening paragraph — the body is `flutter-stack-template`'s to read, on demand. 2. Return the payload below, filled from that listing. ```yaml plugin: flutter templates: - slug: <filename without .md> axis: project platforms: <the file's own platforms: list> name: <display name> summary: <one line — why you would pick it> ``` ## Rules - **This list is exhaustive.** A composition not listed is one this plugin does not offer. There is no `custom` fallback — vwf retired it in `config_format` 14 and halts instead, naming the two ways forward (install