On this page

MIOSA Foundation is the internal component library for the platform frontend. It is the place to inspect components before deciding what to keep, remove, rename, or rebuild.

The live browser is maintained in the Foundation package:

cd miosa-platform/miosa-frontend/src/lib/foundations-components
npm run dev -- --host 127.0.0.1 --port 5174

Open:

http://127.0.0.1:5174/component-library

What Lives Where

Live component browser

Browse every section, pattern, and demo in the Foundation package.

Source sections

src/lib/foundations-components/src/routes/component-library/sections

Design reference

src/lib/foundations-components/DESIGN.md

Cleanup review

src/lib/foundations-components/COMPONENT_REVIEW.md

Compact Reference

MIOSA UI should feel like an operator console for AI compute: precise, dark, dense, and fast to scan. Keep the system mostly neutral. Use a limited blue/cyan signal color only for active compute, selected state, focus, and live status. Avoid decorative gradients, oversized marketing sections, duplicate button variants, and one-off component styling.

TokenValueRole
Canvas#07090dApp background
Panel#10141cPrimary component surface
Raised#151b25Elevated controls and selected rows
Border#263041Hairline structure
Text#f4f7fbPrimary text
Muted#8d98aaSecondary labels
Signal#60a5faActive compute, focus, selected state
Success#34d399Healthy/running status
Warning#fbbf24Attention state
Danger#f87171Destructive or failed state

Core rules:

  • Use one primary button per visual region.
  • Prefer compact toolbars, segmented controls, tabs, tables, and split panes.
  • Use 1px borders for structure; use shadows sparingly.
  • Use status color only where state must be read quickly.
  • Keep cards at 8px radius unless the existing local pattern requires less.
  • Remove duplicate button/component variants unless they encode meaning.

Extended Reference

Component Cleanup Checklist

Use this checklist when deciding what stays in the Foundation library.

DecisionKeep WhenRemove Or Merge When
Button variantIt maps to a real action hierarchyIt only changes color, radius, or vibe
Card/panelIt represents a reusable product surfaceIt is a one-off demo wrapper
Input/composerIt handles real data entry or agent promptsIt duplicates another composer shell
Table/listIt supports scan, sort, compare, or operate workflowsIt is only visual filler
Status badgeIt encodes real stateIt is decorative labeling
Module pageIt maps to a MIOSA product workflowIt is a generic SaaS mockup

See Also

Was this helpful?