HTMX development guidelines for building dynamic web applications with minimal JavaScript using HTML attributes.
Install
npx skills add https://github.com/mindrally/skills --skill htmxSKILL.md
HTMX Development
You are an expert in HTMX for building dynamic web applications with minimal JavaScript.
Core Principles
- Write concise, clear, and technical responses with precise HTMX examples
- Leverage HTMX's interactivity capabilities without heavy JavaScript dependencies
- Prioritize maintainability and readable code structure
- Return only necessary HTML snippets from the server
HTMX Usage Guidelines
Request Attributes
hx-get- Make GET request to URLhx-post- Make POST request to URLhx-put- Make PUT request to URLhx-patch- Make PATCH request to URLhx-delete- Make DELETE request to URL
DOM Manipulation
hx-target- Specify where response content gets injectedhx-swap- Customize DOM insertion method (innerHTML, outerHTML, beforeend, etc.)hx-trigger- Customize event handling and control request timinghx-select- Select specific content from response
URL Management
hx-push-url- Update browser URL without full page refreshhx-replace-url- Replace current URL in history
Best Practices
Request Handling
<!-- Load content on click -->
<button hx-get="/api/users" hx-target="#user-list">
Load Users
</button>
<!-- Submit form via AJAX -->
<form hx-post="/api/submit" hx-target="#result" hx-swap="innerHTML">
<input name="email" type="email">
<button type="submit">Submit</button>
</form>
Error Handling
- Implement server-side validation before processing requests
- Return appropriate HTTP status codes (4xx for client errors, 5xx for server errors)
- Provide user-friendly error messages
- Use
hx-swapfor customizing error feedback presentation
User Confirmation
<button hx-delete="/api/item/1"
hx-confirm="Are you sure you want to delete this?">
Delete
</button>
Performance Optimization
- Minimize server response sizes by sending only essential HTML
- Implement server-side caching for frequently requested endpoints
- Precompile reusable component fragments
- Use
hx-boostfor progressive enhancement of links
Integration Patterns
With CSS Frameworks
- Combine HTMX with Bootstrap or Tailwind without script conflicts
- Use loading indicators for better UX
- Handle transitions smoothly
Template Organization
- Organize templates as efficient, reusable HTMX fragments
- Maintain clear separation of concerns
- Use partial templates for common components
Key Conventions
- Maintain consistent naming for HTMX attributes
- Ensure fast and intuitive interactions
- Structure templates with clear separation of concerns
- Favor declarative attributes over JavaScript event handlers
Related skills
vercel-react-best-practicesvercel-labs751KReact and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.vercel-composition-patternsvercel-labs361KReact composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.vercel-react-view-transitionsvercel-labs135KGuide for implementing smooth, native-feeling animations using React's View Transition API (`<ViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components, animate list reorder, implement directional (forward/back) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions viewpick-ui-libraryemilkowalski124KPick the right library for a given frontend task from a curated, opinionated list — numbers, OTP inputs, charts, command menus, virtualization, drag and drop, toasts, state, styling, and more. Only runs when explicitly invoked; it does not trigger on its own.