Agent skill

Htmx Developer

by FerroxLabs in FerroxLabs/wayland

HTMX development expertise covering hypermedia-driven application patterns, progressive enhancement, server-side rendering integration, HTMX attributes and extensions, partial page updates, form…

Apache-2.0Auto-check passedFrontend & Design

Install Htmx Developer

skills CLI
$ npx skills add FerroxLabs/wayland --skill htmx-developer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install FerroxLabs/wayland htmx-developer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/web-development/htmx-developer .claude/skills/htmx-developer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
htmx-developer
GitHub stars
608
Token cost
~4k tokens
SKILL.md length
813 words
Files
1
Skills in repo
1,194
Repo updated
First seen
Licence
Apache-2.0

At a glance

HTMX development expertise covering hypermedia-driven application patterns, progressive enhancement, server-side rendering integration, HTMX attributes and extensions, partial page updates, form…

  • Works in 6 steps: Keep HTML fragments small: Return only… → Use hx-select: Extract only what you… → Debounce inputs: Always use delay: on… → …
  • The user asks about htmx developer
  • SKILL.md covers When HTMX is the Right Choice, Core HTMX Patterns, Server-Side Integration and Common Application Patterns, plus 9 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Htmx Developer is an agent skill from FerroxLabs/wayland. HTMX development expertise covering hypermedia-driven application patterns, progressive enhancement, server-side rendering integration, HTMX attributes and extensions, partial page updates, form handling, real-time features, and migration from SPA frameworks. Use when the user asks about htmx developer, htmx developer best practices, or needs guidance on htmx developer implementation. Do NOT use when the user needs a different specialized skill or is asking about an unrelated technology domain.

Its SKILL.md is about 4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design, covering Backend development and Forms and validation. The repository describes itself as: Wayland - The AI Agent That Perceives. Reasons. Acts. Evolves. The licence is Apache-2.0.

When your agent uses it

  • The user asks about htmx developer
  • Htmx developer best practices
  • Needs guidance on htmx developer implementation
  • The user needs a different specialized skill

Example prompts

  • “/htmx-developer”

Requirements

  • Python 3

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Keep HTML fragments small: Return only the changed part of the page, not large sections.
  2. Use hx-select: Extract only what you need from a larger response.
  3. Debounce inputs: Always use delay: on keyup/input triggers.
  4. Use hx-indicator: Show loading states so users know something is happening.
  5. Preload on hover: Use the preload extension for navigation links.
  6. Out-of-band swaps: Update multiple page areas with one response using hx-swap-oob.

What it can do on your machine

Read from SKILL.md and the folder at commit 4c030c7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are html, python, go and markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Htmx Developer loads about 4k tokens when it runs. Until then it costs about 129 tokens; SKILL.md has 813 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~129
When it runs · the whole SKILL.md, loaded when a task matches
~4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from FerroxLabs/wayland at commit 4c030c7, republished under its Apache-2.0 licence (© FerroxLabs). 813 words, ~4,027 tokens.

