Frontend Web Components
Use when the user asks about custom elements, shadow DOM, slots and templates, ElementInternals, form-associated elements, declarative shadow DOM or framework-free cross-framework components. Produces standards-based web components. Not for Lit (use frontend-lit) or Stencil (use stencil).
Install
npx skills add j4flmao/agent-skills --skill frontend-web-componentsgit clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/frontend/universal/web-components ~/.claude/skills/frontend-web-componentsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Web Components
## Purpose
Build vanilla web components using the native Custom Elements API: encapsulated shadow DOM, typed lifecycle, form participation via ElementInternals, and cross-framework compatibility patterns.
## Agent Protocol
### Trigger
Exact user phrases: "web component", "custom element", "shadow DOM", "HTML template", "CustomElementsRegistry", "ElementInternals", "form-associated element", "cross-framework component", "vanilla web component".
### Input Context
Before activating, verify:
- No Lit, Stencil, or other web component library in dependencies.
- Whether the component needs shadow DOM or light DOM.
- Whether the component participates in a form (ElementInternals).
- Target browsers (check CustomElementRegistry and ElementInternals support).
### Output Artifact
No file output. Produces element design, encapsulation strategy, framework integration as text.
### Response Format
```
Element Design: {name} — {purpose}
Encapsulation: {open shadow DOM / closed / light DOM}
Framework Integration: {attribute reflection, event mapping}
```
No preamble. No postamble. No explanations. No filler/hedging/transitions. Compress output — why use many token when few do trick.
### Completion Criteria
- [ ] Custom element registered via customElements.define() with kebab-case name.
- [ ] Lifecycle methods implemented (connected, disconnected, attributeChanged).
- [ ] observedAttributes defined for reactive attribute sync.Details
- Skill name
frontend-web-components- Repository
- j4flmao/agent-skills
- Path
skills/frontend/universal/web-components/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Frontend Web Components skill do?
Use when the user asks about custom elements, shadow DOM, slots and templates, ElementInternals, form-associated elements, declarative shadow DOM or framework-free cross-framework components. Produces standards-based web components. Not for Lit (use frontend-lit) or Stencil (use stencil).
How do I install the Frontend Web Components skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill frontend-web-components. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Frontend Web Components popular?
It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.
Related skills
Agent Observability
45j4flmao/agent-skills
Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).
AI Agent Architectures
45j4flmao/agent-skills
Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).
AI Agent Core Loop
45j4flmao/agent-skills
Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).
Htmx
45j4flmao/agent-skills
Use when the user asks about htmx, hx-get, hx-post, hx-swap, hx-target, hypermedia/HATEOAS apps or server-driven partial page updates. Produces htmx attributes, HTML-fragment server responses and CSRF-safe request handling. Not for client-side reactivity inside a page (use alpinejs).
Frontend Vue Patterns
45j4flmao/agent-skills
Use when the user asks about Vue composables, provide/inject, Vue reactivity pitfalls, custom directives, Vue Router guards and lazy routes, Pinia setup stores, renderless components or scoped slots. Produces reusable Vue 3 patterns. Not for overall Vue project structure (use vue-architecture).
Input Systems
45j4flmao/agent-skills
Use when the user asks about a game input system, action mapping, key rebinding, gamepad input, touch gestures, IME text input, haptics or input latency. Produces device-agnostic input architecture tied to the simulation tick. Not for menu accessibility audits (use design-accessibility) or Unity-specific setup (use unity).
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.