agentsclimarketplace

Lang html

Skill arhuman/claude-plugins/plugins/10x/skills/lang-html

Install
npx -y skills add arhuman/claude-plugins --skill lang-html

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

HTML, HTMX, and CSS best practices following CUBE CSS methodology and Every Layout primitives. Use when working with HTML templates, HTMX interactions, CSS styling, or building server-rendered UI components.

SKILL.md

3.4 KB, 762 tokens by cl100k_base, as published. Nobody here has run it

lang-html

This skill defines rules for writing maintainable, progressively enhanced HTML with CUBE CSS and Every Layout.

Reference Guide

Load the relevant reference when the task involves:

TopicFileLoad When
CUBE CSSreferences/cube-css.mdwriting or reviewing CSS, class naming, cascade decisions
Every Layoutreferences/every-layout.mdlayout primitives: stack, cluster, sidebar, grid, center, box
HTMXreferences/htmx.mdHTMX attributes, partial rendering, swap strategies, events

Core Philosophy

  • HTML is the foundation. CSS enhances. HTMX progressively adds interactivity.
  • Prefer semantic HTML over <div> soup.
  • The cascade is a feature — use it, don't fight it.
  • Layouts are solved with composable primitives (Every Layout), not one-off utilities.

CSS Architecture: CUBE CSS

Structure all CSS in four layers:

  1. Composition — layout primitives (.stack, .cluster, .sidebar, .grid, .center, .box)
  2. Utility — single-purpose design tokens (.text-step-1, .bg-surface, .color-accent)
  3. Block — component-scoped styles (.card, .nav, .hero)
  4. Exception — overrides using data-* attributes ([data-variant="inverted"])

Apply classes in that order: composition first, utilities second, blocks third, exceptions last.

Every Layout: Use These Primitives

Do not write ad-hoc layout CSS. Use these intrinsic primitives:

PrimitiveUse for
.stackVertical spacing between siblings
.boxPadding + optional border for a contained region
.centerHorizontal centering with max-width
.clusterWrapping flex groups (tags, buttons, nav items)
.sidebarTwo-column layout with one fixed-width side
.gridAuto-responsive grid without media queries
.frameFixed aspect-ratio media containers
.reelHorizontal scrolling rows
.iconInline SVG icon with text sizing

See references/every-layout.md for CSS implementations.

MUST DO

  • Use semantic HTML elements (<nav>, <main>, <article>, <section>, <aside>, <header>, <footer>)
  • Define spacing, color, and typography via custom properties (--space-s, --color-text, --step-0)
  • Use data-* attributes for state/variant exceptions, not modifier classes (card--dark)
  • Use hx-boost on <a> and <form> elements before reaching for more specific HTMX attributes
  • Scope block CSS to a single class selector matching the HTML element's role
  • Write layout CSS using gap, not margin between siblings
  • Validate that HTMX targets exist on the page before wiring hx-target

MUST NOT

  • Write inline styles (except generated/dynamic values that cannot be in CSS)
  • Use utility classes for layout spacing — use Every Layout primitives instead
  • Nest block selectors more than one level deep
  • Use !important except in utility classes (where it is intentional)
  • Use class names that encode visual appearance (red-text, big-button) — use semantics or tokens
  • Add HTMX attributes without defining a clear fallback for no-JS environments
  • Use hx-swap="outerHTML" on the element that triggers the request (causes self-deletion)

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.