Browse catalog

Quality

Brok treats the registry as product code, not snippets. Every installable item must pass build-time validation, docs visibility checks, mirror parity, render tests, and token/a11y guards before it is considered shippable.

346

cataloged components

431

cataloged blocks

documented bundles

Registry Safety

The registry builder validates every manifest before writing JSON endpoints. It rejects unsafe target paths, missing source files, duplicate names, unknown dependencies, dependency cycles, and open items that depend on Pro items.

terminal

cd apps/docs-registry && php artisan registry:build --dry-run

Install Safety

Installed files are restricted to generated UI paths and each incoming file is re-hashed and checked against its SHA-256 hash before it is written — a mismatch aborts the install. The hash is co-shipped with the content, so it guards against transport corruption and accidental drift, not a tampered registry; end-to-end integrity currently relies on HTTPS transport trust (payload signing is a planned hardening). Existing files are preserved unless the user explicitly confirms an overwrite or passes --force.

resources/views/components/ui/**
resources/views/blocks/**
resources/js/ui/**

Design System Guards

Component and block tests enforce semantic tokens, primitive composition, raw color bans, RTL support, stable data-slot hooks, and admin surface pinning for admin blocks. The docs mirror must also match the registry source exactly.

terminal

cd apps/docs-registry && php artisan test tests/Feature/Components

Component API Coverage

Every catalog component must produce an API reference from either curated metadata or the registry manifest and Blade source. The guard renders every component docs page and fails when a component ships without generated targets, stable data-slot selectors, the API section, or the registry contract.

terminal

cd apps/docs-registry && php artisan test tests/Feature/Components/ComponentApiCoverageTest.php

Browser Coverage

Playwright smoke tests run the docs site on desktop and mobile viewports, check key docs pages for console errors, verify mobile overflow behavior, and exercise high-risk interactive primitives such as dialog, dropdown, combobox, and calendar.

terminal

cd apps/docs-registry && npm run test:browser

Note

These checks are not a substitute for reviewing a component in your product context. They are the baseline that keeps the registry installable, visible in docs, theme-compatible, and safe to copy into a Laravel application.