Effect

Effect

Effect is a powerful TypeScript library designed to help developers easily create complex, synchronous, and asynchronous programs.

3.0
2
Visits
Visit

Available Pages

Version History

Design Analysis

Effect Home design analysis

Design developer-tool pages that feel credible on both the marketing and documentation sides. The dark hero should feel polished and ambitious, while the docs shell should flip into a highly usable light product without...

Overview

Design developer-tool pages that feel credible on both the marketing and documentation sides. The dark hero should feel polished and ambitious, while the docs shell should flip into a highly usable light product without breaking the overall identity.

Image Direction

Use dark media frames, blue-highlighted text, and code surfaces as the main visual language. Product artifacts should look like tools: video windows, editors, playground panes, and clean docs cards. Keep decorative imagery secondary to the utility story.

Colors

Use near-black and charcoal for the hero shell, then switch to cloud-gray and white inside the docs environment. Keep blue as the throughline across both modes, with indigo as a supporting brand note.

Typography

Use a softer geometric display face for major claims and a neutral sans everywhere else. Mono should sit exactly where code and developer affordances appear, not as a general branding voice.

Design.md

System Overview

Core identity and authoring metadata from the refto.one design model.

Midnight TypeScript Lab

A developer-library system balancing midnight hero contrast, cobalt highlights, and documentation-grade light surfaces.

developer-focused, polished, and dual-shell with dark launch energy and light product utility

Primary mode: darkdeveloper tool marketing and docshybrid marketing-docs

Theme

Fields outside the primary renderer remain visible here as structured fallback content.

Visual atmosphere
Summary
developer-focused, polished, and dual-shell with dark launch energy and light product utility
Density
3
Variance
3
Motion
2
Signals
dark hero shell · blue code accent · light docs product · rounded video frame

Colors

Primitive palettes and resolved token colors for the active preview mode.

Palette colors
Night
#09090B
Slate Border
#27272A
Effect Blue
#4B8CFF
Effect Indigo
#4B3CAA
Cloud Surface
#F5F6F8
Zinc Copy
#A1A1AA
Pure White
#FFFFFF
Usage rules
Use dark mode for the marketing hero and major proof sections.
Let docs surfaces flip to light gray and white without losing the blue accent thread.
Keep highlight blue controlled and technical, not playful.

Token Spacing

Spacing scales rendered as tokens with a simple length specimen.

xs
6px
sm
10px
md
16px
lg
24px
section
96px

Token Radii

Corner radii tokens with a live surface sample.

sm
6px
md
12px
lg
20px
full
999px

Typography Families

Font families from the current design YAML, including fallback stacks and usage character.

Display
Cal Sans
soft geometric display with modern weightlessness
Body
Inter
developer-friendly marketing and docs copy
Mono
ui-monospace
code tabs and playground content

Typography Scale

Top-level typography scale rendered as live text specimens.

Display
3rem/—
Display
H2
2.25rem/—
H2
Body
1rem/—
Body
Caption
0.8125rem/—
Caption

Typography Rules

Fields outside the primary renderer remain visible here as structured fallback content.

Rules
Use the display face for large hero and section statements only. · Keep body copy neutral and readable across both dark and light shells. · Mono belongs to code, tabs, playground chrome, and developer detail.

Motion

Motion tokens rendered as resolved values for timing and personality.

Duration
160ms-240ms
Easing
cubic-bezier(.2,.8,.2,1)
Spring
stiffness 115, damping 20

Motion

Resolved motion token values.

PropertyValue
duration160ms-240ms
easingcubic-bezier(.2,.8,.2,1)
springstiffness 115, damping 20

Layout Principles

Use a split hero with copy on one side and a rounded media frame on the other.
Let dark proof sections segue into a clean, product-like docs shell rather than maintaining one flat theme.
Keep code examples and playground surfaces orderly and componentized.

Component Preview

Low-complexity component tokens rendered as design-system specimens.

Buttons primary
Base Attributes
Background
#FFFFFF
Text
#111111
Border
0px none transparent
Radius
12px
Padding
12px 22px
Min height
40px
Buttons secondary
Base Attributes
Background
transparent
Text
#FFFFFF
Border
1px solid #27272A
Radius
12px
Padding
12px 20px
Min height
40px
Cards media
Feature Card
Component preview content
Base Attributes
Background
#111214
Text
#F5F6FA
Border
1px solid #6B6E7A
Radius
20px
Padding
16px
Cards docs
Feature Card
Component preview content
Base Attributes
Background
#F5F6F8
Text
#353841
Border
1px solid #C0C2C7
Radius
12px
Padding
16px
Navigation docs
OverviewFeaturesDocs
Base Attributes
Background
#FFFFFF
Text
#353841
Border
1px solid #C0C2C7
Radius
6px
Item padding
10px 12px
Tabs code
Base Attributes
Background
#09090B
Text
#FFFFFF
Border
1px solid #27272A
Radius
12px
Inactive text
#A1A1AA

Image direction

Schema-agnostic optional blocks from the design YAML. New option keys render here automatically.

Role
supportive
Media types
  • -
    rounded video frame
  • -
    code sample panel
  • -
    docs utility surface
Subject patterns
  • -
    dark video window
  • -
    blue-highlighted text
  • -
    clean light documentation chrome
Composition logic
  • -
    Treat media as a product artifact, not decorative filler.
  • -
    Let the docs shell feel tool-like and highly usable.
Treatment rules
  • -
    Use blue to reinforce TypeScript and action cues.
  • -
    Keep docs and blog imagery sparse and utility-led.
Generation cues
  • -
    developer library landing page with dark hero and blue accent
  • -
    light docs UI with clean code panels
Avoid
  • -
    No flashy crypto neon palettes.
  • -
    No dense enterprise dashboard walls.

Anti Patterns

Compact list of patterns the design system explicitly avoids.

  • -
    Do not force the docs shell to stay as dark as the hero.
  • -
    Do not replace the technical blue accent with consumer rainbow gradients.
  • -
    Do not make code and playground surfaces visually chaotic.