doc-tester

You can validate Hex1b documentation by executing automated tests that compare embedded code samples against a locally built package, surfacing discrepancies in tutorials, guides, and API references. The skill relies on a local dotnet pack build workflow to enforce accuracy.

Yes, Playwright is used to drive page verification for Hex1b documentation, while TerminalMcp-based tests handle TUI scenarios. This combination validates widgets, theming, and layout examples to ensure documentation accurately reflects the actual library behavior.

Documentation drift detection audits Hex1b tutorials, guides, and API references by building the library locally and running automated tests against code examples. It produces concise discrepancy reports highlighting gaps, misrepresentations, or missing demos for doc-writers.

Yes, dotnet is a required dependency because the validation workflow relies on a local dotnet pack build to produce the Hex1b package. Code examples from the documentation are then tested against this locally built package to ensure reproducibility and accuracy.

You audit Hex1b widget and theming docs by running automated tests that validate code examples against the live library behavior using Playwright and TerminalMcp. The process targets specific scenarios like widgets, theming, and layouts to surface any discrepancies.