---
id: legal-luminance-design-en
service: Luminance
website: https://www.luminance.com
category: legal
document: DESIGN.MD
source_prompt: legal-luminance-representative-en
language: en
generated: 2026-07-18
---

# Luminance DESIGN.MD

> Use this DESIGN.MD as the persistent design standard before building a Legal services site or app. It can be given directly to designers, frontend engineers, AI builders, and coding agents. Luminance is an information-architecture reference only.

## Purpose

- Luminance: https://www.luminance.com
- Legal services: legal information and matter management
- matters, documents, and deadlines
- accuracy, versions, and signature status
- legal

## Design brief

Create an original product that supports legal information and matter management. Make matters, documents, and deadlines easy to scan, compare, and act on. Treat accuracy, versions, and signature status as a primary design constraint. Starting direction: operational console · conservative and security-first · high information density · lookup or summary -> status timeline -> exception guidance -> support or review · #6C4CF1 · Luminance.

## Public interface design analysis

- Reference basis: These are recurring visual and structural patterns from public landing screens and representative task flows. Verify the current live capture because services change over time.
- Interface archetype: operational console
- Tone and manner: conservative and security-first
- Information density: high
- Color strategy: ink-led system with limited accent color (#6C4CF1)
- Navigation model: sidebar-led context switching
- Structural sequence: lookup or summary -> status timeline -> exception guidance -> support or review
- Reusable patterns: matter summary, document table, deadline timeline, signature state, review action
- Independent application rule: Use the order and decision principles only. Do not reproduce logos, copy, imagery, icons, or proprietary screen composition.

## Screen architecture

- Global navigation with clear current location and account state
- Overview that exposes the next important action for matters, documents, and deadlines
- Search, filter, sort, or segmented views only where they reduce decision cost
- Detail view that keeps context, status, evidence, and the primary action together
- Persistent help, recovery, privacy, and safety access for accuracy, versions, and signature status

## Design tokens

```css
:root {
  --color-primary: #6C4CF1;
  --color-ink: #17201D;
  --color-canvas: #F6F8F7;
  --color-surface: #FFFFFF;
  --color-tint: #6C4CF122;
  --color-danger: #DC2626;
  --radius-control: 6px;
  --radius-card: 8px;
  --space-1: 4px; --space-2: 8px; --space-3: 12px;
  --space-4: 16px; --space-6: 24px; --space-8: 32px;
  --content-reading: 720px;
  --content-wide: 1280px;
}
```

## Component specifications

- Navigation: active, hover, focus, disabled, and collapsed states
- Cards and rows: stable dimensions, realistic content, metadata hierarchy, and complete click targets
- Forms: labels, descriptions, validation, error summary, progress, and recovery
- Actions: one clear primary action per region; icon buttons require accessible names and tooltips
- Feedback: inline status, toast, banner, skeleton, progress, confirmation, and destructive-action dialog

## State design

For every data-driven region, define loading, empty, partial-data, stale, error, offline, permission-denied, disabled, saving, and success states. Keep layout dimensions stable so state changes do not shift surrounding content.

## Responsive rules

- 360px: one primary column, no horizontal page scroll, 44px touch targets
- 768px: preserve context with two panes only when each pane remains readable
- 1280px and above: constrain reading width and use extra space for comparison or persistent context
- Never scale type with viewport width; wrap long labels and localize for text expansion

## Accessibility requirements

- Semantic landmarks and heading order
- Complete keyboard operation with visible focus
- WCAG AA contrast in all states
- Programmatic labels, descriptions, errors, and live regions
- 200% zoom, reduced motion, forced colors, and screen-reader verification

## Design instruction for AI builders

```text
Design an original Legal services interface for [Product name]. Its goal is legal information and matter management; its core objects are matters, documents, and deadlines; its critical risk is accuracy, versions, and signature status. Use the token system and screen rules in this document. Specify realistic content, component contracts, all data states, responsive behavior, accessibility, and acceptance criteria. Do not copy Luminance's logo, proprietary copy, images, or exact layout.
```

## Completion checklist

- [ ] The critical path for legal information and matter management is obvious without explanation
- [ ] matters, documents, and deadlines have clear hierarchy, status, and actions
- [ ] accuracy, versions, and signature status has prevention and recovery
- [ ] Mobile, tablet, desktop, keyboard, screen reader, zoom, and reduced motion are verified
- [ ] Loading, empty, error, offline, partial, permission, and success states are complete
- [ ] No protected brand asset or pixel-level layout from Luminance is reproduced