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
#1e1b15
pri-accent
#bb4111
secondary
—
sec-accent
—
Surfaces — page · alt · emphasis · inverse
page
#fff9e5
alt
#f4f3f0
emphasis
—
inverse
#1e1b15
Heading font
Iowan Old Style → Google: Inter
Body font
ui-sans-serif → Google: Lora
Heading line-height
1
Mobile h1
72px → 36px ⚠ big
Mobile overflow
none
Base size
16px
Type scale
not detected
Rounding
Slightly rounded (8px)
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
not detected
Section padding
not detected
Accent gradient
not detected
Icon stroke
not detected
Spacing unit
not detected
Transition
150ms
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
heroGAP
buttonsobserved
cardGAP
pricingGAP
testimonialobserved
feature-gridGAP
galleryGAP
accordion-faqobserved
tabsGAP
tableGAP
formobserved
footerobserved
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 →
scroll-snap35×
filter (blur etc.)21×
sticky positioning7×
object-fit7×
scroll-behavior7×
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.