---
id: insurance-samsung-fire-marine-design-en
service: Samsung Fire & Marine
website: https://www.samsungfire.com
category: insurance
document: DESIGN.MD
source_prompt: insurance-samsung-fire-marine-representative-en
language: en
generated: 2026-07-18
---

# Samsung Fire & Marine DESIGN.MD

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

## Purpose

- Samsung Fire & Marine: https://www.samsungfire.com
- Insurance: understanding coverage and managing claims
- policies, coverage, and claims
- exclusions, sensitive data, and claim status
- insurance

## Design brief

Create an original product that supports understanding coverage and managing claims. Make policies, coverage, and claims easy to scan, compare, and act on. Treat exclusions, sensitive data, and claim status as a primary design constraint. Starting direction: comparison and selection flow · calm and trustworthy · medium information density · usage or conditions -> plan comparison -> limits and price -> subscribe or contact · #1428A0 · Samsung Fire & Marine.

## 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: comparison and selection flow
- Tone and manner: calm and trustworthy
- Information density: medium
- Color strategy: restrained brand accents on neutral surfaces (#1428A0)
- Navigation model: lightweight top navigation
- Structural sequence: usage or conditions -> plan comparison -> limits and price -> subscribe or contact
- Reusable patterns: coverage card, comparison card, price policy, claim timeline, contact 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 policies, coverage, and claims
- 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 exclusions, sensitive data, and claim status

## Design tokens

```css
:root {
  --color-primary: #1428A0;
  --color-ink: #17201D;
  --color-canvas: #F6F8F7;
  --color-surface: #FFFFFF;
  --color-tint: #1428A022;
  --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 Insurance interface for [Product name]. Its goal is understanding coverage and managing claims; its core objects are policies, coverage, and claims; its critical risk is exclusions, sensitive data, and claim 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 Samsung Fire & Marine's logo, proprietary copy, images, or exact layout.
```

## Completion checklist

- [ ] The critical path for understanding coverage and managing claims is obvious without explanation
- [ ] policies, coverage, and claims have clear hierarchy, status, and actions
- [ ] exclusions, sensitive data, and claim 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 Samsung Fire & Marine is reproduced