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
#00ffff
pri-accent
#2ff2f9
secondary
—
sec-accent
—
Surfaces — page · alt · emphasis · inverse
page
#ffffff
alt
—
emphasis
—
inverse
#000000
btn hover
#2ff2f9
Heading font
Poppins (Google)
Body font
Poppins (Google)
Heading line-height
1.29
Mobile h1
46.7px → 36.3px ⚠ big
Mobile overflow
none
Base size
16px
Type scale
not detected
Rounding
Sharp (1px)
Line width
not detected
Button hover
brighten background + shadow
Text-over-image halo
not detected
Heading tracking
not detected
Label tracking
not detected
Focus ring
not detected
Easing
not detected
Container max
1178px
Section padding
70px
Accent gradient
not detected
Icon stroke
not detected
Spacing unit
not detected
Transition
800ms
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
#000000
field fill
#000000
field text
#ffffff
focus
#000000
submit
#000000
Captured from
sydneymobiledetailing.com.au/ (home page)
Fields
5 · multi-column
Field border
1px solid #000000
Field radius
0px
Field height
44px
Field padding
10px 12px 10px 12px
Field font
Poppins 16px
Field shadow
rgba(0, 0, 0, 0) 0px 0px 0px 1px
Focus state
none
Label
300 12px
Submit
"Get Your QuoteGet Your Quote" · #000000 · radius 0px
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
13 of 27 values captured from this site. The rest fall back to library defaults — shown so nothing hardcoded can pass as captured.
Components observed vs gaps (gaps left empty — never auto-filled)
navobserved
heroobserved
buttonsobserved
cardobserved
pricingGAP
testimonialobserved
feature-gridGAP
galleryobserved
accordion-faqGAP
tabsobserved
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 →
will-change (perf)300×
object-fit130×
mix-blend-mode116×
CSS mask110×
filter (blur etc.)53×
sticky positioning40×
conic-gradient10×
scroll-snap10×
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.