teenage.engineering

Consumer TechDark

Dieses Design mit KI nutzen

Wähle deine KI, beschreibe deine Idee und sende den Prompt.

  • Füge den Prompt in den Agenten-Chat deines Projekts in Claude Code ein und sende ihn.

Herunterladen

Stile übernehmen

Wähle die Stile für deine Website aus und kopiere dann den Prompt.

Von der Inspiration zur Oberfläche

Sieh, wie aus der Designsprache dieser Website eine eigene Oberfläche entsteht. Nutze den Prompt für deine eigene Idee.

Website als Referenz

Von Stylepack generierte UI

Erstelle etwas Ähnliches

Kopiere den Start-Prompt in deinen Coding-Agenten oder passe ihn an deine Idee an.

Use the teenage.engineering design pack from Stylepack so what you build looks and behaves like https://teenage.engineering/.

Farben

2 Farben

Komponenten

search
Button ghost
#f1f2f2 Text auf transparent über #000000, r 0px, h 32px, 16px/100
Link
#f1f2f2, ohne Unterstreichung, 100
Header
0px, absolute, 12 Links mit 16px
Formulare
0 forms, 4 inputs. Required markers: 0. Help texts: 0. Label placement: other (1).
Icons
Icons: 3 inline SVGs, outline/stroke, sizes 35px, stroke 1px; icon font classes icon-.

Interaktion und Animation

  • nav link "teenage engineering": keine Hover-Änderung
  • Tooltips: Tooltip triggers exist (3 × title) but none opened on hover in the first viewport; title attributes fall back to the browser's native tooltip.
  • Menüs: No dropdown menus found in the header.
  • Animationen: 9 elements carry transitions; typical 0.15s with ease, mostly on background-color, opacity, color. No running keyframe animations at rest. 6 sizable elements sit at opacity 0 before scrolling: scroll-reveal animations are in use (reveal on enter, fade + rise is the usual recipe).

Typografie

1 Schriftfamilie
te-20Selbst gehostet
headline-displayQuick brown fox48px / 100 / lh 1.4
headline-lgQuick brown fox32px / 100 / lh 1.4
headline-mdQuick brown fox24px / 100 / lh 1.4
body-mdThe quick brown fox jumps over the lazy dog19.102px / 100 / lh 22.0408px
label-mdThe quick brown fox jumps over the lazy dog16px / 300 / lh 24px
buttonThe quick brown fox jumps over the lazy dog16px / 100 / lh 1.5
Verwendete Größen

Abstände

4px Einheit
3268
Inhaltsbreite
1308px

Radius

Button 0pxEingabe 0pxKarte 0pxBild 0px

Schatten

0

Flach: keine Box-Shadows verwendet.

Theme

The site is dark by default and no light mode responded to prefers-color-scheme, a theme toggle, or a root class/attribute.

Logo und Icons

3 Referenzen

Diese Ausschnitte und ihre Maße stehen in BRAND.md. Prüfe, ob das richtige Logo erkannt wurde, bevor du das Paket nutzt.

Komponenten-Inventar

8 von 87 Arten · 11 Varianten · 2 Zustände · 1 Overlays

Jede Zeile zeigt eine auf der Seite gefundene visuelle Variante. Aufnahmen zeigen die bei der Extraktion erreichten Zustände. Fehlende Aufnahmen und nicht live geprüfte Zustände werden getrennt gekennzeichnet. Details in COMPONENTS.md und components.css.

Auf der WebsitePro

Sieh jede Komponente im Kontext ihrer ursprünglichen Seite.

