Arkaes Brand Guidelines Foundation Color Typography Buttons Logo Voice Touchpoints Rules Foundation Color Typography Buttons Logo Voice Touchpoints Rules
01 · Brand Foundation

Who is Arkaes?

A frontend engineer with a deep respect for systems and an obsession with the visual. Every interface decision is deliberate — beauty and function are never separate concerns.

01
Craft

Every interface decision is deliberate. Beauty and function are never separate concerns. The work is finished when nothing can be removed.

02
Structure

Systems thinking underpins every project — scalable, maintainable, and architecturally sound from the first component to the final deployment.

03
Restraint

Less, but better. Negative space, typographic discipline, and color used with intention. Secondary color appears only when it clarifies hierarchy.

Archetype

The Refined Practitioner — authoritative craft, expressed with warmth.

Audience

Product teams, design-led companies, and brands who value quality over quantity.

Promise

Interfaces that are as well-considered as they are beautiful to use.

Personality

Calm. Precise. Quietly confident. Never loud, never generic.

Primary Tagline
"Architecture meets aesthetics."
02 · Color System

The Palette

The system uses semantic color tokens first. Accent carries brand emphasis; secondary is a restrained counterpoint for structure, confirmation, and contrast.

Background
#fbf8f3
--ark-color-bg
Surface
#fafaf9
--ark-color-surface
Surface Soft
#f6f0ea
--ark-color-surface-soft
Surface Floating
#f7e8e3
--ark-color-surface-floating
Text
#17130f
--ark-color-text
Text Muted
#5f534a
--ark-color-text-muted
Accent
#8f554d
--ark-color-accent
Accent Soft
#f2ddd7
--ark-color-accent-soft
Accent Strong
#653a35
--ark-color-accent-strong
Secondary
#5f6f48
--ark-color-secondary
Secondary Soft
#e2e7d6
--ark-color-secondary-soft
↑ Accent and secondary tokens — prefer semantic names in new implementation
Accent

Use --ark-color-accent and --ark-color-accent-strong for emphasis, active states, highlighted display text, and brand-defining details.

Secondary

Use --ark-color-secondary sparingly as a counterpoint for structure, success states, rules, and moments that need contrast from the accent family.

Text

Primary copy uses --ark-color-text. Supporting copy uses --ark-color-text-muted or --ark-color-text-subtle only when contrast remains readable.

Surfaces

Use --ark-color-bg for page backgrounds, --ark-color-surface for raised surfaces, and --ark-color-surface-soft for quiet section contrast. Chrome that floats free over the page — the navigation pills, the bottom dock's actions, inline code — uses --ark-color-surface-floating over a --ark-color-border-floating outline. The fill is a light blush tint; the outline is deeper than the default hairline on purpose, because on a fill that light the edge is what makes the control read as a distinct object.

03 · Typography

The Type System

Three type roles. No more. Display type carries the brand expression, sans-serif body text carries clarity, and mono labels provide structure. Decorative serif is reserved for large headings only.

Display / Headlines
Fraunces Display stack · thin / 300
Craft meets architecture.
Hero titles · Section headers · Project names · Logotype · Pull quotes
Use --ark-font-display with --ark-weight-thin. Italic is reserved for concise emphasis and the Æ.
Body / Reading
Plus Jakarta Sans Body stack · regular / medium
Building interfaces where structural clarity and aesthetic sensibility converge into something readable, deliberate, and easy to use.
Body copy · Case studies · Project descriptions · UI descriptions
Use --ark-text-md through --ark-text-lg, --ark-leading-normal through --ark-leading-relaxed, and --ark-measure-md.
Labels / UI / Metadata
JetBrains Mono stack Bold uppercase labels
Frontend Engineer · arkaes.dev · 2026 · v1.0
Eyebrows · Nav links · Tags · Dates · Metadata · Code snippets
Use --ark-font-mono, --ark-weight-bold, uppercase text, and token letter-spacing.
Type Scale
4xl
Architecture
Hero Display
3xl
Craft meets aesthetics
H1 / Section Hero
2xl
Selected Work
H2 / Section Title
xl
Design System Overhaul
H3 / Project Name
lg
Building interfaces where clarity converges with aesthetics.
Body Large
xs
FRONTEND ENGINEER · 2026
Label / Mono
Readability Tokens
Contrast

Primary text uses --ark-color-text. Supporting text uses --ark-color-text-muted, which must remain readable on both light and dark surfaces.

Body Type

Body text uses --ark-font-sans. Decorative serif/display type is reserved for large headings, wordmark moments, and short pull quotes only.

Measure

Long-form content should use --ark-measure-md or the .ark-readable utility to keep case studies comfortable to read.

04 · Interface — Buttons

The Emphasis Scale

One button, five levels of emphasis. Every action on an Arkaes surface sits somewhere on this ladder — from the single loud call-to-action down to inline serif navigation. Variants never compete: one primary per view, and everything else steps down.

primary
View all case studies
The one loud action per view
secondary
Browse all projects
Supporting action
outline
See the archive
Alternate path
ghost
Dismiss
Quiet utility
link
Back to home page
Inline navigation
Sizes
SmallMediumLarge