Download SKILL.mdSave it as .claude/skills/htmx-developer/SKILL.md (or your agent's skills folder).
name
htmx-developer
description
HTMX development expertise covering hypermedia-driven application patterns, progressive enhancement, server-side rendering integration, HTMX attributes and extensions, partial page updates, form handling, real-time features, and migration from SPA frameworks. Use when the user asks about htmx developer, htmx developer best practices, or needs guidance on htmx developer implementation. Do NOT use when the user needs a different specialized skill or is asking about an unrelated technology domain.
license
Apache-2.0
metadata.author
foundry-skills
metadata.version
1.0.0
metadata.tags
web-development frontend javascript
metadata.category
web-development
metadata.subcategory
frontend-frameworks
metadata.disclaimer
none
metadata.difficulty
intermediate

HTMX Developer

You are an expert in building hypermedia-driven applications with HTMX. HTMX returns to the original architecture of the web -- the server sends HTML, not JSON -- but with modern UX expectations like partial page updates, inline editing, and real-time features. The result is dramatically simpler applications: no JavaScript framework, no build step, no client-side state management, and a fraction of the code.

When HTMX is the Right Choice

Decision Framework
HTMX is ideal when:
  ✓ Content-focused applications (dashboards, admin panels, CMS, e-commerce)
  ✓ CRUD-heavy workflows (forms, tables, lists)
  ✓ Server-rendered applications that need dynamic UX upgrades
  ✓ Small teams that want to move fast without frontend complexity
  ✓ Progressive enhancement matters (works without JS, better with JS)

HTMX is NOT ideal when:
  ✗ Rich client-side interactivity (drawing tools, spreadsheets, IDEs)
  ✗ Offline-first applications (HTMX requires server connectivity)
  ✗ Complex client-side state (drag-and-drop reordering, real-time collaboration)
  ✗ Native mobile apps (no HTML rendering)
HTMX vs SPA Frameworks
AspectHTMXReact/Vue/Svelte
Server sendsHTML fragmentsJSON data
RenderingServer-sideClient-side
State managementServer (session/DB)Client (Redux/Zustand)
JavaScript neededMinimal (HTMX + extensions)Significant (framework + deps)
Build stepNone requiredRequired (Webpack/Vite)
SEOBuilt-in (server-rendered)Requires SSR/SSG setup
Learning curveHTML attributesFramework + ecosystem
Bundle size~14KB (HTMX)50-200KB+ (framework + deps)
Offline supportLimitedGood (with service worker)
Rich interactivityGood for most appsExcellent

Core HTMX Patterns

Basic Attributes
html
<!-- GET request, replace inner content -->
<button hx-get="/api/users" hx-target="#user-list" hx-swap="innerHTML">
  Load Users
</button>
<div id="user-list"><!-- Users will appear here --></div>

<!-- POST request with form data -->
<form hx-post="/api/users" hx-target="#user-list" hx-swap="afterbegin">
  <input name="email" type="email" required>
  <button type="submit">Add User</button>
</form>

<!-- DELETE with confirmation -->
<button hx-delete="/api/users/123"
        hx-confirm="Are you sure?"
        hx-target="closest tr"
        hx-swap="outerHTML swap:500ms">
  Delete
</button>

<!-- PUT for inline editing -->
<div hx-get="/api/users/123/edit" hx-trigger="click" hx-swap="outerHTML">
  Click to edit: John Doe
</div>
Swap Strategies
StrategyBehaviorUse Case
innerHTMLReplace children of targetUpdate a list, refresh a section
outerHTMLReplace the entire targetReplace an element with an edited version
afterbeginPrepend inside targetAdd item to top of list
beforeendAppend inside targetAdd item to bottom of list
beforebeginInsert before targetAdd a row above
afterendInsert after targetAdd a row below
deleteDelete the targetRemove an element
noneDon't swap (still fires events)Trigger side effects only
Trigger Patterns
html
<!-- Standard triggers -->
<input hx-get="/search" hx-trigger="keyup changed delay:300ms" hx-target="#results">

<!-- Revealed trigger (lazy loading) -->
<div hx-get="/api/comments?page=2" hx-trigger="revealed" hx-swap="afterend">
  Loading more comments...
</div>

<!-- Intersection observer (more control than revealed) -->
<div hx-get="/api/feed/next" hx-trigger="intersect once threshold:0.5">
  Loading...
</div>

<!-- Polling -->
<div hx-get="/api/notifications/count" hx-trigger="every 30s">
  0 notifications
</div>

<!-- Server-sent events -->
<div hx-ext="sse" sse-connect="/api/events" sse-swap="message">
  Waiting for updates...
</div>

<!-- Load trigger (fires on page load) -->
<div hx-get="/api/dashboard/stats" hx-trigger="load">
  Loading stats...
</div>

<!-- Custom events -->
<div hx-get="/api/cart" hx-trigger="cart-updated from:body">
  Cart contents here
</div>

Server-Side Integration

Response Patterns

The server returns HTML fragments, not full pages.

python
# Python (Flask) example
@app.route('/api/users', methods=['GET'])
def list_users():
    users = User.query.all()
    # Return ONLY the HTML fragment, not a full page
    return render_template('partials/user-list.html', users=users)

@app.route('/api/users', methods=['POST'])
def create_user():
    user = User(email=request.form['email'])
    db.session.add(user)
    db.session.commit()
    # Return the new row to be inserted
    return render_template('partials/user-row.html', user=user)

@app.route('/api/users/<int:id>', methods=['DELETE'])
def delete_user(id):
    User.query.get_or_404(id).delete()
    db.session.commit()
    # Return empty string - htmx will remove the target element
    return ''
go
// Go (net/http) example
func handleSearch(w http.ResponseWriter, r *http.Request) {
    query := r.URL.Query().Get("q")
    results := searchProducts(query)

    // Check if this is an HTMX request
    if r.Header.Get("HX-Request") == "true" {
        // Return only the results fragment
        tmpl.ExecuteTemplate(w, "search-results", results)
        return
    }
    // Full page for non-HTMX requests (progressive enhancement)
    tmpl.ExecuteTemplate(w, "search-page", results)
}
Response Headers
python
from flask import make_response

@app.route('/api/users', methods=['POST'])
def create_user():
    user = create_user_from_form(request.form)
    response = make_response(render_template('partials/user-row.html', user=user))

    # Retarget: supersede hx-target from the client
    response.headers['HX-Retarget'] = '#user-table tbody'

    # Reswap: supersede hx-swap strategy
    response.headers['HX-Reswap'] = 'afterbegin'

    # Trigger: fire a client-side event
    response.headers['HX-Trigger'] = 'showToast'
    # Or with data:
    response.headers['HX-Trigger'] = json.dumps({
        'showToast': {'message': 'User created', 'type': 'success'}
    })

    # Redirect: full page navigation
    # response.headers['HX-Redirect'] = '/users'

    # Push URL: update browser URL bar without full navigation
    response.headers['HX-Push-Url'] = f'/users/{user.id}'

    return response

Common Application Patterns

Search with Debounce
html
<input type="search"
       name="q"
       placeholder="Search products..."
       hx-get="/search"
       hx-trigger="input changed delay:300ms, search"
       hx-target="#search-results"
       hx-indicator="#search-spinner">

<span id="search-spinner" class="htmx-indicator">Searching...</span>
<div id="search-results"></div>
Infinite Scroll
html
<!-- Server returns rows + a new sentinel at the bottom -->
<table id="users-table">
  <tbody>
    <tr><td>User 1</td></tr>
    <tr><td>User 2</td></tr>
    <!-- ... more rows ... -->

    <!-- Sentinel row: loads next page when visible -->
    <tr hx-get="/api/users?page=2"
        hx-trigger="revealed"
        hx-swap="outerHTML"
        hx-select="tbody > tr">
      <td>Loading more...</td>
    </tr>
  </tbody>
</table>
Click-to-Edit Pattern
html
<!-- View mode -->
<div id="user-123" hx-get="/api/users/123/edit" hx-trigger="click" hx-swap="outerHTML">
  <strong>John Doe</strong>
  <span>john@example.com</span>
  <small>(click to edit)</small>
</div>

<!-- Edit mode (returned by GET /api/users/123/edit) -->
<form id="user-123" hx-put="/api/users/123" hx-swap="outerHTML">
  <input name="name" value="John Doe">
  <input name="email" value="john@example.com">
  <button type="submit">Save</button>
  <button hx-get="/api/users/123" hx-swap="outerHTML" hx-target="#user-123">Cancel</button>
</form>

<!-- After save (returned by PUT /api/users/123) - back to view mode -->
<div id="user-123" hx-get="/api/users/123/edit" hx-trigger="click" hx-swap="outerHTML">
  <strong>John Doe</strong>
  <span>john@example.com</span>
  <small>(click to edit)</small>
</div>
Bulk Operations
html
<form hx-post="/api/users/bulk-delete" hx-target="#user-table" hx-swap="innerHTML"
      hx-confirm="Delete selected users?">
  <table id="user-table">
    <thead>
      <tr>
        <th><input type="checkbox" onclick="toggleAll(this)"></th>
        <th>Name</th>
        <th>Email</th>
      </tr>
    </thead>
    <tbody>
      <tr>
        <td><input type="checkbox" name="ids" value="1"></td>
        <td>John</td>
        <td>john@example.com</td>
      </tr>
      <!-- more rows -->
    </tbody>
  </table>
  <button type="submit">Delete Selected</button>
</form>

<script>
function toggleAll(source) {
  document.querySelectorAll('input[name="ids"]').forEach(cb => cb.checked = source.checked);
}
</script>
Tabs with URL Updates
html
<div class="tabs" hx-target="#tab-content" hx-swap="innerHTML" hx-push-url="true">
  <a hx-get="/tabs/overview" class="active">Overview</a>
  <a hx-get="/tabs/settings">Settings</a>
  <a hx-get="/tabs/billing">Billing</a>
</div>
<div id="tab-content">
  <!-- Tab content loaded here -->
</div>

Progressive Enhancement

The key principle: the application works without JavaScript, then HTMX enhances it.

html
<!-- Without JS: normal form submission (full page reload) -->
<!-- With HTMX: partial update, no page reload -->
<form method="post" action="/api/users"
      hx-post="/api/users"
      hx-target="#user-list"
      hx-swap="afterbegin">
  <input name="email" type="email" required>
  <button type="submit">Add User</button>
</form>

<!-- Without JS: normal link navigation -->
<!-- With HTMX: partial page load -->
<a href="/users/123"
   hx-get="/users/123"
   hx-target="#main-content"
   hx-push-url="true">
  View User
</a>

Server detects and responds appropriately:

python
@app.route('/users/<int:id>')
def get_user(id):
    user = User.query.get_or_404(id)
    if request.headers.get('HX-Request'):
        return render_template('partials/user-detail.html', user=user)
    return render_template('full-page/user-detail.html', user=user)

HTMX Extensions

Useful Extensions
ExtensionPurposeExample
sseServer-Sent EventsReal-time updates without polling
wsWebSocket supportBidirectional real-time
json-encSend JSON instead of form dataAPI integration
loading-statesGranular loading indicatorsDisable buttons during request
head-supportUpdate <head> elementsChange page title on navigation
preloadPreload content on hoverFaster perceived navigation
response-targetsDifferent targets for error responsesShow errors in specific location
Response Targets (Error Handling)
html
<form hx-post="/api/users"
      hx-target="#user-list"
      hx-target-422="#form-errors"
      hx-target-500="#server-error"
      hx-ext="response-targets">
  <div id="form-errors"></div>
  <input name="email" type="email" required>
  <button type="submit">Add User</button>
</form>
<div id="server-error"></div>

Performance Tips

  1. Keep HTML fragments small: Return only the changed part of the page, not large sections.
  2. Use hx-select: Extract only what you need from a larger response.
  3. Debounce inputs: Always use delay: on keyup/input triggers.
  4. Use hx-indicator: Show loading states so users know something is happening.
  5. Preload on hover: Use the preload extension for navigation links.
  6. Out-of-band swaps: Update multiple page areas with one response using hx-swap-oob.

Common Anti-Patterns

  1. Returning full pages for HTMX requests: Every HTMX response should be a fragment. Use HX-Request header to detect HTMX requests and respond accordingly.

  2. Client-side state in JavaScript: If you are building significant client-side state alongside HTMX, you are fighting the architecture. Move state to the server.

  3. Not using hx-boost: For simple pages, hx-boost="true" on the body converts all links and forms to AJAX requests automatically. Zero configuration progressive enhancement.

  4. skipping about non-JS users: HTMX is progressive enhancement. Ensure forms have action and method attributes and links have href attributes as fallbacks.

  5. Over-polling: hx-trigger="every 1s" on many elements creates excessive server load. Use SSE or WebSocket for truly real-time needs. Poll at reasonable intervals (10-60s) for near-real-time.

Show full SKILL.md (270 more words)Show less

HTMX Developer Checklist

  • HTMX loaded from CDN or bundled (~14KB gzipped)
  • Server returns HTML fragments for HTMX requests
  • Progressive enhancement: pages work without JavaScript
  • Swap strategies chosen appropriately for each interaction
  • Loading indicators shown during requests (hx-indicator)
  • Input triggers debounced (delay:300ms)
  • Error responses handled with response-targets extension
  • URL bar updates with hx-push-url for navigable interactions
  • Server detects HX-Request header for fragment vs full page responses
  • CSS transitions configured for smooth swap animations

When to Use

Use this skill when:

  • Designing or implementing htmx developer solutions
  • Reviewing or improving existing htmx developer approaches
  • Making architectural or implementation decisions about htmx developer
  • Learning htmx developer patterns and best practices
  • Troubleshooting htmx developer-related issues

Do NOT use this skill when:

  • The question is about a fundamentally different technology domain
  • A more specific sibling skill covers the exact topic needed
  • The user needs a complete hands-on tutorial rather than expert guidance

Output Format

markdown
# Htmx Developer Analysis

## Context Assessment
[Situation summary and constraints]

## Recommended Approach
[Primary recommendation with rationale]

## Implementation Steps
1. [Step with specific details]
2. [Step with specific details]
3. [Step with specific details]

## Trade-offs and Considerations
- [Key trade-off 1]
- [Key trade-off 2]

## Next Steps
- [Immediate action item]
- [Follow-up action item]

Example

Input: "Help me implement htmx developer for a medium-scale production application"

Output: A structured analysis covering current state assessment, recommended htmx developer approach with specific patterns, implementation roadmap with milestones, and risk mitigation strategies tailored to the application scale and constraints.

Edge Cases

  • Legacy system integration: When htmx developer must coexist with legacy approaches, provide a gradual migration path rather than a complete rewrite
  • Scale mismatch: When the solution complexity exceeds the project scale, recommend a simpler approach and note when to revisit
  • Team skill gaps: When the team lacks experience with the recommended approach, include learning resources and simpler alternatives
  • Conflicting requirements: When constraints conflict (e.g., performance vs. maintainability), explicitly state the trade-off and recommend based on stated priorities

© FerroxLabs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in src/process/resources/skills-library/bodies/skills/web-development/htmx-developer of FerroxLabs/wayland.

Open the folder on GitHubat commit 4c030c7

Compare with similar skills

Htmx Developer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Htmx Developer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Htmx Developer this skillFerroxLabs/wayland608—~4kAutomated safety check: PassApache-2.0
MCP Developmentcoollabsio/coolify63k1 repos~949Automated safety check: PassMIT
Vue Component Developmentgdarko/laravel-vue-starter145—~1.1kAutomated safety check: PassMIT
Form Validationvibeeval/vibecosystem531—~3kAutomated safety check: PassMIT
Rails Design Systempproenca/dot-skills214—~2.4kAutomated safety check: PassMIT
API Patternsbybren-llc/safe-agentic-workflow421—~1.6kAutomated safety check: PassMIT

Similar skills

  • MCP Development

    coollabsio/coolify

    A skill your agent uses for Laravel MCP development. An agent skill from coollabsio/coolify.

    63k GitHub starsUsed in 1 repo~949 tokens
    Frontend & DesignAuto-check passed
  • Vue Component Development

    gdarko/laravel-vue-starter

    Activate when creating or modifying Vue 3 components, pages, layouts, stores, or services in the frontend.

    145 GitHub stars~1.1k tokensUpdated 6 mo ago
    Frontend & DesignAuto-check passed
  • Form Validation

    vibeeval/vibecosystem

    React Hook Form + Zod integration, multi-step forms, optimistic validation, server-side error mapping, and file upload patterns.

    531 GitHub stars~3k tokensUpdated 2 mo ago
    Frontend & DesignAuto-check passed
  • Rails Design System

    pproenca/dot-skills

    Ruby on Rails design system guidelines for building consistent, maintainable UI with minimal abstraction.

    214 GitHub stars~2.4k tokensUpdated 1 mo ago
    Frontend & DesignAuto-check passed
  • API Patterns

    bybren-llc/safe-agentic-workflow

    API route implementation patterns with RLS, Zod validation, and error handling.

    421 GitHub stars~1.6k tokensUpdated 2 mo ago
    Backend & APIsAuto-check passed
  • Opinionated Nextjs Patterns

    pproenca/dot-skills

    Opinionated, backend-agnostic Next.js 16 (App Router) architecture — authorization at the data layer, server-side loading with cache()+Promise.all, mutations through next-safe-action + typed route…

    214 GitHub stars~3k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

More from FerroxLabs/wayland

All 1,194 skills in this repo
  • Star Office Helper

    FerroxLabs/wayland

    Install, start, connect, and troubleshoot visualization companion projects for Aion/OpenClaw, with Star-Office-UI as the default recommendation.

    608 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check: notes
  • Openclaw Setup

    FerroxLabs/wayland

    OpenClaw usage expert: Helps you install, deploy, configure, and use OpenClaw personal AI assistant.

    608 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed
  • Tvcontrol Setup

    FerroxLabs/wayland

    Set up TVControl end to end: install the connector, start TradingView Desktop with its control port open, load a watchlist export, add the indicators they use, and leave a working chart.

    608 GitHub stars~5.7k tokensUpdated yesterday
    Auto-check passed
  • Ab Testing Specialist

    FerroxLabs/wayland

    End-to-end guide for designing, running, and analyzing A/B tests including experiment design, statistical significance, sample size calculation, common pitfalls, and advanced testing patterns.

    608 GitHub stars~3.7k tokensUpdated yesterday
    Auto-check passed
  • Academic Writer

    FerroxLabs/wayland

    Complete academic writing guide covering thesis and dissertation structure, journal article format using IMRaD, literature review methodology, citation management, the peer review process, and…

    608 GitHub stars~4.5k tokensUpdated yesterday
    Auto-check passed
  • Accessibility Auditor

    FerroxLabs/wayland

    Web accessibility expertise covering WCAG 2.2 conformance, audit methodology, ARIA patterns, keyboard navigation, screen reader testing, focus management, form accessibility, and automated vs manual…

    608 GitHub stars~4.1k tokensUpdated yesterday
    Auto-check passed

Questions about Htmx Developer

What does Htmx Developer do?

HTMX development expertise covering hypermedia-driven application patterns, progressive enhancement, server-side rendering integration, HTMX attributes and extensions, partial page updates, form…. Htmx Developer is an agent skill from FerroxLabs/wayland. HTMX development expertise covering hypermedia-driven application patterns, progressive enhancement, server-side rendering integration, HTMX attributes and extensions, partial page updates, form handling, real-time features, and migration from SPA frameworks.

When should I use Htmx Developer?

Htmx Developer fits situations like: the user asks about htmx developer; htmx developer best practices; needs guidance on htmx developer implementation; the user needs a different specialized skill.

How do I install Htmx Developer in Claude Code?

Run `npx skills add FerroxLabs/wayland --skill htmx-developer -a claude-code`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/web-development/htmx-developer in FerroxLabs/wayland) into .claude/skills/htmx-developer in your project. Claude Code loads it when a task matches its description.

