Reuse the system in Radarist

What can be reused now

The source already provides shared field classes, creation actions, settings controls, project identity mappings, and specialized workspace components. Reuse those definitions inside the existing application. The public documentation does not publish private application source, authentication code, or a package that can be installed into another company’s product.

A project overview composition

import { AppHeader } from "./components/app-header";
import { PageHero } from "./components/page-hero";
import { ProjectsWorkspace } from "./components/projects-workspace";

// The page owns authorization and real data retrieval.
<AppHeader />
<main>
  <PageHero title="Projects" help={projectHelp} />
  <ProjectsWorkspace cards={authorizedProjectCards} />
</main>

Reuse boundary

Integration checklist

• Choose the appropriate existing component before writing new markup.
• Match the documented props and provide the required context/custom properties.
• Use the real parent data/action boundary for persistence; no capture fixture belongs in production.
• Check both themes, phone/desktop layout, keyboard operation and error feedback.
• Record any new variant or exception with its source reference and applied example.

Available downloads

tokens.json records exact light/dark CSS variable values and source revision. tokens.css is the original public style definition. source-inventory.json maps exported component implementations and source hashes. capture-manifest.json records image provenance. These are useful handoff references; they are not a Figma kit or a portable component package.