Add Web Components patterns to web integration skill #13
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adds comprehensive Web Components (Custom Elements) patterns as a framework-agnostic alternative to framework-specific integration patterns.
What's Added
New Section in SKILL.md:
connectedCallback/disconnectedCallbackobservedAttributes+attributeChangedCallbackfor live updatesPatterns Covered
Basic Web Component
Usage Across Frameworks
The same component works without modification in:
Advanced Patterns
getMap()Benefits
✅ Framework-agnostic - write once, use everywhere
✅ No framework lock-in - web platform standard
✅ Maximum portability - ideal for component libraries
✅ Future-proof - based on web standards
✅ Encapsulation - clear API via attributes
When to Use
When to Use Framework Components Instead
Testing
Addresses user request to add Web Components as framework-agnostic alternative to framework-specific patterns.