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
#4a017d
pri-accent
#f0047f
secondary
—
sec-accent
—
Surfaces — page · alt · emphasis · inverse
page
#ffffff
alt
—
emphasis
—
inverse
—
btn hover
#4a017d
Heading font
Montserrat (Google)
Body font
Montserrat (Google)
Heading line-height
0.93
Mobile h1
55px → 48px ⚠ big
Mobile overflow
none
Base size
15px
Type scale
not detected
Rounding
Sharp (0px)
Line width
not detected
Button hover
subtle / none
Text-over-image halo
not detected
Heading tracking
not detected
Label tracking
not detected
Focus ring
not detected
Easing
not detected
Container max
1260px
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
#cccccc
field fill
#ffffff
field text
#333333
focus
#cccccc
submit
#f0047f
Captured from
huntervdigital.com.au/ (home page)
Fields
5 · single-column
Field border
1px solid #cccccc
Field radius
2px
Field height
38px
Field padding
6px 10px 6px 10px
Field font
Montserrat 16px
Field shadow
not detected
Focus state
none
Label
700 16px
Submit
"Submit" · #f0047f · 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
12 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
heroGAP
buttonsobserved
cardGAP
pricingGAP
testimonialobserved
feature-gridobserved
galleryobserved
accordion-faqobserved
tabsobserved
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-fit38×
mix-blend-mode12×
filter (blur etc.)12×
scroll-behavior12×
will-change (perf)6×
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.