avalonia-docs

Reviews and lints Avalonia documentation pages against house style rules, content boundaries, anti-marketing standards, accessibility, and SEO. Use when reviewing, editing, or writing documentation to ensure consistency with established patterns. Checks structure, voice, terminology, formatting, linking, tone, Diataxis compliance, image accessibility, meta descriptions, and jargon simplification.

Scans the /docs directory for opportunities to cross-link with API reference documentation in /api, and vice versa. Creates bi-directional links between human-written docs and generated API pages. Invoke with /api-link-builder [optional-path-or-topic].

Analyzes GitHub discussion links to identify documentation gaps. Fetches the discussion, reviews questions and answers, searches existing docs for coverage, and recommends next steps (create new content, adjust existing content, or no action needed). Invoke with /discussion-gap-finder <github-discussion-url>.

Style Docusaurus sites to match Avalonia Customer Portal theme using TailwindCSS, CSS variables, and component swizzling. Use when user requests Docusaurus styling, theming, visual customization, or component modifications. Ensures unified brand experience across documentation and portal.

You are an expert in Docusaurus theming and the Infima CSS framework. The user has a React application built with Tailwind CSS and wants to replicate that look in a Docusaurus site.