Content
47%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A brief, well-sectioned overview that stays token-efficient, but it reads as a menu of capabilities rather than an executable guide: the actual scaffold/build/publish commands are missing and no ordered workflow or verification step is given.
Suggestions
Replace the Capabilities list with a numbered setup workflow starting with the concrete scaffold command (e.g. `dotnet new avalonia.app -n MyAvaloniaApp` or the equivalent manual csproj), followed by theme/MVVM configuration steps.
Add a validation checkpoint (e.g. `dotnet build` then `dotnet run` to confirm the window renders) so failures are caught before further configuration.
Include the missing key files (App.axaml, Program.cs, a minimal ViewModel showing the Greeting/ClickCommand bindings referenced in MainWindow.axaml) or move publishing/hot-reload detail into a references file instead of only listing it as a capability.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly lean, but the opening sentence duplicates the frontmatter description nearly verbatim and the 8-bullet 'Capabilities' list ('Set up hot reload', 'Configure build for all platforms') restates the theme without teaching anything — it could be tightened or cut. | 3 / 5 |
Actionability | Concrete artifacts exist (input schema, project tree, a complete MainWindow.axaml), but the core task is unexecutable: no `dotnet new` command, no .csproj template, no package references, and no App.axaml/Program.cs content despite listing them in the structure. | 3 / 5 |
Workflow Clarity | For a multi-step setup task (create project, configure MVVM/theme, build, publish per platform) there is no sequenced procedure at all — just reference fragments — and no validation step such as `dotnet build`/`dotnet run` to confirm the setup works. | 2 / 5 |
Progressive Disclosure | The body is short with clearly labeled sections and no nested or buried references, but several advertised capabilities (hot reload, native menus, platform publishing) have no supporting detail here and no reference files exist to carry them — a minor organization gap. | 4 / 5 |
Total | 12 / 20 Passed |