# UseFlo — Design System
> Tasks, Habits and a Focus Timer for Students
- **Canonical:** https://uiuxskills.com/library/useflo
- **Source:** https://useflo.pro/
- **Category:** Productivity & SaaS
- **Compatible tools:** claude, cursor, lovable, figma-make
- **Coverage:** 79%
- **License:** MIT
- **Last updated:** 2026-11-08T03:40:30.824Z

---

---
version: alpha
name: UseFlo
tagline: Do the thing. Feel amazing.
description: Tasks, Habits and a Focus Timer for Students
tone: playful, energetic, encouraging, modern
color-scheme: light
colors:
  primary: "#FF90E8"
  secondary: "#FFC900"
  background: "#F6F4EC"
  surface: "#FFFFFF"
  surface-container: "#F6F4EC"
  on-surface: "#000000"
  on-primary: "#000000"
  outline: "#000000"
  error: "#FF7051"
  success: "#23A094"
typography:
  display-lg:
    fontFamily: DM Sans
    fontSize: 104px
    fontWeight: 700
    lineHeight: "1.1"
    letterSpacing: "-0.02em"
  display-md:
    fontFamily: DM Sans
    fontSize: 72px
    fontWeight: 700
    lineHeight: "1.1"
    letterSpacing: "-0.02em"
  headline-lg:
    fontFamily: DM Sans
    fontSize: 48px
    fontWeight: 700
    lineHeight: "1.2"
    letterSpacing: "-0.01em"
  headline-md:
    fontFamily: DM Sans
    fontSize: 32px
    fontWeight: 700
    lineHeight: "1.2"
    letterSpacing: 0em
  headline-sm:
    fontFamily: DM Sans
    fontSize: 24px
    fontWeight: 600
    lineHeight: "1.3"
    letterSpacing: 0em
  body-md:
    fontFamily: DM Sans
    fontSize: 20px
    fontWeight: 400
    lineHeight: "1.5"
    letterSpacing: 0em
  body-sm:
    fontFamily: DM Sans
    fontSize: 16px
    fontWeight: 400
    lineHeight: "1.5"
    letterSpacing: 0em
  label-md:
    fontFamily: DM Sans
    fontSize: 14px
    fontWeight: 500
    lineHeight: "1.4"
    letterSpacing: 0.02em
  label-sm:
    fontFamily: DM Sans
    fontSize: 12px
    fontWeight: 500
    lineHeight: "1.4"
    letterSpacing: 0.05em
rounded:
  sm: 4px
  md: 6px
  lg: 12px
  xl: 24px
  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.md}"
    padding: 12px 24px
    height: auto
    width: auto
    borderColor: "{colors.outline}"
    outlineOffset: 0px
  button-primary-hover:
    backgroundColor: "{colors.secondary}"
    textColor: "{colors.on-primary}"
    typography: "{typography.label-md}"
    rounded: "{rounded.md}"
    padding: 12px 24px
    height: auto
    width: auto
    borderColor: "{colors.outline}"
    outlineOffset: 0px
  button-secondary:
    backgroundColor: "{colors.surface}"
    textColor: "{colors.on-surface}"
    typography: "{typography.label-md}"
    rounded: "{rounded.md}"
    padding: 12px 24px
    height: auto
    width: auto
    borderColor: "{colors.outline}"
    outlineOffset: 0px
  card:
    backgroundColor: "{colors.surface}"
    textColor: "{colors.on-surface}"
    rounded: "{rounded.lg}"
    padding: 24px
    height: auto
    width: 100%
    borderColor: "{colors.outline}"
    outlineOffset: 0px
  card-elevated:
    backgroundColor: "{colors.surface}"
    textColor: "{colors.on-surface}"
    rounded: "{rounded.lg}"
    padding: 24px
    height: auto
    width: 100%
    borderColor: "{colors.outline}"
    outlineOffset: 0px
  card-flat:
    backgroundColor: "{colors.surface-container}"
    textColor: "{colors.on-surface}"
    rounded: "{rounded.md}"
    padding: 16px
    height: auto
    width: 100%
    borderColor: "{colors.outline}"
    outlineOffset: 0px
  input-field:
    backgroundColor: "{colors.surface}"
    textColor: "{colors.on-surface}"
    typography: "{typography.body-sm}"
    rounded: "{rounded.md}"
    padding: 12px 16px
    height: 48px
    width: 100%
    borderColor: "{colors.outline}"
    outlineOffset: 0px
  input-field-focus:
    backgroundColor: "{colors.surface}"
    textColor: "{colors.on-surface}"
    typography: "{typography.body-sm}"
    rounded: "{rounded.md}"
    padding: 12px 16px
    height: 48px
    width: 100%
    borderColor: "{colors.primary}"
    outlineOffset: 2px
  link:
    textColor: "{colors.on-surface}"
    typography: "{typography.label-md}"
  link-hover:
    textColor: "{colors.primary}"
    typography: "{typography.label-md}"
  badge:
    backgroundColor: "{colors.secondary}"
    textColor: "{colors.on-surface}"
    typography: "{typography.label-sm}"
    rounded: "{rounded.full}"
    padding: 4px 12px
    height: auto
    width: auto
    borderColor: "{colors.outline}"
    outlineOffset: 0px
  badge-error:
    backgroundColor: "{colors.error}"
    textColor: "{colors.on-surface}"
    typography: "{typography.label-sm}"
    rounded: "{rounded.full}"
    padding: 4px 12px
    height: auto
    width: auto
    borderColor: "{colors.outline}"
    outlineOffset: 0px
  badge-success:
    backgroundColor: "{colors.success}"
    textColor: "{colors.on-surface}"
    typography: "{typography.label-sm}"
    rounded: "{rounded.full}"
    padding: 4px 12px
    height: auto
    width: auto
    borderColor: "{colors.outline}"
    outlineOffset: 0px
  divider:
    backgroundColor: "{colors.outline}"
    height: 1px
    width: 100%
  swatch-background:
    backgroundColor: "{colors.background}"
    rounded: "{rounded.sm}"
    size: 32px
