Sonar DESIGN.md

Brands

Code quality and security design with clean developer dashboards, orange-blue brand energy, and issue remediation clarity.

Raw DESIGN.md

At a glance

Group
Brands
Main color
#236afaBlue design systems
Fonts
InterSF Mono

Colors in this file

  • #ffffff

    background

  • #236afa

    background

  • #0b1f33

    background

  • #e2e8f0

    Unnamed

  • #ff7a1a

    Unnamed

  • #22c55e

    Unnamed

  • #dc2626

    Unnamed

  • #f8fafc

    Unnamed

  • #64748b

    Unnamed

  • #15803d

    Unnamed

Code quality and security design with clean developer dashboards, orange-blue brand energy, and issue remediation clarity.

1. Visual Theme & Atmosphere

Sonar should feel like code quality made measurable and actionable. The interface needs to support SonarQube, SonarCloud, SonarQube for IDE, clean code metrics, security issues, quality gates, and team remediation workflows.

  • Mood: precise, analytical, developer-focused, quality-driven
  • Density: medium-to-high for issue lists and metrics
  • Character: white dashboards, blue/orange accents, quality gate indicators, code snippets

2. Color Palette & Roles

TokenHexRole
--sonar-blue#236AFAPrimary action and links
--sonar-orange#FF7A1ABrand energy and attention
--sonar-navy#0B1F33Strong text and dark panels
--sonar-green#22C55EPassed quality gate
--sonar-red#DC2626Failed gate / high severity
--surface-page#F8FAFCPage background
--surface-card#FFFFFFCards and tables
--border-default#E2E8F0Dividers and inputs
--text-muted#64748BMetadata

Use green/red only for real quality status. Use blue for navigation and orange for brand emphasis.

3. Typography Rules

css--font-sans: Inter, ui-sans-serif, system-ui, -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif;
--font-mono: "SF Mono", "JetBrains Mono", "Roboto Mono", Menlo, monospace;
ElementSizeWeightLine Height
Hero Display56px7001.05
Page Title38px7001.12
Section Title28px6501.2
Metric Title20px6501.3
Body16px4001.6
Code13px5001.55
Label13px6001.35

4. Component Stylings

css.button-primary {
  min-height: 44px;
  padding: 0 18px;
  border: 1px solid #236AFA;
  border-radius: 10px;
  background: #236AFA;
  color: #FFFFFF;
  font: 600 14px/1 Inter, sans-serif;
}

.quality-card {
  border: 1px solid #E2E8F0;
  border-radius: 14px;
  background: #FFFFFF;
  padding: 18px;
}

.gate-pass {
  background: rgba(34, 197, 94, 0.12);
  color: #15803D;
}

.code-panel {
  border-radius: 14px;
  background: #0B1F33;
  color: #FFFFFF;
  padding: 16px;
}

5. Layout Principles

TokenValueUsage
--space-28pxMetric rows
--space-416pxDashboard rhythm
--space-524pxCards
--space-848pxMajor sections

Organize by project, branch, quality gate, issue type, severity, rule, and remediation owner.

6. Depth & Elevation

css.shadow-card { box-shadow: 0 8px 18px rgba(11, 31, 51, 0.07); }
.shadow-panel { box-shadow: 0 18px 42px rgba(11, 31, 51, 0.12); }

Use flat cards for analytics and focused elevation for issue detail overlays.

7. Do's and Don'ts

Do make quality gates unmistakable. Do use code evidence and rule context. Do not turn code quality into abstract charts only. Do not mix warning colors without severity labels.

8. Responsive Behavior

BreakpointMin WidthBehavior
Mobile0pxStack metrics and issue cards
Tablet768pxTwo-column dashboard cards
Desktop1200pxFull issue table, metric panels, and code view

Tables should collapse into card rows on mobile.

9. Agent Prompt Guide

Design like Sonar: clean code-quality dashboard, blue primary actions, orange brand accents, quality gate status, code evidence panels, and precise remediation workflows.

Use it with your agent

Save the file as DESIGN.md in your project root, then ask your agent to follow it for UI work. Or let the agent fetch it over MCP.

Download

curl -o DESIGN.md https://www.uiskillbook.com/design-md/sonar.md

MCP server

https://www.uiskillbook.com/mcp

MCP tool call

get_design_md({ "slug": "sonar" })