Conciseness

Quotes: "If a file is imported by module.ts directly (even transitively), it ends up in module.js" and the symlink workaround ("ln -s plugin/yarn.lock yarn.lock") — dense, non-obvious, Grafana-specific guidance with no tutorial padding about React.lazy or webpack basics. Minor over-length comes from ~65 lines of inline CI workflow YAML ("# .github/workflows/bundle-size.yml") that is tangential to the core splitting skill — efficient overall with trimmable sections, matching the 4 anchor rather than the 5 anchor's 'every token earns its place'.

Actionability

Quotes: complete module.tsx example ("const LazyApp = lazy(async () => { await initFaro(); return import('./features/app/App').then(m => ({ default: m.App })); })"), executable bash ("jq -r '"\(.id) — \(.type)"' src/plugin.json"), and copy-paste webpackChunkName snippets. The code covers the common cases (named vs default exports, barrels, singletons) and is directly executable — matches the 5 anchor.

Workflow Clarity

Quotes: "Measure the current PRODUCTION bundle size BEFORE making any changes" (baseline checkpoint in Step 2), Step 7's target table ("module.js size < 200 KB | Total JS chunk count 15–25"), and Step 8's manual verification checklist ("Navigate to every route — each triggers a new chunk download", "Check Console for errors"). Steps 1–8 are clearly sequenced with explicit validation and recovery paths (Step 6 over-splitting remediation, troubleshooting reference) — matches the 5 anchor's explicit validation steps and feedback loops.

Progressive Disclosure

Quotes: "see [references/datasource-plugins.md](references/datasource-plugins.md)" and "see [references/troubleshooting.md](references/troubleshooting.md)" — both files exist in the bundle, are one level deep, and are signalled at the point of need; the datasource reference correctly parks a sub-case out of the main flow. Slightly below the 5 anchor because the body still inlines large self-contained content (two full CI workflow YAML blocks) that fits the bundle's reference pattern, leaving the overview role less clean than 'appropriately split'.

Specificity

Quotes: "Optimise Grafana app plugin bundle size using React.lazy, Suspense, and webpack code splitting" plus enumerated actions ("reduce plugin bundle size, optimise module.js, add code splitting, ... lazy load plugin pages"). Several concrete actions with named tools, but they are all facets of one optimisation technique — not the comprehensive multi-action coverage of the 5 anchor (no measuring, CI, or datasource-plugin coverage). Clearly above the 3 anchor's '1-2 concrete actions'.

Completeness

Explicitly answers both: what ("Optimise Grafana app plugin bundle size using React.lazy, Suspense, and webpack code splitting") and when ("Use when the user asks to... Triggers on phrases like..."), with concrete trigger phrases — a direct match to the 5 anchor exemplar. Neither the what nor the when is vague, so 4 ('when could be more explicit') does not fit.

Trigger Term Quality

Quotes: "optimise plugin bundle size", "module.js is too large", "plugin is slow to load", "code split the plugin", "reduce initial JS payload", "help me with Suspense in my plugin" — comprehensive natural phrasings including file names and synonyms users would actually say. Matches the 5 anchor's 'natural terms including synonyms and file extensions' better than the 4 anchor's 'a few natural terms missing'.

Distinctiveness Conflict Risk

Quotes: "Grafana app plugin", "module.js", "Grafana app plugin" trigger scoping — a clear niche (Grafana app-plugin bundle optimisation) with distinct triggers. Only marginal overlap with generic web-performance skills; matches the 5 anchor's 'clear niche with distinct triggers; minimal conflict risk'.