arviahq/tidex

Tidex is a tool for teams who build React component libraries and want a visual workbench to browse, test, and document those components without the usual overhead. Instead of requiring developers to write a separate story file for every button, card, or modal, it scans your existing source code and automatically builds a full explorer with live controls, auto-generated docs, design tokens, and built-in accessibility, interaction, and visual testing. The way it works is straightforward in concept: you run a command that scans your components folder, reads the TypeScript types on each component, and generates everything needed to render an interactive preview. From those types it infers what props each component accepts, what variants exist, and how callbacks should wire up to state. The result is a manager UI with tabs for props, variants, docs, tests, visual regression, interactions, and design foundations, all driven by what your code already declares. You configure it through a single config file rather than managing multiple addon configurations. The primary audience is design system teams and frontend developers maintaining a shared component library, especially in monorepos. For example, a company with an internal UI kit used across multiple products could use this to give designers and product managers a live gallery where they can tweak props and see results, while engineers get automated accessibility checks, screenshot-based visual regression tests, and interaction tests that run in CI. It positions itself as a lighter-weight alternative to Storybook by eliminating the need to hand-write and maintain separate story files for every component. A few things stand out about how the project is built. Testing is powered by Playwright under the hood, and the scan output is persisted as JSON artifacts in a hidden folder, which keeps the generated material separate from source code. It also offers a plugin API for adding custom panels or hooking into the generation pipeline, and it works in monorepo setups. The project is quite new (two stars at time of writing), so it is early-stage and likely still evolving rapidly.