Skip to content

Latest commit

 

History

History
56 lines (43 loc) · 2.34 KB

BRAND.md

File metadata and controls

56 lines (43 loc) · 2.34 KB

Brand System

DevDoctor is an AxiomNode project. The code is MIT-licensed; the DevDoctor name, logo, icon, and social banner in assets/brand/ identify that project. Forks and derived products are welcome under the MIT terms but should use their own name and marks so users can tell them apart from the AxiomNode release.

DevDoctor uses a calm workstation-bootstrap identity: dark terminal surfaces, cyan diagnostics, green ready states, amber warning states, and rose missing states.

Assets

  • Logo: assets/brand/devdoctor-logo.svg
  • Logo PNG: assets/brand/devdoctor-logo.png
  • App icon: assets/brand/app-icon.svg
  • App icon PNG: assets/brand/app-icon.png
  • Favicon: assets/brand/favicon.svg
  • Favicon PNG: assets/brand/favicon.png
  • GitHub social banner: assets/brand/github-social-banner.png
  • Terminal preview: assets/screenshots/terminal-preview.png
  • Demo GIF: assets/screenshots/devdoctor-demo.gif

Color Palette

Token Hex Use
Night #0B1020 Background
Panel #111827 Terminal panels and report surfaces
Border #263A55 Table and panel borders
Diagnostic Cyan #22D3EE Primary accent
Glow Cyan #67E8F9 Logo highlight
Ready Green #34D399 Installed states
Repair Amber #FBBF24 Broken or repairable states
Missing Rose #FB7185 Missing states
Text #E5EDF7 Primary text
Muted #8EA4BD Secondary text

Typography

  • Product and docs: Inter, Noto Sans, Segoe UI, or the system UI font.
  • Terminal/code labels: JetBrains Mono, Noto Sans Mono, or the user's terminal monospace.
  • Do not scale terminal text with viewport width.

Voice

DevDoctor sounds direct and operational.

  • Prefer: "Docker is missing. Install plan: sudo dnf install moby-engine."
  • Avoid: "Critical environment failure detected."
  • Prefer: "No changes made. Use --apply to execute commands."
  • Avoid: "Magic repair complete."

Interface Rules

  • Installed, missing, and broken counts are the primary visual anchors.
  • Use tables for comparable command data.
  • Always show exact commands before system changes.
  • Do not imply a command ran unless DevDoctor actually executed it.
  • Do not invent download sizes, latest versions, or package ownership data.
  • Screenshots and demo recordings must be generated from real DevDoctor output.