mc-table-legacy-audit

Audit legacy mc-table implementations and generate a parity matrix for HTML table migration.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/obaDev95/myf-agent-skills --skill mc-table-legacy-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mc-table-legacy-audit
Source: https://github.com/obaDev95/myf-agent-skills/tree/main/skills/mc-table-legacy-audit
Command: npx skills add https://github.com/obaDev95/myf-agent-skills --skill mc-table-legacy-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-migration inventory and parity-scoping for legacy mc-table usage, producing a parity matrix that guides the HTML table migration pipeline.

Core Features & Use Cases

  • Generates a complete parity matrix (columns, slots, props, conditionals, behaviors, side-effects) to verify what the legacy mc-table renders before rewriting to a11y-friendly <table class="mds-table">.
  • Serves as a read-only audit to validate migration readiness, detect omissions, and document legacy behavior for migration planning.
  • Useful for audits across views and components where mc-table is present, ensuring no parity gaps are introduced during migration.

Quick Start

Run this audit against the legacy mc-table sources to generate the parity matrix used by the migration pipeline.

Frequently Asked Questions about mc-table-legacy-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a parity matrix for legacy mc-table migration?

A legacy mc-table audit evaluates pre-migration readiness by producing a parity matrix that details columns, slots, props, conditionals, behaviors, and side-effects. This read-only process ensures no parity gaps are introduced when rewriting to a11y-friendly HTML tables.

What is the best way to inventory mc-table components before converting to md-table?

The best way to inventory mc-table components is to perform a read-only audit across all views where mc-table is present. This documents legacy behavior and outputs a parity matrix to guide the migration to md-table a11y components.

Can I use a read-only audit to validate pre-migration baselines for HTML table migration?

Yes, you can use a read-only audit to validate pre-migration baselines for HTML table migration. It generates a complete parity matrix to detect omissions and verify exactly what the legacy mc-table renders before rewriting to a11y-friendly md-table components.

How does an mc-table parity matrix help with migrating to a11y-friendly HTML tables?

An mc-table parity matrix helps with migrating to a11y-friendly HTML tables by documenting the exact legacy behavior, including side-effects and conditionals. This scoping output validates parity and ensures no rendering gaps are introduced during the migration pipeline.

Do I need to check mc-table views separately before starting the migration pipeline?

You need to run the audit across views and components where mc-table is present to check migration readiness. Applying the audit across these sources produces a complete parity matrix that validates the pre-migration baseline before rewriting the HTML table system.