# CTT — Design System
> Portugal's national postal and financial services provider.
- **Canonical:** https://uiuxskills.com/library/ctt
- **Source:** https://www.ctt.pt/particulares/index
- **Category:** Fintech & Crypto
- **Compatible tools:** claude, cursor, lovable, figma-make
- **Coverage:** 80%
- **License:** MIT
- **Last updated:** 2026-10-22T23:31:09.580Z

---

---
version: alpha
name: CTT
tagline: Uma nova opção de poupança com taxa fixa crescente a 10 anos e capital garantido
description: Portugal's national postal and financial services provider.
tone: Professional, reliable, and highly energetic.
color-scheme: light
colors:
  primary: "#DF0024"
  secondary: "#0ABEB4"
  background: "#FFFFFF"
  surface: "#FFFFFF"
  surface-dim: "#F4F4F4"
  on-primary: "#FFFFFF"
  on-surface: "#3B3B3B"
  on-surface-variant: "#707070"
  outline: "#D8D8D8"
  error: "#D50000"
  success: "#71C387"
typography:
  display-lg:
    fontFamily: Acto Cttmedium, Helvetica Neue, Helvetica, Arial, sans-serif
    fontSize: 48px
    fontWeight: 700
    lineHeight: "1.2"
  display-md:
    fontFamily: Acto Cttmedium, Helvetica Neue, Helvetica, Arial, sans-serif
    fontSize: 38px
    fontWeight: 700
    lineHeight: "1.25"
  headline-lg:
    fontFamily: Acto Cttmedium, Helvetica Neue, Helvetica, Arial, sans-serif
    fontSize: 32px
    fontWeight: 700
    lineHeight: "1.3"
  headline-md:
    fontFamily: Acto Cttmedium, Helvetica Neue, Helvetica, Arial, sans-serif
    fontSize: 24px
    fontWeight: 700
    lineHeight: "1.35"
  headline-sm:
    fontFamily: Acto Cttmedium, Helvetica Neue, Helvetica, Arial, sans-serif
    fontSize: 20px
    fontWeight: 700
    lineHeight: "1.4"
  body-lg:
    fontFamily: Acto Cttbook, Helvetica Neue, Helvetica, Arial, sans-serif
    fontSize: 18px
    fontWeight: 400
    lineHeight: "1.5"
  body-md:
    fontFamily: Acto Cttbook, Helvetica Neue, Helvetica, Arial, sans-serif
    fontSize: 16px
    fontWeight: 400
    lineHeight: "1.5"
  body-sm:
    fontFamily: Acto Cttbook, Helvetica Neue, Helvetica, Arial, sans-serif
    fontSize: 14px
    fontWeight: 400
    lineHeight: "1.4"
  label-md:
    fontFamily: Acto Cttbook, Helvetica Neue, Helvetica, Arial, sans-serif
    fontSize: 14px
    fontWeight: 500
    lineHeight: "1"
  label-sm:
    fontFamily: Acto Cttbook, Helvetica Neue, Helvetica, Arial, sans-serif
    fontSize: 12px
    fontWeight: 600
    lineHeight: "1"
rounded:
  none: 0px
  sm: 4px
  md: 8px
  lg: 16px
  full: 9999px
spacing:
  xs: 4px
  sm: 8px
  md: 16px
  lg: 24px
  xl: 32px
  2xl: 48px
