holographik.space

# Start here: holographik.space

Observed 2026-10-28T00:36:55.609Z; default light theme. This is a compact handoff, not the full evidence archive: everything you need to start is here, the detailed files are one step away.

## How to use this pack

1. Read `START_HERE.md` and `tokens.css` first: the priority values. Keep observed values; a value marked inferred or fallback is a suggestion to resolve against the screenshots.
2. Open `screenshots/desktop-1440-fold.png` and `screenshots/phone-390-fold.png` and match the composition, density, whitespace and image treatment; the values do not carry those. Treat the inside of an image or canvas as a visual inference, not measured DOM.
3. Read `FONTS.md` and load `fonts.css` before `tokens.css`. Keep exact weights and variable-font settings and verify the fonts that actually render. If a font is unavailable, name the substitute and compare its width and apparent weight before touching the type scale.
4. Before drawing any logo or icon, read `BRAND.md` and open `screenshots/brand-icon-1.png`, `screenshots/brand-favicon-source.png`, `screenshots/brand-favicon.png`: for a new product, create an original mark with the observed proportions and treatment; never guess a shape from a label.
5. Before building any control, read `COMPONENTS.md` (every variant and measured state, with a crop of each), use `components.css` for the CSS and `demos/` for a live copy of each component. A component listed as not found does not exist on the site; do not invent it.
6. Read `REGIONS.md` and inspect its context, detail and icon crops: reconstruct outer and inner surfaces, per-layer gradients and shadows and group spacing (`regions.css` has the recipes), then check the whole page again.
7. Read `BEHAVIOR.md` for hover, focus, tooltips, menus, motion, scrolling, tables, forms, text and each breakpoint, and reproduce the behaviour, not only the colours. No alternate theme was verified; use the observed theme unless another is requested.
8. `layout.html` is a generic page composed only from this pack's measured values, with placeholder copy: open it to see the colours, type, recipes and spacing working together and to check your own wiring of the fonts and tokens against it. It is not the site's composition; the screenshots are.
9. `DESIGN.md` has the whole system when a value is missing above. `evidence.json` is diagnostic data: never in the first read.
10. When done, render at desktop, 390px and 320px, compare with the screenshots, fix the biggest visible mismatch first (usually type size, whitespace or image treatment), recheck keyboard focus, overflow, navigation and forms, and repeat.
11. For another site's design, run `npx stylepack-cli <host>` in the project (it downloads that pack and records it the same way), or fetch https://stylepack.ai/packs/<host>/pack.zip; one question at a time is at https://stylepack.ai/packs/<host>/fonts, /colors and /buttons.

## Priority values and evidence

Values labeled fallback were not observed for that role; inferred-role means a visible heading was mapped to a display role. Keep observed values, but treat fallbacks as suggestions.
Keep measured sizes, tracking, radii and colors unless the new content requires an explicit adaptation. Do not enlarge the headline simply to fill a different line length.
Content width: not detected. Inferred spacing base: 4px; sampled scale: 4, 8, 12, 16, 20, 28px. Observed CSS breakpoints: 640, 760, 761, 900, 901px.
Colors: background=#ffffff; surface=#f1f1f1; surface-2=#c8c8c8; foreground=#ffffff; primary=#000000; on-primary=#ffffff; border=#ffffff.
- primary: Selected from measured button, link, text, painted-area and theme colors. It is not proof of a filled primary button; follow the observed component recipes.
Radii: button 9999px, card 0px, input 0px, image 0px.
Shadows: rgba(0, 0, 0, 0.28) 0px 8px 30px 0px.

## Typography

Load fonts.css before applying tokens.css. FONTS.md contains the observed face/weight inventory and rendered-font checks. A CSS family name alone does not load a font.
Copy the supplied @font-face sources verbatim; do not replace a captured face with Google Fonts merely because its name looks similar. Keep fonts.css linked (or inline it verbatim for a single HTML deliverable). It includes measured semantic font defaults; tokens.css supplies scale and spacing. Use each role as a complete recipe: family, exact numeric weight, size, line height, tracking, font-feature-settings (including cv/ss stylistic sets), optical sizing and variable-font settings. A font shorthand resets feature settings; reapply the supplied longhands after it. Do not round 510 to 500/600, or turn a measured light style into a bold heading.
Use the captured family first. Self-hosted is a hosting location, not an availability verdict. An unverified probe is not evidence of failure; do not choose the optional fallback merely because it is familiar. Substitute only after an actual failed destination request or missing licensed source; record that reason and the replacement. A transient network error merits a retry before redesigning the typography.
Fallback roles are unmeasured suggestions. If a role is absent, start from the nearest observed text treatment; do not assume headings must be bold.
- KH Teka: observed weights 400, 500, 700; source loading recipe in fonts.css.
- KH Teka delivery by face: confirmed 400 600 normal; failed none; unverified none. Confirmation is from one isolated-origin check, not every deployment. Keep confirmed faces; attempt unverified faces. A failed unused face does not invalidate a working regular/bold face.
After loading, inspect the browser's Rendered Fonts for the headline, body and button. Computed font-family/font-weight and document.fonts.check() alone do not prove which face drew the glyphs.