Three sizes scale the box for the four button-shaped variants. The link variant only scales its type — it never grows a box.

Danger Tone
Delete projectDiscard changesRemove

Tone composes with every emphasis level, so destructive actions can be loud or quiet — but always unmistakably destructive.

Do
  • Use one primary action per view — everything else steps down
  • Use the link variant for prose-adjacent navigation
  • Reserve tone="danger" for destructive actions
  • Put directional arrows in the prefix / suffix slots
  • Compose ark-button — never rebuild its styles by hand
Don't
  • Never place two primary buttons in the same view
  • Never use danger tone for emphasis — it signals destruction
  • Never mix accent and danger in one action cluster
  • Never box inline navigation that belongs to the link variant
  • Never hardcode button colors outside the token contract
06 · Voice & Tone

How Arkaes Speaks

Calm authority. Never loud. Never generic. Confident without being boastful. The work leads — the words follow.

01
Precise

Exact language. No filler phrases. Every word earns its place. If it can be removed without loss, remove it.

02
Warm

Approachable craft — not cold expertise. The work invites, not intimidates. People should want to work with Arkaes.

03
Considered

Thoughtful explanations of why, not just what. Process is visible. Decisions are explained, not just displayed.

04
Understated

The work speaks first. Self-description is minimal and factual. No superlatives, no passion-for-excellence clichés.

05
Curious

Genuine interest in problems. Questions are as valued as answers. Arkaes is always learning — and makes that visible.

Project description · Do

"A design system built for a multinational engineering team — 40+ components, zero visual inconsistencies, shipped in 6 weeks."

Project description · Don't

"I am a passionate and driven developer with a love for creating amazing user experiences that delight users and stakeholders."

About copy · Do

"Frontend engineer. Obsessed with the intersection of systems and craft."

About copy · Don't

"I'm a creative individual who loves bringing ideas to life through the power of technology and innovative design thinking!"

Call to action · Do

"Let's build something remarkable." — Never "Let's connect!" or "Hire me!"

07 · Digital Touchpoints

Brand Across Platforms

Every touchpoint should feel like it belongs to the same quiet, considered creative — regardless of the platform's own visual conventions.

arkaes.dev
Primary Portfolio
  • Semantic token system throughout: accent for emphasis, secondary for restrained counterpoint.
  • Fraunces display, Plus Jakarta Sans body, JetBrains Mono token labels.
  • Motion: staggered reveals and subtle hero parallax only when it improves orientation.
  • Light and dark modes are supported. Both must preserve strong text contrast and readable long-form copy.
  • Pointer feedback should be subtle and must preserve the default cursor on touch-first experiences.
GitHub
Code & Open Source
  • Profile README uses the Arkaes wordmark (text-based, mono variant).
  • Bio: "Frontend Engineer. Craft meets architecture. arkaes.dev"
  • Pinned repos: design system, AI-powered projects, portfolio source.
  • Commit voice: precise, lowercase, imperative mood. No emojis.
LinkedIn
Professional Network
  • Headline: "Frontend Engineer — UI Architecture, Motion Design & AI Integration"
  • Banner: token background with Arkaes wordmark and semantic accent rule.
  • About section uses the Arkaes voice — precise, warm, understated.
  • Featured section: link to arkaes.dev as primary CTA.
Dribbble
Design Showcase
  • Only post work reflecting the Arkaes aesthetic — no generic shots.
  • Use token background, surface-soft, or accent-soft backgrounds on mockups consistently.
  • Caption voice matches the brand: factual, no exclamation marks.
  • Shots should feel like excerpts from a unified body of work.

Consistency principle: Every touchpoint should feel like it belongs to the same quiet, considered creative. Platform-native conventions are respected, but the Arkaes voice, tone, and visual restraint remain non-negotiable regardless of where the brand appears.

08 · Usage Rules

Brand Integrity

What protects the brand — and what breaks it. These rules exist because the brand's refinement is fragile. One wrong choice dilutes years of consistency.

Do
  • Use exact token values — no approximations or eyeballed matches.
  • Use Fraunces for large display moments only; use readable sans-serif for body copy.
  • Apply grain texture subtly, matching the current implementation opacity.
  • Use secondary color as a restrained counterpoint, not as a second dominant accent.
  • Use semantic surface tokens instead of hard-coded background hex values.
  • Ensure every project shown reflects the Arkaes aesthetic.
  • Use .ark-readable for case studies and long-form project pages.
  • Use the Æ ligature in the wordmark — always.
  • Keep the Æ legible; use the mono wordmark in tight spaces.
Don't
  • Never use low-contrast muted text in dark mode. Dark mode is allowed only when text contrast remains strong.
  • Never use decorative serif for body paragraphs, small cards, labels, or long-form reading.
  • Never use accent and secondary colors at equal visual weight on the same page.
  • Never apply drop shadows, gradients, or glow effects on type.
  • Never show work that contradicts the refined aesthetic.
  • Never stack decorative motion that distracts from content.
  • Never use exclamation marks in brand copy.
  • Never modify the Æ color outside the brand specification.
"Architecture meets aesthetics."
ARKAES · ARKAES.DEV · 2026