{
  "skill_name": "ui-system-extractor",
  "evals": [
    {
      "id": 1,
      "prompt": "Audit this existing Next.js dashboard and move its reusable Radix and Tailwind UI into our central mm-ui package. Preserve the current layout and styling, and do not create replacement designs.",
      "expected_output": "An evidence-backed inventory and extraction map, followed by dependency-ordered package changes and incremental application migration that preserve current variants, behavior and visual layout.",
      "files": []
    },
    {
      "id": 2,
      "prompt": "Our CMS has local page shells, Gutenberg styles and several customer themes. Turn the reusable parts into installable themes, content adapters and layouts without moving CMS queries into the UI package.",
      "expected_output": "A separation of semantic theme contracts, scoped content adapters and typed slot-based layouts, with CMS data loading left in the application and visual parity verified.",
      "files": []
    },
    {
      "id": 3,
      "prompt": "We have four different Button components and many repeated Tailwind class strings. Consolidate what is genuinely reusable, but keep intentional differences and base behavior on existing components or official primitives.",
      "expected_output": "A usage-aware comparison that distinguishes true variants from separate semantics, selects an existing or official basis, adds a stable package API and migrates call sites incrementally without flattening intentional differences.",
      "files": []
    }
  ]
}