templui

templUI & HTMX/Alpine Best Practices Apply templUI patterns and HTMX/Alpine.js best practices when building Go/Templ web applications.

| HTMX | Server-driven interactions | AJAX requests, form submissions, partial page updates, live search | | Alpine.js | Client-side state & reactivity | Toggles, animations, client-side filtering, transitions, local state | | templUI | Pre-built UI components | Dropdowns, dialogs, tabs, sidebars (uses vanilla JS via Script() templates) |

Note: templUI components use vanilla JavaScript (not Alpine.js) via Script() templates. This is fine - Alpine.js is still part of the stack for your custom client-side needs.

WHEN: User is building Go/Templ web apps, using templUI components, converting sites to Templ, asking about templ syntax, Script() templates, HTMX/Alpine integration, JavaScript in templ, or working with .templ files. Also trigger when user mentions "component library", "UI components", "buttons/cards/modals/tables" in a Go web project, "templ generate", Alpine.js with Go, or asks how to build interactive UIs in Go without React/Vue. Activate whenever .templ files are present in the project or templUI is in dependencies. WHEN NOT: Non-Go projects, pure JavaScript/TypeScript frontend frameworks Source: gopherguides/gopher-ai.