templui
templUI component library for Go templ apps. templUI is vanilla JavaScript only — zero JS frameworks (per templui.io). Covers Script() setup, Go variable interpolation into inline JavaScript, HTML-to-templ conversion, HTMX integration, and optional Alpine.js as a separate app-level state layer. Use when user pastes templ code, builds UI in a templ project, asks 'how do I add an icon/button/dialog/dropdown' in templ, or interpolates Go state into client-side scripts.
What this skill does
# templUI Best Practices
Apply templUI patterns when building Go/Templ web applications.
## CRITICAL: templUI Uses Vanilla JavaScript (Zero JS Frameworks)
Per [templui.io](https://templui.io/): "Zero JS frameworks — Just vanilla. Just fast." templUI components use **vanilla JavaScript via Script() templates** for all interactivity (popovers, dropdowns, dialogs, tabs, etc.). They do NOT depend on Alpine.js, React, Vue, or any other framework.
**Earlier versions of templUI integrated with Alpine.js. That dependency has been removed.** If you find documentation or code referencing `x-data`/`x-show`/`x-if` directives inside templUI components, it's stale.
## The Frontend Stack
| Tool | Purpose | Use For |
|------|---------|---------|
| **templUI** | Pre-built UI components (vanilla JS) | Dropdowns, dialogs, tabs, sidebars, popovers, accordions |
| **HTMX** | Server-driven interactions | AJAX, form submissions, partial page updates, live search |
| **Alpine.js** *(optional)* | Lightweight client-side state | Toggles, animations, client-side filtering, transitions — used **alongside** templUI, not as an integration. Skip if you don't need a reactive state layer beyond what HTMX + Script() provide. |
| **Floating UI** | Positioning primitive (used internally by templUI) | Tooltips, popovers, dropdowns — usually transparent to users |
---
## Reference Files
Read the relevant file for detailed patterns, code examples, and troubleshooting:
### `htmx-alpine-integration.md` — HTMX + Alpine.js (optional, separate from templUI)
For apps that choose to add Alpine.js as a client-side state layer **alongside** templUI. Read only when Alpine is actually in use. Covers: when to use HTMX vs Alpine vs combined, Alpine-Morph extension for state preservation across swaps, `htmx.process()` for Alpine conditionals, triggering HTMX from Alpine. **Skip if your app uses templUI + HTMX + Script() without Alpine** — that's templUI's recommended setup.
### `templ-interpolation.md` — CRITICAL: Templ Interpolation in JavaScript
Go expressions `{ value }` do NOT interpolate inside `<script>` tags. Five patterns to solve this:
1. **Data attributes** (recommended) — `data-*` attrs + `this.dataset`
2. **templ.JSFuncCall** — auto JSON-encodes, prevents XSS
3. **Double braces** — `{{ value }}` inside `<script>` tags
4. **templ.JSONString** — complex structs/maps via attributes or `templ.JSONScript`
5. **templ.OnceHandle** — ensures scripts render once in loops
Includes when-to-use table and common mistakes.
### `templui-cli.md` — templUI CLI Tool
Install, init, add components, force-update, list available. **Always use CLI to add/update components** — manual copies miss Script() templates.
### `script-templates.md` — Script() Templates (REQUIRED)
Components with JavaScript need Script() calls in base layout `<head>`. Lists all Script() imports (popover, dropdown, dialog, accordion, tabs, carousel, toast, clipboard), component dependency table, and troubleshooting for non-working components.
### `conversion-and-audit.md` — Converting Sites & Auditing
Converting HTML/React/Vue to Go/Templ: process, syntax mapping, package structure. Templ syntax quick reference (props, conditionals, loops, composition). Audit checklist for Script() calls, CLI installation, consistency, dark mode, responsive. Import patterns and troubleshooting guide. Resource links for templUI, HTMX+Alpine, and templ docs.
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".