Skip to content

Latest commit

 

History

History
113 lines (77 loc) · 6.15 KB

CHANGELOG.md

File metadata and controls

113 lines (77 loc) · 6.15 KB

Changelog

0.4.0

Minor Changes

  • 5cb679b: Add multi-dimensional health scoring engine with source-level accessibility analysis
    • 6 CEM-native dimensions: CEM Completeness, Accessibility, Type Coverage, API Surface Quality, CSS Architecture, Event Architecture
    • Enterprise grade algorithm with critical dimension gates preventing score gaming
    • Source-level accessibility scanner reading component source files for ARIA bindings, keyboard handling, focus management, form internals, live regions, and screen reader support
    • Deep mixin-aware scanner following CEM superclass/mixin declarations and a11y-relevant imports through full inheritance chains
    • Honest scoring: empty CEM data returns null (excluded from weighted average) instead of inflating to 100/100
    • CEM accessibility analyzer reweighted for CEM-realistic scoring
    • New MCP tools: score_component_multi_dimensional, score_all_multi_dimensional, audit_library
    • JSONL audit report generation
    • Validated against 14 real-world component libraries across Lit, FAST, Stencil, and vanilla architectures

0.3.0

Minor Changes

  • f5bbbe7: Add /update-helixir slash command skill that allows users to self-update the helixir MCP server from npm in one step, with version detection, update, verification, and restart instructions.

[0.2.0] - 2026-03-13

Minor Changes

  • 2308edf: - Migrate release pipeline from semantic-release to @changesets/cli for explicit per-PR version control
    • Add Zod schema validation for design token files against the W3C DTCG spec
    • Remove @semantic-release/* dependencies; add @changesets/cli

Patch Changes

  • 03dabcf: Add root package to pnpm-workspace.yaml so changesets can resolve the helixir package during version and publish.

All notable changes to helixir (formerly wc-tools) will be documented in this file.

The format follows Keep a Changelog, and this project adheres to Semantic Versioning.

[0.1.0] - 2026-03-01

Added

MCP server

  • MCP server for web component Custom Elements Manifest (CEM) analysis — gives AI agents full situational awareness of any web component library.
  • Multi-library support: Shoelace, Lit, Stencil, FAST, Spectrum, Material, Vaadin, Carbon, Ionic, Lion, Fluent UI, and PatternFly.
  • CDN CEM resolution via resolve_cdn_cem — fetch and cache CEM files from unpkg/jsDelivr without a local install.
  • Watch mode (--watch) — automatically reloads the CEM when the source file changes.
  • helixir init CLI command — interactive setup wizard to generate a mcpwc.config.json.

Discovery tools

  • list_components — list all custom elements registered in the Custom Elements Manifest.
  • find_component — semantic search for components by name, description, or member names using token-overlap scoring.
  • get_library_summary — library overview: component count, average health score, and grade distribution.
  • list_events — list all events exposed across all components.
  • list_slots — list all named slots across all components.
  • list_css_parts — list all CSS shadow parts across all components.
  • list_components_by_category — filter components by category tag.

Component tools

  • get_component — retrieve full metadata for a component including members, events, slots, CSS parts, and CSS custom properties.
  • validate_cem — validate CEM documentation completeness for a component; returns a 0–100 score and a list of issues.
  • suggest_usage — generate an HTML usage snippet showing key attributes with default values.
  • generate_import — generate side-effect and named import statements from CEM exports and package.json.
  • get_component_narrative — plain-language description of a component's purpose and API.
  • get_prop_constraints — list property constraints (allowed values, types, defaults) for a component.
  • find_components_by_token — find components that reference a specific design token.
  • get_component_dependencies — list components that a given component depends on.
  • find_components_using_token — reverse lookup: find all components that use a given CSS custom property.

Health tools

  • score_component — health score for a single component: grade, dimension breakdown, and issues.
  • score_all_components — health scores for every component in the library in one call.
  • get_health_trend — component health trend over the last N days with trend direction and change percentage.
  • get_health_diff — before/after health comparison between the current branch and a base branch.
  • analyze_accessibility — accessibility analysis for a component: ARIA roles, keyboard support, and WCAG coverage.

Safety tools

  • diff_cem — per-component CEM diff between branches; classifies breaking changes (removals, type changes) vs. non-breaking additions.
  • check_breaking_changes — breaking-change scan across all components vs. a base branch with per-component emoji status summary.

TypeScript tools

  • get_file_diagnostics — TypeScript diagnostics for a single source file.
  • get_project_diagnostics — full TypeScript diagnostic pass across the entire project.

Token tools

  • get_design_tokens — list all design tokens from the configured tokens file, optionally filtered by category.
  • find_token — search for a design token by name or value.

Framework & validation tools

  • detect_framework — detect the web component authoring framework (Lit, Stencil, FAST, etc.) used in the project.
  • validate_usage — validate a component usage snippet against the CEM (attribute names, types, required props).

Composition & story tools

  • get_composition_example — generate a multi-component composition example showing components used together.
  • generate_story — generate a Storybook story (CSF format) for a component.

Bundle & benchmark tools

  • estimate_bundle_size — estimate the tree-shaken bundle size contribution of one or more components.
  • Benchmark handler — compare component health metrics across branches or snapshots.
  • Compare handler — side-by-side library comparison for evaluating component coverage and quality.