One system from canvas to code.
Design and implementation share one semantic language. Explore variables, component variants, and handoff patterns that map directly to Lumen code.
brandPrimary interaction
surfaceRaised content
successPositive state
- Plugin stage
- Beta
- Mapped components
- 6
- Plugin target
- Astro v4
Lumen for Figma
Development betaSelect a design built with Lumen, inspect its components, and take an Astro starter into your project. The AI handoff gives your coding agent the selected structure, component properties, semantic color references, and items that need review.
The beta recognizes Button, Input, Field, Card, Tabs, and Dialog. It runs locally and makes no AI calls. Your coding agent handles application integration and validation. Generated code, responsive layouts, custom layers, and action behavior still need review.
Exports target @santi020k/lumen-astro v4. Compare the exact version in the handoff with your installed package before integrating the starter. Load the Astro stylesheet and UIPrimitives once at the application boundary.
pnpm install --frozen-lockfile
pnpm exec turbo run build --filter=@santi020k/lumen-figma-pluginIn Figma desktop, choose Plugins → Development → Import plugin from manifest and select apps/figma-plugin/dist/manifest.json. Run these build commands from the Lumen repository root. The plugin is not yet published to Figma Community; the separate Community link on this page opens the design library.
Select one frame or component instance, choose Inspect selection, and review the findings. Copy or save the Astro starter or AI handoff for your project. Exports include the selected design's visible text and component data, so review them before sharing with your coding agent.
Community publication follows the Lumen v4 package and documentation release. An install link will appear here after Figma approval and verified public installation.
Beta setup and limitationsInside the file
Built for useful handoff
The library is intentionally compact: foundations establish the contract, components demonstrate it, and the codebase remains the source of truth for behavior.
Variables
Semantic colors, radius, and effects connect component appearance to shared design decisions.
Library pages
Cover, Foundations, and Components keep the design file easy to scan during handoff.
Component variants
Core variants mirror code props where possible, so review language remains consistent.
Code workflow
Use Code Connect mappings and the beta plugin to bring Lumen components into an Astro handoff.
Recommended flow
Design with the contract
A short loop keeps visual decisions traceable from the first frame through production.
- 01
Start with semantics
Choose canvas, surface, ink, brand, and state tokens before reaching for raw color values.
- 02
Compose with variants
Use library components and their variants to keep behavior and naming close to production.
- 03
Hand off by contract
Reference component names, props, and semantic tokens—the same vocabulary engineers use in code.
Lumen UI Library
Add the published library to your Figma workflow for token references, component variants, and design-to-code review.
File key: luQW2pTQ3jGGxSFPAAsfa9View in Community