Conciseness

Every line is a Vizro-specific gotcha, pattern, or import — no explanations of concepts Claude already knows, no padding. The body assumes competence and each token carries Vizro-irreversible information, matching the lean-and-efficient anchor.

Actionability

Concrete directives ("use `data_frame` directly; never re-lookup via `data_manager[data_frame]`") and accurate YAML/Python snippets cover the common component types, but the Quick Patterns are fragments without a complete end-to-end config (no page/dashboard wrapper), so they are not fully copy-paste runnable. Fits mostly-executable-with-minor-gaps rather than the fully-executable anchor.

Workflow Clarity

Clear organization (mistakes → patterns → imports → deep-dive lookup table) gives an unambiguous usage flow, and the Deep Dive table maps needs to specific reference sections. No explicit sequence or verification checkpoint for assembling/validating a config exists, keeping it below the explicit-validation anchor; no destructive or batch operations trigger the cap.

Progressive Disclosure

The body is a genuine overview with details split into a single one-level-deep reference (references/yaml-reference.md, verified to exist with all mapped section headers), clearly signaled twice and navigable via a need-to-search-string table. Matches the clear-overview, well-signaled one-level-deep anchor.

Specificity

The description enumerates multiple concrete capabilities — "component syntax, data_manager registration, custom function wiring, filter/parameter setup, or AG Grid tables" — covering the full Vizro YAML surface, matching the comprehensive-coverage anchor rather than the minor-gaps anchor below it.

Completeness

Both halves are explicit: the "what" ("writing or debugging Vizro YAML dashboard configurations" with enumerated sub-capabilities) and a concrete "when" ("Activate when the user is building a Vizro app, encountering YAML or runtime errors, or asking about Vizro component patterns"). Matches the both-what-and-when-with-concrete-triggers anchor; the level below requires a weaker or less specific 'when'.

Trigger Term Quality

Good natural-term coverage ("building a Vizro app", "encountering YAML or runtime errors", "dashboard", "AG Grid", "component patterns") but a few natural variations are missing (e.g., ".yaml" file extension, "chart", "KPI"). Fits the good-coverage-with-a-few-missing anchor, not the comprehensive synonym/extension coverage of 5.

Distinctiveness Conflict Risk

A clear niche (Vizro-specific YAML configuration) with distinct triggers; unlikely to fire for unrelated dashboard or YAML-generic skills, matching the minimal-conflict-risk anchor.