components:
  button-primary:
    backgroundColor: "{colors.primary}"
    textColor: "{colors.on-primary}"
    typography: "{typography.label-md}"
    rounded: "{rounded.none}"
    padding: 12px 24px
    borderColor: "{colors.primary}"
  button-primary-hover:
    backgroundColor: "#B8001D"
    textColor: "{colors.on-primary}"
    typography: "{typography.label-md}"
    rounded: "{rounded.none}"
    padding: 12px 24px
    borderColor: "#B8001D"
  button-secondary:
    backgroundColor: transparent
    textColor: "{colors.on-primary}"
    typography: "{typography.label-md}"
    rounded: "{rounded.none}"
    padding: 12px 24px
    borderColor: "{colors.background}"
  input-field:
    backgroundColor: "{colors.surface}"
    textColor: "{colors.on-surface}"
    typography: "{typography.body-md}"
    rounded: "{rounded.none}"
    padding: 12px 16px
    borderColor: "{colors.outline}"
  input-field-focus:
    backgroundColor: "{colors.surface}"
    textColor: "{colors.on-surface}"
    typography: "{typography.body-md}"
    rounded: "{rounded.none}"
    padding: 12px 16px
    borderColor: "{colors.primary}"
  card:
    backgroundColor: "{colors.surface-dim}"
    rounded: "{rounded.md}"
    padding: 24px
    borderColor: "{colors.outline}"
  card-quick-action:
    backgroundColor: "{colors.surface}"
    rounded: "{rounded.none}"
    padding: 24px
  link:
    textColor: "{colors.secondary}"
    typography: "{typography.body-md}"
  link-hover:
    textColor: "{colors.primary}"
    typography: "{typography.body-md}"
  badge:
    backgroundColor: "{colors.primary}"
    textColor: "{colors.on-primary}"
    typography: "{typography.label-sm}"
    rounded: "{rounded.full}"
    padding: 4px 8px
  badge-error:
    backgroundColor: "{colors.error}"
    textColor: "{colors.on-primary}"
    typography: "{typography.label-sm}"
    rounded: "{rounded.full}"
    padding: 4px 8px
  badge-success:
    backgroundColor: "{colors.success}"
    textColor: "{colors.on-primary}"
    typography: "{typography.label-sm}"
    rounded: "{rounded.full}"
    padding: 4px 8px
  divider:
    backgroundColor: "{colors.outline}"
    height: 1px
  fab-chat:
    backgroundColor: "{colors.primary}"
    textColor: "{colors.on-primary}"
    rounded: "{rounded.full}"
    size: 56px
  swatch-background:
    backgroundColor: "{colors.background}"
    rounded: "{rounded.sm}"
    size: 32px
  swatch-on-surface-variant:
    backgroundColor: "{colors.on-surface-variant}"
    rounded: "{rounded.sm}"
    size: 32px
motion:
  duration-short: 200ms
  duration-medium: 500ms
  easing-standard: cubic-bezier(0.25, 0.1, 0.25, 1)
elevation:
  sm: 0 1px 2px rgba(0,0,0,0.1)
  md: 0 4px 8px rgba(0,0,0,0.1)
  lg: 0 10px 20px rgba(0,0,0,0.2)
---

## Overview

CTT's visual identity is anchored by its iconic, high-energy red brand color, conveying urgency, reliability, and national presence. The design balances traditional utility with digital service patterns, utilizing sharp-edged components, high-contrast photography, and clean, structured layouts. It projects a professional, reliable, and energetic atmosphere suitable for a trusted national postal and financial services provider.

## Colors

The color strategy relies on a high-contrast, energetic palette dominated by the signature brand red, balanced with clean white surfaces and a vibrant teal accent. This combination ensures high visibility, clear hierarchy, and strict accessibility standards across all digital interfaces.

