Milestones
List view
shadcn/ui support, defineCatalog override definitions, and breaking-change detection. Exit criteria: shadcn/ui components, including Radix-composed ones, render in the catalog without hand-written Stories; a Next.js project's client components render in the catalog without a Vite host; breaking changes to props are caught in CI before merge; agents can add and verify variant overrides through MCP without direct file access; and a catalog of a shadcn/ui-sized component set — several dozen components and several hundred previews — stays usable to open and browse. See the Roadmap in docs/requirements.md.
No due date•0/5 issues closedVite + React + Tailwind, the adapter foundation, and the agent-facing MCP server. Exit criteria: React + cva analysis runs on top of the adapter interface, and the Tailwind adapter is added without breaking the manifest contract; agents can query the MCP server and receive valid component metadata; catalog.json is versioned so consumers can detect incompatibility; configuration is expressible through thmh() options without a second config file; what thmh reports is trustworthy, in that analysis does not silently drop or misreport what it found and a failure reaches whoever asked for it rather than appearing as an empty catalog or a clean build; and the official website (landing and documentation) is published. See the Roadmap in docs/requirements.md.
No due date•12/20 issues closed