Pay Transparency Law Checker (bulk, Apify) vs Melta UI

Pay Transparency Law Checker (bulk, Apify) tools

No tool names declared yet. Check the project README from the listing page.

Melta UI tools 6

• get_tokenGet a design token by dot-path. Returns the token object with its value and class mapping.
• get_componentGet component metadata including variants, sizes, accessibility requirements, HTML sample, per-state specs (stateSpecs: disabled/loading/open/empty etc. — each with delta class strings + aria changes), and anatomy parts (overlay/container/th etc. with element/roles/class). Prefer these structured fields over inferring states from the HTML sample.
• check_ruleCheck class strings against this design system's prohibition rules. Returns violations with reasons and alternatives.
• check_htmlLint a full HTML/JSX source against melta-ui rules — the same checks as CI and the PostToolUse hook (class rules + html-attr rules + composition rules for HTML). Use this AFTER generating UI code to self-verify before presenting it. Response always includes coverage info (manual rules cannot be auto-checked).
• searchSearch across tokens and components by keyword. Matches against names, values, class strings, and descriptions. Returns up to 20 results (truncated flag when more matched).
• get_rulesGet melta-ui prohibition rules from rules.json (107 total). Use this to retrieve manual/contextual rules that check_rule cannot auto-detect. Supports filtering by category, severity, or detector.