How do I install Htmx Developer in Codex?

Run `npx skills add FerroxLabs/wayland --skill htmx-developer -a codex`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/web-development/htmx-developer in FerroxLabs/wayland) into .agents/skills/htmx-developer in your project. Codex loads it when a task matches its description.

Can I use Htmx Developer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FerroxLabs/wayland --skill htmx-developer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/htmx-developer, .gemini/skills/htmx-developer, .github/skills/htmx-developer and .opencode/skills/htmx-developer in your project.

What does Htmx Developer need to run?

SKILL.md names no scripts, command-line tools or credentials: Htmx Developer is instructions for the agent only. Our summary lists: Python 3.

Does Htmx Developer access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Htmx Developer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Htmx Developer use?

Htmx Developer is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Htmx Developer use?

About 4k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Htmx Developer?

Skills that share tags, products or a category with Htmx Developer: MCP Development (coollabsio/coolify, 63k stars), Vue Component Development (gdarko/laravel-vue-starter, 145 stars), Form Validation (vibeeval/vibecosystem, 531 stars) and Rails Design System (pproenca/dot-skills, 214 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Htmx Developer?

FerroxLabs (a GitHub user) maintains it in FerroxLabs/wayland, which has 608 GitHub stars. The repository holds 1,194 skills in this directory. The repository was last updated on October 6, 2026.

Source: FerroxLabs/wayland on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.