/brand
// design system & identity
/logo
// mark & wordmark
Clear space
Minimum clear space around the logo equals the height of the "n" character on all sides.
Background
Logo must always appear on dark backgrounds (#0a0a0a or darker). Never place on light or mid-tone surfaces.
Colors
"null" in #00ff41, "shift.sh" in #888888. Never recolor.
Use on dark backgrounds with proper clear space
Place on light backgrounds
Recolor the wordmark
Change the typeface
/colors
// click any swatch to copy
Core Palette
Pillar Colors
Backgrounds
Text
/typography
// two faces, one system
JetBrains Mono
Monospace / PrimaryHeadings, code, labels, navigation, terminal UI, buttons
Inter
Sans-serif / SecondaryBody text, descriptions, long-form content
Type Scale
/spacing
// consistent rhythm
/components
// live rendered demos
Buttons
<a class="btn btn-primary">> Execute</a>
<a class="btn btn-ghost">> View Source</a>
Status Tags
<span class="status-tag status-live">[LIVE]</span>
<span class="status-tag status-building">[BUILDING]</span>
<span class="status-tag status-concept">[CONCEPT]</span>
Pillar Badges
<span class="pillar-badge" data-pillar="privacy">privacy</span>
Terminal Prompt
nullshift@labs$ command
Hacker Card
Whisper Protocol
End-to-end encrypted messaging with zero metadata leakage.
/tone
// how we write
> Prefix for actions
All button text and list items use the > prefix. It signals executability and terminal heritage.
> Execute
> View Source
> Deploy to mainnet
// Subtitles & comments
Section subtitles use // comment syntax. Reinforces the code-first identity.
// engineering across four pillars
// prove everything, reveal nothing
[STATUS] brackets
Status indicators always use square brackets. Bold, scannable, unambiguous.
[LIVE]
[BUILDING]
[CONCEPT]
Terminal metaphors
UI elements reference terminal/hacker culture. File paths for navigation, commands for actions.
/services
nullshift@labs$
cat about.txt
Copy Rules
- > Technical, direct, aggressive. No fluff, no filler.
- > Write like you're composing a README, not a marketing brochure.
- > Prefer short sentences. Active voice. Cut every unnecessary word.
- > Never say "leverage" or "synergy." Say "use" and "combine."
- > Dark mode only. No sunshine metaphors. Think midnight, not midday.
- > When in doubt, ask: "Would a cypherpunk say this?"
/rules
// design system constraints
Use CSS custom properties from variables.css for all visual values
Load data from JSON files under data/ and render client-side
Use inline SVGs for icons. Never icon fonts.
Respect prefers-reduced-motion for all animations
Add frameworks, build tools, or CSS preprocessors
Use light mode, light backgrounds, or light color themes
Hardcode colors, fonts, or spacing. Use CSS variables.
Add tracking, analytics cookies, or third-party scripts