motion:
  duration-short: 200ms
  duration-medium: 300ms
  easing-standard: cubic-bezier(0.4, 0.0, 0.2, 1)
elevation:
  sm: "2px 2px 0px #000000"
  md: "4px 4px 0px #000000"
  lg: "8px 8px 0px #000000"
---

## Overview

UseFlo is a bright, high-energy productivity application designed specifically for students. It utilizes a playful, neo-brutalist visual style characterized by bold pastel colors, thick black borders, solid offset shadows, and friendly hand-drawn elements. The interface is designed to make task management feel rewarding, tactile, and engaging.

## Colors

The color strategy relies on a high-contrast, playful palette that pairs bright pastel accents with heavy black outlines. A warm, paper-like background softens the high-contrast elements, while vibrant primary and secondary colors draw attention to key interactive states and achievements.

*   `{colors.primary}` (#FF90E8): The signature bright pink used for primary branding, hero backgrounds, and key call-to-actions.
*   `{colors.secondary}` (#FFC900): A vibrant yellow used for secondary highlights, marquee tickers, and active state badges.
*   `{colors.background}` (#F6F4EC): A warm, off-white paper-like background color that softens the high-contrast black borders.
*   `{colors.surface}` (#FFFFFF): Pure white used for card backgrounds and input fields to ensure readability.
*   `{colors.surface-container}` (#F6F4EC): A container surface variant matching the off-white background for nested elements.
*   `{colors.on-surface}` (#000000): Deep black ink color used for primary body text and high-contrast readability.
*   `{colors.on-primary}` (#000000): Black text used on top of the primary pink background to maintain high contrast.
*   `{colors.outline}` (#000000): Thick black borders characteristic of the neo-brutalist design style.
*   `{colors.error}` (#FF7051): A warm coral-red used for error states, streak warnings, and destructive badges.
*   `{colors.success}` (#23A094): A minty teal green used for completed tasks, success states, and positive progress indicators.

## Typography

The typography system is built entirely on the DM Sans font family, delivering a clean, geometric, yet friendly aesthetic. Heavy weights are used for high-impact headers to anchor the neo-brutalist design, while lighter weights maintain readability across body copy and metadata.

*   `{typography.display-lg}`: Extra-large bold heading in DM Sans used for primary hero statements.
*   `{typography.display-md}`: Large bold heading in DM Sans used for major section introductions.
*   `{typography.headline-lg}` (inferred): Standard section heading size for feature titles.
*   `{typography.headline-md}` (inferred): Sub-section heading size for feature descriptions.
*   `{typography.headline-sm}` (inferred): Small headings for card titles and list headers.
*   `{typography.body-md}`: Primary body copy size for high readability on desktop viewports.
*   `{typography.body-sm}` (inferred): Secondary body copy size for smaller descriptions and metadata.
*   `{typography.label-md}` (inferred): Interactive labels, button text, and navigation links.
*   `{typography.label-sm}` (inferred): Micro-labels, badge text, and small helper text.

## Layout

*   **Grid & Spacing**: Built on a structured grid with a max-width container of 1200px, using a base spacing scale where `{spacing.md}` (16px) acts as the standard gutter and padding unit.
*   **Section Order**: The page flows top-to-bottom through the following sections: nav, hero, ticker, features, pricing, faq, and footer.
*   **Hero Pattern**: Features an asymmetric layout with a bright pink background, large bold typography on the left, and a tilted neo-brutalist task list card on the right.
*   **Responsive Behavior**: Utilizes a mobile-first layout with collapsing navigation and stacked feature cards on smaller viewports, maintaining the playful, hand-drawn aesthetic across all screen sizes.

## Elevation & Depth

Depth is conveyed through flat, solid offset shadows rather than soft, blurred gradients, characteristic of a neo-brutalist approach. These inferred shadows use hard black drop shadows to lift elements off the page, creating a tactile, comic-book-like interface.

*   `elevation.sm` — Used for small interactive elements, minor buttons, or nested containers.
*   `elevation.md` — Used for standard interactive cards and primary buttons to give them a distinct neo-brutalist offset shadow.
*   `elevation.lg` — Used for major hero elements, modals, or highlighted feature cards to maximize visual depth.

## Shapes

The shape language relies on a high-contrast mix of sharp, black borders and rounded corners. This juxtaposition balances the harshness of neo-brutalist outlines with friendly, approachable geometry.

Interactive elements like buttons use a subtle `{rounded.md}` radius, while standard containers and cards use a more pronounced `{rounded.lg}` radius to establish structure. Badges, tags, and pill indicators utilize `{rounded.full}` to create a friendly, pill-like appearance. Small elements like color swatches use `{rounded.sm}` to maintain crispness.

## 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 uses `{colors.primary}` as its background, wrapped in a solid `{colors.outline}` border. On hover, the background transitions to `{colors.secondary}`. Use this for the main call-to-action on a page or form.

### button-secondary

A secondary action button with a `{colors.surface}` background and `{colors.outline}` border. It maintains high contrast while remaining visually subordinate to the primary button. Use this for alternative choices or secondary actions.

### card

The standard container component featuring a `{colors.surface}` background, `{rounded.lg}` corners, and a solid `{colors.outline}` border. It provides structured containment for content blocks. Use this to group related feature information.

### card-elevated

An interactive variant of the standard card that incorporates a solid drop shadow using `elevation.md` or `elevation.lg`. It visually lifts off the background to signify interactivity. Use this for clickable features or high-priority content blocks.

### card-flat

A flat, non-interactive container that uses `{colors.surface-container}` as its background and `{rounded.md}` corners. It does not feature a heavy shadow. Use this for nesting secondary information inside a standard card.

### input-field

The text input component features a `{colors.surface}` background, `{rounded.md}` corners, and a `{colors.outline}` border. When focused, the border color changes to `{colors.primary}` with an outline offset of 2px. Use this for forms and search inputs.

### link

Text links utilize `{typography.label-md}` and `{colors.on-surface}` text. On hover, the text color transitions to `{colors.primary}`. Use this for inline navigation or secondary actions.

### badge

A small pill-shaped indicator using `{colors.secondary}` background, `{colors.on-surface}` text, and `{rounded.full}` corners. Use this for general status tags, highlights, or category labels.

### badge-error

A status badge variant using `{colors.error}` background and `{colors.on-surface}` text with `{rounded.full}` corners. Use this exclusively for error states, streak warnings, or destructive indicators.

### badge-success

A status badge variant using `{colors.success}` background and `{colors.on-surface}` text with `{rounded.full}` corners. Use this for completed tasks, positive progress, and success states.

### divider

A simple horizontal line using `{colors.outline}` with a height of 1px. Use this to separate distinct content blocks within a card or page layout.

### swatch-background

A small visual indicator using `{colors.background}` and `{rounded.sm}` corners. Use this for color selection interfaces or background preview swatches.

## Do's and Don'ts

| Do | Don't |
| --- | --- |
| Use `{colors.primary}` for primary call-to-action backgrounds like `{button-primary}`. | Do not apply `{colors.primary}` text on `{colors.secondary}` backgrounds due to low contrast. |
| Apply `{colors.outline}` thick borders to all interactive elements like `{card}` and `{button-secondary}`. | Avoid using borderless containers; always wrap `{card}` elements with a solid `{colors.outline}` stroke. |
| Use `{typography.display-lg}` for high-impact hero headings to maintain the bold, playful aesthetic. | Do not mix font families; stick strictly to `{typography.body-md}` and other levels defined in DM Sans. |
| Use `{rounded.md}` on buttons and `{rounded.lg}` on cards to ensure consistent corner rounding. | Never use a border radius larger than `{rounded.lg}` on standard cards to prevent them from looking overly pill-shaped. |
| Apply `{elevation.md}` to interactive cards to give them a distinct neo-brutalist offset shadow. | Never use soft, blurry shadows instead of the solid offset `{elevation.md}` or `{elevation.lg}`. |
| Use `{colors.success}` for positive status indicators and completed task `{badge-success}` elements. | Do not use `{colors.error}` for standard non-destructive badges or labels. |
| Style text input focus states with `{colors.primary}` borders and an outline offset of 2px. | Do not let focused inputs remain styled with standard `{colors.outline}` borders. |
| Separate nested content blocks inside `{card-flat}` containers using a `{divider}` with `{colors.outline}`. | Do not use light gray dividers that violate the high-contrast `{colors.outline}` aesthetic. |

## Content Style

*   **CTA Style**: Call-to-actions must be action-oriented, friendly, and low-friction (e.g., "Continue with Google", "Try the demo"). Use active verbs and clear, direct phrasing.
*   **Heading Tone**: Headlines should be playful, direct, and encouraging (e.g., "Do the thing. Feel amazing."). They should motivate the user and maintain a lighthearted, student-friendly energy.
*   **Copy Density**: Content must be highly scannable, utilizing bulleted lists and short, punchy paragraphs. Avoid dense blocks of text to keep the interface feeling fast and approachable.

## Imagery & Icons

The imagery style features a playful, hand-drawn aesthetic with thick black strokes, star shapes, and a custom cartoon character logo. High-contrast UI mockups must utilize solid drop shadows to match the neo-brutalist interface. Icons should align with this hand-drawn, thick-stroke language, avoiding thin or overly minimalist vector styles.

---

## Companion prompt

## Role
You are an AI assistant generating UI components and layouts for UseFlo, a playful, neo-brutalist student productivity app with a bold, energetic tone. Content, copy, and information architecture remain owned by the product team.

## How to use design.md
1. Reference every visual value by token name — `{colors.primary}`, `{typography.display-lg}`, `{spacing.lg}`, `{rounded.md}` — never hardcode hex values, pixel sizes, or font names.
2. Render only the component variants listed under `components:` (`button-primary`, `card`, `badge`, etc.). Do not invent variants the spec doesn't define.
3. Apply the neo-brutalist shape rules: `{rounded.md}` on buttons and inputs, `{rounded.lg}` on cards, `{rounded.full}` on badges and tags. All interactive elements and cards must carry a solid `{colors.outline}` border — never borderless.
4. Use solid offset shadows (`{elevation.md}`, `{elevation.lg}`) exclusively. The spec prohibits soft, blurry drop shadows; surface this conflict if a user requests one.
5. Follow the Layout note: contain content to ~1200px, use the `{spacing.xs}`–`{spacing.2xl}` scale for all gaps and padding, and allow subtle rotation or offset on elements to preserve the hand-drawn feel.

## Output contract

**Must:**
- Use all tokens by name on every generated component.
- Include hover, focus, and disabled states whenever the spec defines them (`button-primary-hover`, `input-field-focus`, `link-hover`).
- Maintain contrast ≥ 4.5:1 on body text; never place `{colors.primary}` text on `{colors.secondary}` backgrounds.
- Use `{colors.success}` only for positive states and `{colors.error}` only for destructive or warning states.

**Must NOT:**
- Invent colors, radii, or font families outside the spec.
- Use a radius larger than `{rounded.lg}` on standard cards.
- Apply soft blurry shadows in place of solid offset shadows.
- Add emoji, filler copy, or marketing language.
- Rewrite existing page copy, button labels, headings, or alter navigation structure.

## When in doubt
- If a value isn't in the spec, ask the user before inventing one.
- Prefer composing existing components over introducing new tokens.
- For ambiguous backgrounds use `{colors.surface-container}`; for text on those surfaces use `{colors.on-surface}`.
- For unspecified breakpoints, default to mobile-first with one breakpoint at 768px.
- Tokens marked "(inferred)" in spec prose are approximations; defer to any authoritative theme file if one exists.
