Quick look above; the showcases render the full Slipstream bank with sample data. Captured values only on A-side — anatomy stays ours until we craft a library.
Style Guide preset (skin)
primary
#6b4eff
pri-accent
#6b4eff
secondary
—
sec-accent
—
Surfaces — page · alt · emphasis · inverse
page
#000000
alt
—
emphasis
—
inverse
—
btn hover
#ffffff
Heading font
Mona Sans → Google: Inter
Body font
DM Sans (Google)
Heading line-height
1
Mobile h1
?
Mobile overflow
62px ⚠
Base size
16px
Type scale
not detected
Rounding
Very rounded (48px)
Line width
not detected
Button hover
not detected
Text-over-image halo
not detected
Heading tracking
not detected
Label tracking
not detected
Focus ring
not detected
Easing
not detected
Container max
1140px
Section padding
not detected
Accent gradient
not detected
Icon stroke
not detected
Spacing unit
not detected
Transition
300ms
Link underline
false
Button
not detected
rendered (getComputedStyle on laid-out page) — higher fidelity than the regex engine
Contact form — how the fields render
field border
#666666
field fill
#000000
field text
#ffffff
focus
#666666
submit
#000000
Captured from
scalify.au/ (home page)
Fields
1 · single-column
Field border
0px none #666666
Field radius
3px
Field height
46px
Field padding
8px 16px 8px 16px
Field font
-apple-system 20px
Field shadow
not detected
Focus state
none
Label
no visible labels
Submit
"Claim Now →" · #000000 · radius 48px
Captured form-field facts. These feed the contact-form component — see the field-token proposal in docs/contact-form-component.md.
Capture audit — what's real vs default
11 of 27 values captured from this site. The rest fall back to library defaults — shown so nothing hardcoded can pass as captured.
Brand primarycaptured: #6b4eff
Secondary colourdefault
Page backgroundcaptured: #000000
Text colourdefault
Text colour (inverse)default
Heading colourdefault
Link colourdefault
Link colour (inverse)default
Heading fontcaptured: Mona Sans
Body fontcaptured: DM Sans
Heading size (H1)captured: 24px
Heading weightcaptured: 800
Heading trackingdefault
Primary button bgcaptured: #000000
Primary button radiuscaptured: 40
Roundingcaptured: 48px
Line / border widthdefault
Button hoverdefault
Focus ringdefault
Easingdefault
Transition speedcaptured: 300ms
Container max-widthcaptured: 1140px
Section paddingdefault
Accent gradientdefault
Image treatmentdefault
Text-over-image halodefault
Icon strokedefault
Alt background (derived from page)library default
Card paddinglibrary default
Small/large shadow scalelibrary default
Secondary-button outline stylelibrary default
Inventory (raw evidence)
Palette by frequency
#ffffff ·1
#e5e4ff ·1
#6366f1 ·1
#1a1a1a ·1
#666666 ·1
Radii
pill
Shadow samples
none / flat
Character & component map
Shadow usage
none/flat
Border usage
light
Gradients
rare/none
Uppercase labels
no
Letter-spacing
no
Components observed vs gaps (gaps left empty — never auto-filled)
navGAP
heroGAP
buttonsGAP
cardGAP
pricingGAP
testimonialGAP
feature-gridGAP
galleryGAP
accordion-faqGAP
tabsGAP
tableGAP
formGAP
footerGAP
dropdownGAP
Worth considering — seen here, not yet captured
Notable styling present in this site's CSS that the tool doesn't yet turn into a captured value — candidates for future capture. Full coverage & roadmap →
Nothing notable beyond what we already capture.
Beyond the capture — Claude's read & generative proposals
The character CSS mining can't reach — bespoke anatomy, motifs, the "feel". These are my interpretations and generative suggestions. They are NOT applied to the reconstruction above — they're ideas to react to when this becomes a library's seed.
Not reviewed yet. Ask Claude in chat to “read this teardown” and I'll add observations + generative proposals here.
