VirtuProbe Studio / Brand

v0.1 · internal · last updated 2026-05-03

Brand guidelines.

A working reference for everything VirtuProbe Studio touches — landing page, docs, social, packaging. Not a museum: edit when reality demands it.

The mark

Dagger in a hex.

A precision instrument inside a tessellating field — the icon for a tool that probes systems with intent. The dagger reads as offensive tooling; the hex grid reads as systems and structure. The mint→lime gradient is the only sanctioned brand gradient.

Use the mark wherever space is tight (favicon, app icon, social avatar). Use a wordmark lockup whenever the surface allows it.

VirtuProbe Studio mark

Colors

01 / Tokens

Surfaces

bgVoid#0A0D0C
bg-1Surface#0F1413
bg-2Raised#141A18
bg-3Overlay#1B231F

Foreground

fgPrimary#E6F2EC
fg-dimBody#A3B3AC
fg-muteMute#6B7872
fg-faintFaint#3D4742

Brand & signal

brand · gradientProbe#5EF0C2 → #8DF860
accentNeon#6FF39B
warnProbe-warn#F5C453
dangerHalt#FF6B6B

Rules. Surfaces stack: bg → bg-1 → bg-2. The gradient appears on the mark and at most one hero element per page. The flat --neon token is the workhorse for links, focus, and CTAs. Never use neon for body copy.

Typography

02 / Type
Display Chakra Petch 500 / 600 / 700 Headlines, marks, eyebrows
Probe. Chain. Exploit.
Body Geist 300 / 400 / 500 / 600 UI, paragraphs, navigation
The request manager for people who break things — built for engineers who treat HTTP like a contract worth interrogating.
Mono Geist Mono 400 / 500 Code, tokens, metadata
POST /v1/auth/login → 401 Unauthorized · 84ms

Scale

display-1Probe everything.72 / 1.02 / -1%
display-2Chain everything.48 / 1.05 / 0%
headingSection title32 / 1.15 / 0.5%
subheadComponent subhead20 / 1.3 / -0.5%
bodyWorkhorse paragraph copy used across the product, marketing and docs.15 / 1.55 / 0%
captionMETA · TIMESTAMP · STATUS12 / 1.4 / 12%

Voice

04 / Tone

Confident, technical, occasionally cheeky. We respect the reader's time and intelligence. We never bluff. If something's a beta, we say beta.

Do

  • Speak like a senior engineer reviewing a PR. This chains 14 requests in 80ms. Yours doesn't.
  • Use precise verbs. Probe the endpoint. Chain the response. Replay until it breaks.
  • Keep humor dry and earned. If your test plan ends at HTTP, half your bugs ship to prod.
  • Show, then tell. Lead with a code or screenshot, follow with a sentence.

Don't

  • Sound like enterprise marketing. Unleash synergies across your API surface.
  • Posture about hacking. Dominate every endpoint. Pwn the gateway.
  • Use AI-fluff hedges. Empower teams to leverage requests holistically.
  • Pile on adjectives. One sharp word beats three soft ones.