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
#006080
pri-accent
#00a0e3
secondary
—
sec-accent
—
Surfaces — page · alt · emphasis · inverse
page
#ffffff
alt
#e5e7eb
emphasis
#006080
inverse
#050608
btn hover
#006080
Heading font
IBM Plex Sans (Google)
Body font
NouvelR → Google: Inter
Heading line-height
1.5
Mobile h1
56px → 36px ⚠ big
Mobile overflow
none
Base size
20px
Type scale
not detected
Rounding
Very rounded (60px)
Line width
not detected
Button hover
shadow
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
72px
Accent gradient
not detected
Icon stroke
not detected
Spacing unit
not detected
Transition
not detected
Link underline
false
Button
not detected
rendered (getComputedStyle on laid-out page) — higher fidelity than the regex engine
Components observed vs gaps (gaps left empty — never auto-filled)
navobserved
heroobserved
buttonsobserved
cardGAP
pricingGAP
testimonialobserved
feature-gridGAP
galleryobserved
accordion-faqobserved
tabsGAP
tableGAP
formobserved
footerobserved
dropdownobserved
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 →
object-fit24×
filter (blur etc.)12×
scroll-snap12×
sticky positioning6×
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.