* Primary `{colors.primary}` (#DF0024): The signature CTT Red, used for primary branding, key call-to-actions, and high-priority UI elements.
* Secondary `{colors.secondary}` (#0ABEB4): A vibrant teal accent color used for links, secondary interactive elements, and highlights.
* Background `{colors.background}` (#FFFFFF): The primary background color for the website, ensuring maximum readability and clean contrast.
* Surface `{colors.surface}` (#FFFFFF): Used for card backgrounds, quick-action containers, and form fields.
* Surface Dim (inferred) `{colors.surface-dim}` (#F4F4F4): A light gray background variant used to differentiate content sections and secondary cards.
* On Primary `{colors.on-primary}` (#FFFFFF): Text and icon color used on top of the primary red background to ensure high contrast.
* On Surface `{colors.on-surface}` (#3B3B3B): The primary dark gray color for body text and main headings on light surfaces.
* On Surface Variant (inferred) `{colors.on-surface-variant}` (#707070): A medium gray used for secondary text, captions, and less prominent labels.
* Outline `{colors.outline}` (#D8D8D8): Used for borders on input fields, dividers, and subtle container outlines.
* Error (inferred) `{colors.error}` (#D50000): A high-visibility red used for error states, validation alerts, and critical warnings.
* Success `{colors.success}` (#71C387): A soft green used for successful validation, completed states, and positive indicators.

## Typography

The typography system uses the Acto Ctt typeface family to establish a clean, highly structured editorial feel. Acto Cttmedium provides weight and authority for display and headline elements, while Acto Cttbook ensures optimal legibility for body copy and interactive labels.

* Display Large `{typography.display-lg}`: Acto Cttmedium. Used for main hero headings to establish strong brand presence.
* Display Medium `{typography.display-md}`: Acto Cttmedium. Used for secondary hero headings and major section titles.
* Headline Large (inferred) `{typography.headline-lg}`: Acto Cttmedium. Used for standard section headers and prominent card titles.
* Headline Medium (inferred) `{typography.headline-md}`: Acto Cttmedium. Used for medium-sized headings and content block titles.
* Headline Small (inferred) `{typography.headline-sm}`: Acto Cttmedium. Used for small headings, sub-sections, and card titles.
* Body Large `{typography.body-lg}`: Acto Cttbook. The standard body text size for primary reading and descriptive paragraphs.
* Body Medium (inferred) `{typography.body-md}`: Acto Cttbook. Used for secondary body text, form labels, and general UI descriptions.
* Body Small (inferred) `{typography.body-sm}`: Acto Cttbook. Used for small helper text, footer links, and metadata.
* Label Medium (inferred) `{typography.label-md}`: Acto Cttbook. Used for interactive labels, button text, and form inputs.
* Label Small (inferred) `{typography.label-sm}`: Acto Cttbook. Used for uppercase overlines, badges, and micro-copy.

## Layout

The layout utilizes a structured grid with a prominent hero section and overlapping quick-action containers to bridge the hero and content areas. Spacing is generous but highly structured, using a scale built around `{spacing.md}` and `{spacing.lg}` to ensure clear visual hierarchy. The observed page section order is nav, hero, quick-actions, features, and footer. The hero composition pattern features a full-width high-energy red background with a large photographic focal point on the right, bold white typography on the left, and a primary CTA button. On mobile screens, the layout transitions to a mobile-first stacked structure where the quick-actions container stacks vertically and the hero image scales down or collapses below 768px.

## Elevation & Depth

Depth is primarily conveyed through flat color contrast and subtle, single-layer shadows across three levels.

* `elevation.sm`: Used for subtle card lifts and low-level interactive elements.
* `elevation.md`: Applied to standard dropdowns, popovers, and the overlapping quick-action card containers to separate them from the background.
* `elevation.lg`: Reserved for modal overlays, drawer menus, and high-priority floating elements.

## Shapes

CTT employs a strict sharp-corner philosophy for its primary interactive elements. Buttons, input fields, and quick-action cards utilize `{rounded.none}` to project a highly structured, geometric, and authoritative brand image.

Rounded shapes are reserved exclusively for specific UI indicators. Small elements like `{rounded.sm}` are used for color swatches, `{rounded.md}` is applied to standard informational cards, and `{rounded.full}` is reserved for floating action buttons, badges, and circular UI indicators to create visual distinction from the primary sharp-edged layout.

## Components

> **Note:** This spec was generated from a website scrape and contains visual approximations.
> For production use, add a deep reference to each component pointing to its authoritative
> source (Storybook story, metadata file, or component spec):
> `→ Deep reference: src/components/Button/metadata.ts`

### button-primary
The primary action button features a solid `{colors.primary}` background with `{colors.on-primary}` text using `{typography.label-md}` and a sharp `{rounded.none}` corner treatment. It transitions to `button-primary-hover` with a darker red background on hover. Use this component for the single primary call-to-action on a page or section.

### button-secondary
This button features a transparent background with `{colors.on-primary}` text and a border matching `{colors.background}`. It uses `{typography.label-md}` and `{rounded.none}`. Use this component for secondary actions on dark or primary-colored backgrounds, such as inside the hero section.

### input-field
The standard input field consists of a `{colors.surface}` background, `{colors.on-surface}` text, and a `{colors.outline}` border with `{rounded.none}` corners. On focus, it transitions to `input-field-focus`, changing its border color to `{colors.primary}`. Use this for all user text inputs and form fields.

### card
The standard card container uses a `{colors.surface-dim}` background with `{rounded.md}` corners and a `{colors.outline}` border. It is designed to group related informational content. Use this component to structure secondary content blocks on a page.

### card-quick-action
This specialized container features a `{colors.surface}` background with sharp `{rounded.none}` corners and generous padding. It is designed to overlap background transitions to provide immediate access to key utilities. Use this component exclusively for high-priority quick-action panels.

### link
An inline interactive element using `{colors.secondary}` text and `{typography.body-md}`. On hover, it transitions to `link-hover`, changing the text color to `{colors.primary}`. Use this for inline navigation and secondary text-based actions.

### badge
A small status indicator featuring a solid background, `{colors.on-primary}` text, and `{rounded.full}` corners. It comes in standard `{colors.primary}`, `{colors.error}` (badge-error), and `{colors.success}` (badge-success) variants. Use this to highlight counts, status updates, or validation states.

### divider
A thin horizontal rule with a height of 1px and a `{colors.outline}` background. Use this component to create subtle visual separation between content sections or list items.

### fab-chat
A persistent floating action button featuring a `{colors.primary}` background, `{colors.on-primary}` icon/text, and a `{rounded.full}` shape. Use this component exclusively in the bottom corner of the viewport for persistent chat or support utilities.

## Do's and Don'ts

| Do | Don't |
| --- | --- |
| Use `{colors.primary}` for primary call-to-action buttons like `{components.button-primary}`. | Never apply rounded corners to `{components.button-primary}` as it violates the brand's sharp-edged design language. |
| Apply `{colors.surface}` for high-contrast content containers overlapping dark backgrounds. | Do not use `{colors.primary}` for body text; reserve it for headings and key interactive elements. |
| Ensure `{components.input-field}` maintains a sharp `{rounded.none}` border radius to align with the brand's geometric style. | Never omit the `{colors.outline}` border on `{components.input-field}` to maintain form accessibility. |
| Use `{colors.secondary}` to highlight interactive links and secondary actions. | Avoid using `{colors.secondary}` for critical error states; use `{colors.error}` instead. |
| Maintain clear spacing using `{spacing.lg}` for container padding to ensure readability. | Do not mix multiple border-radius styles within the same card container. |
| Use `{components.fab-chat}` with `{rounded.full}` for persistent floating utility actions. | Avoid placing low-contrast text on `{colors.primary}` backgrounds; always use `{colors.on-primary}`. |
| Use `{colors.surface-dim}` for secondary content blocks to separate them from the main `{colors.background}`. | Do not use `{typography.display-lg}` for standard body text; reserve it strictly for main hero headings. |
| Apply `{colors.success}` for positive validation states and successful transaction badges. | Do not use `{colors.outline}` for primary text elements as it lacks sufficient contrast against `{colors.surface}`. |

## Content Style

* CTA Style: Call-to-action labels must use direct, action-oriented verbs in Portuguese (e.g., "Ver produto", "Comprar já", "Pesquisar"). They should be concise, imperative, and set in `{typography.label-md}`.
* Heading Tone: Headlines must be informative, trust-building, and benefit-driven. They should clearly state the value proposition or service utility, utilizing `{typography.display-lg}` or `{typography.display-md}` to establish immediate authority.
* Copy Density: Content must be highly scannable and structured into concise blocks of text. Use bulleted lists and clear headings to break up information, ensuring high readability and accessibility for users navigating complex financial or postal services.

## Imagery & Icons

The visual style uses a mixed imagery treatment featuring high-contrast photography with a dominant red color cast to align with `{colors.primary}`. Icons must be simple, red-outlined vector shapes with a clean, minimalist aesthetic. Photographic assets should depict real-world utility and human interaction, while illustrations and icons must maintain clean geometric lines that complement the sharp `{rounded.none}` design language of the UI components.

---

## Companion prompt

## Role
You are an AI assistant generating UI components and layouts for CTT, a bold, accessible, enterprise brand with a professional and high-energy tone. Content, copy, and information architecture remain owned by the product team.

## How to use design.md
1. Reference every visual value by its token name — `{colors.primary}`, `{typography.body-lg}`, `{spacing.md}` — never hardcode hex values, font sizes, or pixel measurements.
2. Render only the components listed under `components:` (`button-primary`, `input-field`, `card`, `badge`, etc.). Do not invent variants the spec does not define.
3. Apply the sharp-corner philosophy from Shapes: use `{rounded.none}` on buttons and inputs, `{rounded.full}` on `{components.fab-chat}` and badges only. Do not mix radius styles inside a single container.
4. Follow the Layout narrative — structured grid, prominent hero, overlapping quick-action containers — when composing page sections. Use `{spacing.lg}` as the baseline container padding.
5. Treat the Do's and Don'ts table as authoritative. If a user request conflicts with it (e.g., adding rounded corners to `{components.button-primary}`), surface the conflict explicitly before proceeding.

## Output contract

**Must:**
- Use token names for all colors, typography, spacing, and radii.
- Cover hover, focus, and disabled states for every interactive component the spec defines (e.g., `button-primary-hover`, `input-field-focus`, `link-hover`).
- Apply `{colors.on-primary}` for text and icons placed on `{colors.primary}` backgrounds.
- Use `{colors.error}` for error states and `{colors.success}` for success states; never substitute `{colors.secondary}` in these roles.
- Write CTAs using direct, action-oriented Portuguese verbs per the Voice and Content section.

**Must NOT:**
- Invent colors, font families, or radii absent from the spec.
- Apply generic unnamed utility defaults when a brand token exists.
- Add emoji, filler copy, or unsolicited marketing text.
- Use `{colors.primary}` for body text.
- Omit the `{colors.outline}` border on `{components.input-field}`.
- Rewrite page copy, button labels, headings, or alter navigation structure as a side effect of applying tokens.

## When in doubt
- If a value is not defined in the spec, ask the user before inventing one.
- Prefer composing existing components over introducing new tokens.
- For ambiguous backgrounds, default to `{colors.surface}`; for ambiguous text, default to `{colors.on-surface}`.
- For unspecified breakpoints, use mobile-first layout with one breakpoint at 768px.
- If the product has an authoritative token source (Figma tokens, a theme file), those values take precedence over any inferred values in the spec.
