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
#c14679
pri-accent
#007bff
secondary
—
sec-accent
—
Surfaces — page · alt · emphasis · inverse
page
#06020e
alt
—
emphasis
—
inverse
—
Heading font
Georgia → Google: Lora
Body font
Jost (Google)
Heading line-height
1.1
Mobile h1
84px → 50px ⚠ big
Mobile overflow
none
Base size
16px
Type scale
not detected
Rounding
Slightly rounded (6px)
Line width
not detected
Button hover
swap background
Text-over-image halo
not detected
Heading tracking
not detected
Label tracking
not detected
Focus ring
not detected
Easing
not detected
Container max
1160px
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
Components observed vs gaps (gaps left empty — never auto-filled)
navobserved
heroobserved
buttonsobserved
cardGAP
pricingGAP
testimonialGAP
feature-gridGAP
galleryGAP
accordion-faqGAP
tabsobserved
tableobserved
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 →
filter (blur etc.)39×
object-fit34×
sticky positioning14×
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.