- headline-display: KH Teka; 26px/32.5px; weight 700; tracking 0.052px; observed, source h1.
- headline-lg: KH Teka; 69.12px/65.664px; weight 500; tracking -1.52064px; observed, source h2.
- headline-md: KH Teka; 24px/1.4; weight 400; tracking normal; fallback, source h3, inferred fields: fontSize, fontFamily, fontWeight, lineHeight.
- body-md: KH Teka; 13px/15px; weight 400; tracking 0.052px; observed, source body.
- label-md: KH Teka; 12px/1.17; weight 400; tracking 0.052px; observed, source label.
- button: KH Teka; 13px/15px; weight 500; tracking normal; observed, source button.
- Font KH Teka: self-hosted; use its captured loader first. Self-hosted does not imply unavailable or licensed for reuse; substitution is conditional, not a second design choice.

## Regional composition

Read REGIONS.md and open the referenced context, detail and icon crops before drawing complex previews. Build outer shell, inset content panel and internal groups as distinct layers where observed. Preserve which surface owns each gradient, border and shadow; do not apply one generic card treatment to every layer.
For images, canvas, video and external SVG, use the rendered crops to infer visible internal groupings. Keep those inferences separate from measured DOM facts. Do not treat an illustration as a functional app or paste the screenshot as the finished UI. Return to the whole-page screenshots to match scale and placement.
- r1: 1425×900px at page (0, 450); 1 measured layers, 0 icon samples, 1 opaque media layers. screenshots/region-r1-context.jpg, screenshots/region-r1-detail.png
- r2: 1425×900px at page (0, 1350); 5 measured layers, 0 icon samples, 1 opaque media layers. screenshots/region-r2-context.jpg, screenshots/region-r2-detail.png
- r3: 1425×900px at page (0, 2250); 5 measured layers, 0 icon samples, 1 opaque media layers. screenshots/region-r3-context.jpg

## Component recipes

- primary button: bg #000000; text #ffffff; border none; radius 9999px; height 29px; padding 7px 14px; type 13px/500; shadow none.
- secondary button: bg #f1f1f1; text #000000; border none; radius 0px; height 27px; padding 6px 12px; type 13px/500; shadow none.

## Responsive and interaction evidence

- desktop 1440px: content fluid, gutter 19px, H1 26px, 0 lines, start, header 56px, 5 links, 2 CTA, grids 3→3 col.
- laptop 1024px: content fluid, gutter 19px, H1 26px, 0 lines, start, header 56px, 5 links, 2 CTA, grids 3→3 col.
- tablet 768px: content fluid, gutter 19px, H1 28px, 0 lines, start, header 54px, 5 links, 2 CTA, grids .
- phone 390px: content fluid, gutter 9px, H1 28px, 0 lines, start, header 52px, 5 links, 2 CTA, grids .
H1 goes 26px → 28px (108%), 0 → 0 lines.
No hamburger observed at 390px; 5 navigation links remain visible.
Body text 13px → 14px.
Phone side gutter 9px.
- Hover button-primary: no visible change.
- Hover button-secondary: background transparent → #ffffff1a, text #b7b7b2 → #ffffff, icon/inner colour → #ffffff.
- Hover nav-link: opacity 1 → 0.55.
- Focus button-primary: outline 2px solid rgb(0, 0, 0), offset 2px.
57 elements carry transitions; typical 0.15s with ease, mostly on opacity, color, background. No running keyframe animations at rest.
No alternate theme verified.

## Logo and icons

Logo not confidently located.
Icon: 13×13px; outline/stroke; stroke 1.3px, caps round.

## First images to open

- screenshots/desktop-1440-fold.png: Desktop 1440, above the fold
- screenshots/phone-390-fold.png: Phone 390, above the fold

## Verify the build

Render at desktop, 390px and 320px. Inspect the result, compare against the supplied references, fix the largest visible mismatch, and recheck keyboard focus, overflow, navigation and form behavior. Match the visual language while following the requested product content.