Mit Pro freischalten
Button, ghost (sm)1 auf der Seite, z. B. „search“#f1f2f2 text on transparent, radius 0px, h 15px, padding 0px 0px 0px 0px, 16px/100
Mit Pro verfügbarAuf der Website
Button, ghost (sm), Restrest
hover, focus (keyboard), active (pressed), disabled: keine Änderung
Button, ghost1 auf der Seite, z. B. „search“ · partially outside the capture viewport#f1f2f2 text on transparent, radius 0px, h 32px, padding 0px 0px 0px 0px, 16px/100
Diese Aufnahme enthält keine Website-Vorschau. Versuche eine neue Extraktion.Auf der Website
rest: Vorschau nicht verfügbar
Button, ghost (lg)1 auf der Seite, z. B. „search“ · partially outside the capture viewport#f1f2f2 text on transparent, radius 0px, h 44px, padding 0px 0px 0px 0px, 16px/100
Diese Aufnahme enthält keine Website-Vorschau. Versuche eine neue Extraktion.Auf der Website
rest: Vorschau nicht verfügbar
Field label, other1 auf der Seite, z. B. „country or regionunited stat“16px/300 #e5e5e5, other the field, margin-bottom 0px, lowercase
Mit Pro verfügbarAuf der Website
Field label, other, Restrest
Navigation link, plain22 auf der Seite, z. B. „teenage engineering“ · partially outside the capture viewport#f1f2f2, no underline, 16px/100
Diese Aufnahme enthält keine Website-Vorschau. Versuche eine neue Extraktion.Auf der Website
rest: Vorschau nicht verfügbar
Footer1 auf der Seite, z. B. „country or regionunited stat“h 96px, bg #000000, 1 link columns, 7 links
Diese Aufnahme enthält keine Website-Vorschau. Versuche eine neue Extraktion.Auf der Website
rest: Vorschau nicht verfügbar
Footer link, plain7 auf der Seite, z. B. „newsletter“#e5e5e5, no underline, 16px/300
Mit Pro verfügbarAuf der Website
Footer link, plain, Restrest Footer link, plain, Hoverhover
Dialog / modal1 auf der Seite, z. B. „in cart“ · partially outside the capture viewport47×90px, bg transparent, #000000, border none, radius 0px, padding 0px 0px 0px 0px
Diese Aufnahme enthält keine Website-Vorschau. Versuche eine neue Extraktion.Auf der Website
rest: Vorschau nicht verfügbar
Image / figure, aspect-14 auf der Seite · covered by div.box1440×1440px, aspect 1, radius 0px, object-fit fill
Diese Aufnahme enthält keine Website-Vorschau. Versuche eine neue Extraktion.Auf der Website
rest: Vorschau nicht verfügbar
Image / figure, aspect-29.671 auf der Seite1308×44px, aspect 29.67, radius 0px, object-fit fill
Mit Pro verfügbarAuf der Website
Image / figure, aspect-29.67, Restrest
hover: keine Änderung
Icon, outline-35px1 auf der Seite · covered by select._country-select_11j21_135×19px, outline, stroke 1px none
Diese Aufnahme enthält keine Website-Vorschau. Versuche eine neue Extraktion.Auf der Website
rest: Vorschau nicht verfügbar
Dialog / modal 1geöffnet durch button "search" bei click, schließt mit Escape617×95px, top centered, bg rgba(0, 0, 0, 0.9), text #f5f5f5 16px, radius 26.4489px, padding 0px 0px 0px 0px, no shadow, backdrop transparent, 1 input(s), closes on Escape
Mit Pro verfügbarAuf der Website
Dialog / modal 1offen

Nicht auf dieser Seite: Icon button, Toggle / segmented control, Button group, Text link, Floating action button, Close / dismiss button, Text input, Search field, Textarea, Select (native), Combobox / custom select, Checkbox, Radio, Switch / toggle, Range slider, File input / dropzone, Date / time input, Input with attached button or addon, Help / hint text, Validation error text, Fieldset / form section, Header / navbar, Menu / dropdown trigger, Breadcrumb, Tabs, Pagination, Stepper / progress steps, Sidebar navigation, Skip link, Back to top, Social icon links, Theme toggle, Language / region switch, Tooltip, Popover, Dropdown menu, Drawer / sheet / off-canvas, Toast / snackbar, Banner / announcement bar, Cookie / consent notice, Lightbox / media viewer, Badge / pill / tag, Chip (removable / selectable tag), Alert / callout, Progress bar, Spinner / loader, Skeleton / shimmer, Counter / notification dot, Empty state, Rating / stars, Card, Pricing card / plan, Feature item (icon + title + text), Testimonial / quote card, Stat / metric, Styled list, List row / menu row, Table, Table row, Accordion / disclosure, Avatar, Avatar stack, Divider, Code block / inline code, Keyboard key, Blockquote, Video / media embed, Carousel / slider, Logo strip, Eyebrow / kicker, FAQ block, Call-to-action band, Newsletter / signup form, Search results / listing row, Hero, Section band, Content container, Grid of items, Sticky bar.

Responsive

1440 / 1024 / 768 / 390 px
ViewportInhaltGutterFließtextÜberschriftHeaderHeroRasterButtons
desktop 14401308px16px0px, 22 linkscontent-width
laptop 1024930px16px0px, 22 linkscontent-width
tablet 768697px16px0px, 22 linkscontent-width
phone 390354px16px0px, 0 links3→3 col1 full-width
  • No navigation links or hamburger detected at 390px; mobile navigation behavior is unverified.
  • Body text is 16px at the sampled desktop and phone widths.
  • 1 buttons stretch full-width on phones.

Dateien im Paket

