Audience fit
Built for founder-led service teams in contracting, healthcare, HVAC, and operator-heavy businesses that need trust before spectacle.
Clockless Design System
Brand, tokens, logo assets, components, motion, and implementation references for the dark public website and the warm app-facing system layer.
Brand Foundations
This page is not a token dump. It explains why the brand looks this way, who it is for, and which assets are stable enough to reuse across future website and product work.
Built for founder-led service teams in contracting, healthcare, HVAC, and operator-heavy businesses that need trust before spectacle.
The public website stays dark, cinematic, and high-trust. The app-facing surface gets warmer, denser, and easier to work inside for long sessions.
Logo family, cyan/orange website accents, warm app tokens, signal green, glass shells, and orbital glow are canonical. They are not one-off experiments.
Every block here is designed to be screenshotted, referenced in PRs, and reused as the baseline for later marketing and product surfaces.
Logo System
These are the actual shipped assets from `public/brand/`. Show them on both dark and light grounds so later implementations do not guess about fit.
Default use on dark surfaces, nav bars, and hero areas.
120px minimum widthAvatar, app icon, profile surfaces, and compact navigation.
40px minimumTile-based contexts, social previews, and app launcher slots.
48px minimum
Fallback for dark-image overlays and exported static decks.
120px minimum widthBrowser tab, system shortcuts, and tiny brand affordances.
16px minimumKeep at least the favicon width around the mark. Never crowd it with dense UI chrome.
Primary logo belongs on dark surfaces. Circle and square variants handle smaller, lighter contexts.
Do not recolor, stretch, crop, or place the mark on noisy gradients that destroy edge clarity.
Color System
The dark website palette and the warm app palette belong to the same brand, but they solve different jobs. They must be displayed with context, not merged into one blob.
High-trust, cinematic, and public-facing.
Page canvas and large trust surfaces.
#060B18Sticky nav, glass shell, raised zones.
#0B1426Cards, demos, and comparison slices.
#101D35Links, highlights, orbital glow, section accents.
#00D4FFCTA energy, urgency, and secondary emphasis.
#FF6B35Live signal, success, and health state.
#10B981Warm, denser, and easier for long working sessions.
App docs and warm system background.
#FFF8F6Soft panels and grouped sections.
#FBF2EFInputs, muted surfaces, dividers.
#F5ECE9Cards and primary work surfaces.
#FFFFFFPrimary buttons and brand anchors.
#A03B00Secondary logic, data accents, and app contrast.
#4D44E3Status dots, healthy flows, completed loops.
#10B981System info, links, and contextual assistance.
#3B82F6Premium states, experimental features, and guidance.
#8B5CF6Needs attention, pending review, cautious states.
#F59E0BErrors, overdue states, broken automations.
#EF4444Typography
Typography must work in English and Chinese contexts. Use real sample copy instead of raw token labels so hierarchy is legible at a glance.
AI systems that never sleep.
AI 系统持续在线,不等人起床。Space Grotesk 700 · clamp(3.2rem, 8vw, 6rem)Systemized, cinematic, controlled.
系统化,但不做工具感堆砌。Space Grotesk 700 · clamp(2rem, 4vw, 3rem)Readable enough for long operator sessions and client-facing explanation.
给老板看得懂,也给客户感到安心。Plus Jakarta Sans 500 · 1rem / 1.7WEBSITE DARK / APP LIGHT / LIVE SIGNAL
网站深色 / App 浅色 / 状态可见Plus Jakarta Sans 600 · 0.78rem / trackingSurfaces, Borders, Radius, Shadows
Decide first whether the section needs glass, solid structure, or simply more space. Radius stays soft and modern; borders stay ghosted and supportive.
Use for sticky nav, hero utility panels, and high-trust overlays. Blur supports depth, not decoration.
Use for dense reading, operator cards, pricing, and testimonial blocks where content needs stable contrast.
If a section is already visually distinct, use rhythm and whitespace instead of wrapping it in another card.
Components
Every family below includes a usage note and a do / don’t rule so later pages can inherit the right behavior instead of only copying shapes.
Growth
“Clockless gives our operation a visible rhythm instead of a pile of reminders.”
Marcus Chen · Summit BuildersPrimary for decisive CTA, outline for secondary navigation, ghost/text for local actions.
Do: One clear primary action per cluster.Don’t: Do not make every button glow.Use pill labels for state, mode, and signal. Keep copy short and legible.
Do: Live, review, pilot, blocked.Don’t: Do not use badge stacks as decoration.Warm surface, clear border, and focused accent ring. Form fields should feel product-grade, not marketing-only.
Do: Use for lead capture and app forms.Don’t: Do not rely on placeholders as labels.Top nav is glass and shallow. Section nav is compact, sticky, and mobile-scrollable.
Do: Keep anchor nav accessible on small screens.Don’t: Do not hide core navigation on mobile.Cards can carry testimonials, pricing, feature comparisons, and operator work queues.
Do: Differentiate cards with tone and scale.Don’t: Do not repeat identical card grids without hierarchy.Green pulse for live, cyan for ready, amber for human review, red for failure.
Do: Tie motion to a real system state.Don’t: Do not animate everything at once.Motion & Loaders
The raw source libraries still exist under `/brand/loaders.html` and `/brand/animations.html`. Shipping UI should only promote the core set below.
AI thinking
Background processing
Composing or conversational reply
Async workflow progression
Page load: use staggered reveal and orbital atmosphere, not constant motion everywhere.
AI thinking: recommend Breathe and Orbit loaders for contemplative or background reasoning states.
Async action: use Typing, Pulse, or Pipeline for explicit in-progress moments.
Health state: keep the green pulse reserved for live / online / healthy signal.
Reduced motion: disable pulsing, spinning, and floating while preserving information hierarchy.
Galaxy and Morse are visually interesting but too ornamental for default UI.
Bounce and Hourglass feel louder than the Clockless baseline and should stay experimental.
Use `/brand/loaders.html` and `/brand/animations.html` as source libraries, not as shipping galleries.
Composition Examples
These blocks show what happens when tokens, surfaces, motion, and copy are composed into meaningful UI slices rather than isolated specimens.
Large headline, sparse accent copy, glow field, and one high-confidence CTA. The hero should feel premium before it feels busy.
Feature grids can break symmetry. One card leads, others support. Use cyan and orange sparingly to guide scan order.
Pricing earns a calmer, lighter island so cost and scope are easy to compare without glare fatigue.
Warm surfaces, disciplined borders, and strong typography make long operational sessions feel stable instead of flashy.
Implementation Notes
This page should act as the implementation contract for later website and product work, not just a presentation artifact.
Tokens: source from `~/.clockless/data/brand/tokens.css` and `~/.clockless/data/brand/DESIGN-SYSTEM.md`.
Website baseline: follow `clockless-website/SITE.md` and the approved `b99f4a9` visual language from `BRAND.md`.
Logo assets: use the real files under `public/brand/` and do not substitute generated mock marks.
Motion sources: curate from `public/brand/loaders.html` and `public/brand/animations.html`; do not dump every experiment onto shipping pages.
Static vs interactive: color, type, logo, and usage guidance can stay static; loaders and section anchors should remain interactive and responsive.