EraAIInternal
Developers · Common UI

Build one coherent interface without flattening the work.

A practical implementation layer distilled from the Brandbook. Use these rules while building product and internal surfaces; consult the Brandbook for the complete identity system and visual rationale.

F1

Typography

Inter with system fallbacks. Operational body text stays at 13–14px; metadata at 11–12px; page titles at 19px.

F2

Color

Neutral surfaces lead. Teal communicates focus, governance, success, and live state—not decoration.

F3

Shape

Use compact 7px controls, 12px rows, 16px cards, and larger radii only for expressive reference or entry surfaces.

F4

Depth

Prefer thin borders and nearly flat surfaces. Floating menus may use restrained shadow; dark surfaces are opaque.

SHARED COMPONENT CONTRACTS

Header rails

  • Use one persistent 52px rail per workspace.
  • Center titles and every control on the same vertical axis.
  • Keep restore controls in flow; never overlay content.
  • Use a quiet hairline divider and preserve the canvas through the rail.

Buttons and menus

  • Default to neutral secondary and ghost actions.
  • Use short verb labels and accessible names for icon-only controls.
  • Use solid, content-sized dropdown bodies with keyboard dismissal.
  • Keep detail dialogs, inspectors, and drawers fully opaque in both themes.
  • Disabled destinations are visibly planned and have no link target.

Cards and data

  • A card answers one coherent question.
  • Use hierarchy and alignment instead of miniature text.
  • Preserve specialized graphs, workflows, traces, and previews.
  • Pair status color with readable text and explicit scope.

Responsive behavior

  • Adapt or stack before controls become too small.
  • Keep one clear scroll owner per workspace.
  • Prevent document-level horizontal overflow.
  • Honor reduced motion and preserve keyboard focus.
Decision order
  1. 1Start with the user’s task and information hierarchy.
  2. 2Reuse the common shell and established components.
  3. 3Preserve domain-specific structure.
  4. 4Add a reusable rule only when a real gap remains.
IMPLEMENTATION CHECKLIST

Before calling UI done

  • 01Reuse existing components, product marks, and theme tokens before adding a variant.
  • 02Check light and dark themes at desktop and narrow widths.
  • 03Verify hover, focus, active, disabled, loading, empty, error, and success states as applicable.
  • 04Keep event handlers inside Client Components and application images in next/image.
  • 05Update the Brandbook for reusable visual decisions and Requirements for shared behavior.
  • 06Run the narrowest relevant check, then complete production delivery verification for frontend work.