MCP Development
coollabsio/coolify
A skill your agent uses for Laravel MCP development. An agent skill from coollabsio/coolify.
HTMX development expertise covering hypermedia-driven application patterns, progressive enhancement, server-side rendering integration, HTMX attributes and extensions, partial page updates, form…
$ npx skills add FerroxLabs/wayland --skill htmx-developer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install FerroxLabs/wayland htmx-developer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "htmx-developer" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/web-development/htmx-developer into .claude/skills/htmx-developer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "htmx-developer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/web-development/htmx-developerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add FerroxLabs/wayland --skill htmx-developer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install FerroxLabs/wayland htmx-developer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .agents/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/web-development/htmx-developer .agents/skills/htmx-developer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "htmx-developer" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/web-development/htmx-developer into .agents/skills/htmx-developer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "htmx-developer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add FerroxLabs/wayland --skill htmx-developer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install FerroxLabs/wayland htmx-developer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/web-development/htmx-developer .cursor/skills/htmx-developer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "htmx-developer" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/web-development/htmx-developer into .cursor/skills/htmx-developer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "htmx-developer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/FerroxLabs/wayland.git --path src/process/resources/skills-library/bodies/skills/web-development/htmx-developer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add FerroxLabs/wayland --skill htmx-developer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install FerroxLabs/wayland htmx-developer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/web-development/htmx-developer .gemini/skills/htmx-developer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "htmx-developer" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/web-development/htmx-developer into .gemini/skills/htmx-developer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "htmx-developer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install FerroxLabs/wayland htmx-developerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add FerroxLabs/wayland --skill htmx-developer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .github/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/web-development/htmx-developer .github/skills/htmx-developer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "htmx-developer" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/web-development/htmx-developer into .github/skills/htmx-developer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "htmx-developer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add FerroxLabs/wayland --skill htmx-developer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install FerroxLabs/wayland htmx-developer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/web-development/htmx-developer .opencode/skills/htmx-developer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "htmx-developer" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/web-development/htmx-developer into .opencode/skills/htmx-developer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "htmx-developer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
htmx-developerHTMX 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. 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.
6 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 4c030c7. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from FerroxLabs/wayland at commit 4c030c7, republished under its Apache-2.0 licence (© FerroxLabs). 813 words, ~4,027 tokens.
.claude/skills/htmx-developer/SKILL.md (or your agent's skills folder).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.
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)| Aspect | HTMX | React/Vue/Svelte |
|---|---|---|
| Server sends | HTML fragments | JSON data |
| Rendering | Server-side | Client-side |
| State management | Server (session/DB) | Client (Redux/Zustand) |
| JavaScript needed | Minimal (HTMX + extensions) | Significant (framework + deps) |
| Build step | None required | Required (Webpack/Vite) |
| SEO | Built-in (server-rendered) | Requires SSR/SSG setup |
| Learning curve | HTML attributes | Framework + ecosystem |
| Bundle size | ~14KB (HTMX) | 50-200KB+ (framework + deps) |
| Offline support | Limited | Good (with service worker) |
| Rich interactivity | Good for most apps | Excellent |
<!-- 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>| Strategy | Behavior | Use Case |
|---|---|---|
innerHTML | Replace children of target | Update a list, refresh a section |
outerHTML | Replace the entire target | Replace an element with an edited version |
afterbegin | Prepend inside target | Add item to top of list |
beforeend | Append inside target | Add item to bottom of list |
beforebegin | Insert before target | Add a row above |
afterend | Insert after target | Add a row below |
delete | Delete the target | Remove an element |
none | Don't swap (still fires events) | Trigger side effects only |
<!-- 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>The server returns HTML fragments, not full pages.
# 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 (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)
}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<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><!-- 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><!-- 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><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><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>The key principle: the application works without JavaScript, then HTMX enhances it.
<!-- 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:
@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)| Extension | Purpose | Example |
|---|---|---|
sse | Server-Sent Events | Real-time updates without polling |
ws | WebSocket support | Bidirectional real-time |
json-enc | Send JSON instead of form data | API integration |
loading-states | Granular loading indicators | Disable buttons during request |
head-support | Update <head> elements | Change page title on navigation |
preload | Preload content on hover | Faster perceived navigation |
response-targets | Different targets for error responses | Show errors in specific location |
<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>hx-select: Extract only what you need from a larger response.delay: on keyup/input triggers.hx-indicator: Show loading states so users know something is happening.hx-swap-oob.Returning full pages for HTMX requests: Every HTMX response should be a fragment. Use HX-Request header to detect HTMX requests and respond accordingly.
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.
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.
skipping about non-JS users: HTMX is progressive enhancement. Ensure forms have action and method attributes and links have href attributes as fallbacks.
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.
hx-indicator)delay:300ms)response-targets extensionhx-push-url for navigable interactionsHX-Request header for fragment vs full page responsesUse this skill when:
Do NOT use this skill when:
# 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]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.
© 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
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
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Htmx Developer this skillFerroxLabs/wayland | 608 | — | ~4k | Automated safety check: Pass | Apache-2.0 | |
| MCP Developmentcoollabsio/coolify | 63k | 1 repos | ~949 | Automated safety check: Pass | MIT | |
| Vue Component Developmentgdarko/laravel-vue-starter | 145 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Form Validationvibeeval/vibecosystem | 531 | — | ~3k | Automated safety check: Pass | MIT | |
| Rails Design Systempproenca/dot-skills | 214 | — | ~2.4k | Automated safety check: Pass | MIT | |
| API Patternsbybren-llc/safe-agentic-workflow | 421 | — | ~1.6k | Automated safety check: Pass | MIT |
coollabsio/coolify
A skill your agent uses for Laravel MCP development. An agent skill from coollabsio/coolify.
gdarko/laravel-vue-starter
Activate when creating or modifying Vue 3 components, pages, layouts, stores, or services in the frontend.
vibeeval/vibecosystem
React Hook Form + Zod integration, multi-step forms, optimistic validation, server-side error mapping, and file upload patterns.
pproenca/dot-skills
Ruby on Rails design system guidelines for building consistent, maintainable UI with minimal abstraction.
bybren-llc/safe-agentic-workflow
API route implementation patterns with RLS, Zod validation, and error handling.
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…
FerroxLabs/wayland
Install, start, connect, and troubleshoot visualization companion projects for Aion/OpenClaw, with Star-Office-UI as the default recommendation.
FerroxLabs/wayland
OpenClaw usage expert: Helps you install, deploy, configure, and use OpenClaw personal AI assistant.
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.
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.
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…
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…
Categories
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.
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.
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.
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.
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.
SKILL.md names no scripts, command-line tools or credentials: Htmx Developer is instructions for the agent only. Our summary lists: Python 3.
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.
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.
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.
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.
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.
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.