62 Dateien

Starte mit 30 kB Anleitungstext. Der gesamte Text im Paket umfasst 305 kB; öffne die Detaildateien bei Bedarf. Bilder kommen hinzu.

START_HERE.md86 Zeilen
# Start here: teenage.engineering

Observed 2026-10-28T01:08:18.647Z; default dark 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 `MEDIA.md` before choosing or generating imagery. Preserve the reference's art direction while adapting the subject to the new product. Inspect actual candidate images against the reference and check their desktop and phone crops in the rendered UI. Photography must not silently become geometric illustration; unresolved assets must be reported.
4. 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.
5. Before drawing any logo or icon, read `BRAND.md` and open `screenshots/brand-logo.png`, `screenshots/brand-icon-1.png`, `screenshots/brand-favicon-source.png`: for a new product, create an original mark with the observed proportions and treatment; never guess a shape from a label.
6. 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 was not detected in this capture; do not invent a source measurement.
7. 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.
8. 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.
9. `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.
10. `DESIGN.md` has the whole system when a value is missing above. `evidence.json` is diagnostic data: never in the first read.
11. 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.
12. For another site's design, use the enabled Stylepack MCP tools: query_components for specific controls or get_design_pack for broader visual context. Without MCP, fetch https://stylepack.ai/packs/<host>/pack.zip; one question at a time is at https://stylepack.ai/packs/<host>/fonts, /colors and /buttons. Preserve explicit source pages and report missing evidence.

## 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: 1308px. Inferred spacing base: 4px; sampled scale: 32, 68px. Observed CSS breakpoints: not detected.
Colors: background=#000000; foreground=#f1f2f2.
Radii: button 0px, card 0px, input 0px, image 0px.
Shadows: none observed.

## 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.
- te-20: observed weights 100, 300; source loading recipe in fonts.css.
- te-20 delivery by face: confirmed none; failed 100 normal, 300 normal; 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: te-20; 48px/1.4; weight 100; tracking normal; fallback, source h1, inferred fields: fontSize, fontFamily, fontWeight, lineHeight.
- headline-lg: te-20; 32px/1.4; weight 100; tracking normal; fallback, source h2, inferred fields: fontSize, fontFamily, fontWeight, lineHeight.
- headline-md: te-20; 24px/1.4; weight 100; tracking normal; fallback, source h3, inferred fields: fontSize, fontFamily, fontWeight, lineHeight.
- body-md: te-20; 19.102px/22.0408px; weight 100; tracking normal; observed, source body.
- label-md: te-20; 16px/24px; weight 300; tracking normal; observed, source label.
- button: te-20; 16px/1.5; weight 100; tracking normal; observed, source button.
- Font te-20: 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: 1440×1440px at page (0, 0); 1 measured layers, 0 icon samples, 1 opaque media layers. screenshots/region-r1-context.jpg, screenshots/region-r1-detail.png
- r2: 1440×1440px at page (0, 1440); 1 measured layers, 0 icon samples, 1 opaque media layers. screenshots/region-r2-context.jpg, screenshots/region-r2-detail.png
- r3: 1440×1440px at page (0, 2880); 1 measured layers, 0 icon samples, 1 opaque media layers. screenshots/region-r3-context.jpg, screenshots/region-r3-detail.png

## Component recipes

- ghost button: bg transparent; text #f1f2f2; border none; radius 0px; height 32px; padding 0px 37px; type 16px/100; shadow none.

## Responsive and interaction evidence

- desktop 1440px: content 1308px, gutter , H1 , header 0px, 22 links, grids .
- laptop 1024px: content 930px, gutter , H1 , header 0px, 22 links, grids .
- tablet 768px: content 697px, gutter , H1 , header 0px, 22 links, grids .
- phone 390px: content 354px, gutter , H1 , header 0px, 0 links, grids 3→3 col.
No navigation links or hamburger detected at 390px; mobile navigation behavior is unverified.
Body text is 16px at the sampled desktop and phone widths.
1 buttons stretch full-width on phones.
- Hover nav-link: no visible change.
9 elements carry transitions; typical 0.15s with ease, mostly on background-color, opacity, color. No running keyframe animations at rest.
No alternate theme verified.

## Logo and icons

Logo lockup: 163×70px, external image or text; inspect crop. See BRAND.md and its crops for shape evidence.
Icon: 36×20px; outline/stroke; stroke 1px, caps butt.

## First images to open

- screenshots/desktop-1440-fold.png: Desktop 1440, above the fold
- screenshots/brand-logo.png: primary logo lockup
- 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.
Page background comes from body; large surface colors remain in the palette.