HAX Web Component Development
SkillMediaDevelop HAX-capable web components using LitElement, DDD design system, and HAXSchema. Use when scaffolding new components, adding HAX editor support, auditing accessibility, or applying DDD tokens to elements in the webcomponents monorepo.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the HAX Web Component Development skill
What this skill tells your AI
The instructions your AI receives, as published by haxtheweb/haxcms-php in .well-known/agent-skills/hax-webcomponent-dev/SKILL.md and read by ahel’s review.
Develop HAX-capable web components using LitElement, DDD design system, and HAXSchema.
When to Use
- Scaffolding a new component in the webcomponents monorepo
- Adding or updating
haxProperties/demoSchema - Auditing a component for DDD compliance or accessibility
- Refactoring legacy SimpleColors usage to DDD tokens
- Fixing build issues with HAXCMSLitElement themes
- Reviewing component JavaScript for Polymer parser compatibility
How It Works
- Scaffold: Always use
hax webcomponent my-element --yinstead of manual creation. Do not create directories or files manually in the monorepo. - Import DDD: Use
import '@haxtheweb/d-d-d/d-d-d.js'and extendDDDdirectly (neverDDD(LitElement)). With mixins, DDD must be the base class:class MyEl extends SomeMixin(DDD) {}. - Implement HAXSchema: Add
haxProperties()withdemoSchemafor editor examples. Use demoSchema and HAX helper methods to create valid demos with appropriate tag names, properties, and slotted content. - Style with DDD: Use
ddd-prefixed CSS custom properties for spacing, colors, typography, and icon sizes. Only use SimpleColors where explicitly needed as fallback. - Audit: Check DDD token usage, ARIA attributes, keyboard navigation, semantic HTML, and dark mode compliance.
- Build: Run
yarn run buildafter changes to HAXCMSLitElement themes. Do not manually editcustom-elements.json— it is auto-generated.
JavaScript Standards
- Use
globalThisinstead ofwindowfor global references - Do not use optional chaining (
?.) — the Polymer parser has issues with this syntax - Use single quotes, avoid semicolons where possible, prefer functional patterns
- Use Prettier for consistent formatting
- No TypeScript — pure JavaScript with LitElement
- When using third-party libraries, import the pre-compiled JavaScript distribution
Component Audits
When working on any component, perform these checks:
- DDD Design System: Verify proper usage of design tokens
- Accessibility: Check ARIA attributes, keyboard navigation, semantic markup
- HAX Schema: Ensure complete and accurate haxProperties implementation
- Performance: Review bundle size, lazy loading opportunities
- Browser Compatibility: Test across supported browser versions
References
- For DDD token reference:
references/ddd-tokens.md - For HAXSchema examples:
references/haxschema-examples.md
Signals
- GitHub stars
- 129
- Forks
- 57
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
hax-webcomponent-dev- Source
- github.com/haxtheweb/haxcms-php