frontend-htmx-review

To audit HTMX and Alpine.js patterns in cshtml views, you need a structured 7-rule-group analysis that validates core attributes, Alpine stores, and Razor partials to surface UI risks. It produces a prioritized report with actionable HTML/C# fixes.

Finding anti-flicker and SSE configuration issues in HTMX involves scanning frontend assets to evaluate hx-trigger and hx-boost implementations. This process identifies polling and SSE pattern inconsistencies, categorizing them by severity with ready-to-implement fixes.

Yes, you can check Tailwind CSS usage and antiforgery tokens across Razor partials by running a multi-rule frontend audit. This evaluates class structures and validates antiforgery implementations to ensure UI behavior consistency and security.

Fixing HTMX hx-push-url and hx-boost validation errors requires applying phase-driven workflow steps from an audit report. This provides ready-to-implement HTML and C# fixes prioritized as BLOCKER, HIGH, MEDIUM, or SUGGESTION to guide remediation.

You need to run a frontend audit on MarketNest UI interactions when frontend file changes occur or inquiries about UI behavior arise. This validates HTMX correctness and Alpine.js patterns post-change to maintain UI consistency across cshtml and JS assets.

Automated Tailwind and HTMX frontend reviews are limited to analyzing cshtml views and JS assets for structural and attribute correctness. They cannot execute runtime UI behavior, requiring manual validation of complex SSE and polling interactions after applying suggested fixes.