Codebase intelligence for AI and humans: code health scores, auto-generated docs, git analytics, dead code detection, and architectural decisions via MCP.
@repowise-dev/ui
Shared visualization components for the Repowise dashboard
(packages/web) and any downstream consumer that wants to render the
same engine artifacts.
Layout
src/
blast-radius/ PR impact analysis shells
c4/ C4 architecture views (+ mobile/ layout primitives)
chat/ chat-interface, artifact-panel, chat-markdown, …
commits/ commit explorer table + detail
costs/ LLM cost breakdowns
coverage/ coverage-donut, freshness-table
dashboard/ health-score-ring, attention-panel, overview tiles, …
dead-code/ summary-bar, findings shells
decisions/ decisions-table, evidence drawer, verification badge
docs/ docs-tree, doc-nav, reader-persona
files/ file entity page (doc/health/history/coverage/graph tabs)
git/ hotspot-table, ownership-table/treemap, churn viz, …
graph/ graph-flow (Sigma), toolbar, legend, panels (+ sigma/)
graph-primitives/
health/ file-table, markers, score tokens
hooks/ use-debounce, …
jobs/ generation-progress, job-log
modules/ module health detail
onboarding/ first-run surfaces
owners/ owner directory + profile
security/ findings table
settings/ general-form
shared/ primitives: responsive-table, adaptive-panel, toast,
error-boundary, empty-state, api-error, metric-card,
entity links/hover cards, context-drawer, orb-loader
symbols/ symbol-table, symbol-drawer, symbol-page, graph/git panels
ui/ Radix-CVA primitives
wiki/ wiki-markdown, code-block, ToC, git-history, backlinks
workspace/ multi-repo tables + summary
styles/
globals.css canonical design tokens (Tailwind v4 @theme)
Consuming
Components are exposed via subpath exports — import the slice you need rather than the barrel:
import { HotspotTable } from "@repowise-dev/ui/git";
import { GraphFlow } from "@repowise-dev/ui/graph";
import { ResponsiveTable, AdaptivePanel, Toaster, toast } from "@repowise-dev/ui/shared";
Consumers must add transpilePackages: ["@repowise-dev/ui", "@repowise-dev/types"]
to their next.config.ts (Tailwind v4 + TS source ship as-is, no
pre-build step).
To inherit the canonical design tokens, import the stylesheet once at the root of the app:
@import "@repowise-dev/ui/styles.css";
Shared primitives
ResponsiveTable— the table primitive every list surface should build on. Columns declare apriority(1 always visible, 2 hidden belowmd, 3 hidden belowlg); the wrapper always falls back tooverflow-x-auto, andstackedcollapses the table into cards on phones.AdaptivePanel— one overlay surface: right-side panel on desktop, swipe-dismissable bottom sheet on mobile.ContextDrawerand the chatArtifactPanelare built on it.Toaster/toast— token-themed sonner toaster (uses--z-toast). Mount theToasteronce at the app shell; the host passes the resolved theme.ErrorBoundary— recoverable render-error boundary; default fallback isApiErrorwith a reset retry.EmptyState— the only sanctioned empty-state rendering. No raw<p>placeholders.- Score colors come from
health/tokens.ts, on the one band vocabulary in@repowise-dev/types/health(HealthBand— Excellent≥8.5/ Good≥7.0/ Fair≥5.5/ Needs work≥4.0/ At risk below). Excellent and Good share the green; the word carries the difference. UsehealthBandSoftBadgeClass/healthBandTextColorwhen you already have a band, andscoreBadgeClass/scoreTextColor/healthInkwhen you have a score. All of them resolve to the semantic tokens (--color-error/warning/caution/success).
Peer deps
react, react-dom, next-themes (theme resolution only). Components
stay client-pure or pure-presentational — they do not call
next/navigation or next/link directly. Where routing is needed,
accept it via props (renderLink render props, LinkComponent,
buildHref) or context so consumers can wire their own router. New
components must not read window.location; initial state arrives via
props.