Adam Savage — Tested

Personal CreatorVisit sitetested.com

A compact white navigation bar and red wordmark frame a wide workshop photograph, followed immediately by a concise introduction to the video channel.

Adam Savage — Tested — captured interface — Viewport capture · opening screen

Source capture · 2026-09-08Open full image ↗

Personal websites

Why this pattern works

A engineering creator website; study its opening composition, identity, and paths into the creator’s work.

Design notes

Mood: Practical and documentary.
Colors: White, black, and red with warm workshop photography.
Type: The captured page uses refrigerator-deluxe. Keep a clear contrast between the main statement and the smaller navigation.
Layout: A compact white navigation bar and red wordmark frame a wide workshop photograph, followed immediately by a concise introduction to the video channel.
Motion: Static viewport capture. Inspect the source website to assess animation, video, and reduced-motion behavior.
Texture: Let the original photographic or video imagery carry the visual detail.
Imagery: The screenshot documents the original live website. Use your own approved photography, illustration, and brand assets when adapting the composition.
Don't: Do not reproduce the creator’s identity, claims, copy, or artwork in a new brand.

Make it your own

Turn this reference into a useful brief for your project. Copy it into the AI tool you already use.

Your project

Use withI want to

Tech stack

Add constraints

What should the tool respect?

Preview & edit prompt

Prompt text

# My project
[Describe the product, audience, and screen you want to improve]

Stack: Use the existing project stack
Task: Implement the interface and verify the result in the existing project.

## Tool guidance (Any AI tool)
Use available project tools to inspect, implement, and test. State any unavailable capabilities.

# Design reference: Adam Savage — Tested
Source: https://www.tested.com/
Swipefile reference: https://swipefile.design/ref/youtube-adam-savage/
Captured: 2026-09-08. This is a dated reference, not a claim about the current live product.
Capture scope: one viewport. Do not infer unseen page sections or a complete user flow.

## Objective
Adapt the visual principles below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- mood: Practical and documentary.
- colors: White, black, and red with warm workshop photography.
- typography: The captured page uses refrigerator-deluxe. Keep a clear contrast between the main statement and the smaller navigation.
- layout: A compact white navigation bar and red wordmark frame a wide workshop photograph, followed immediately by a concise introduction to the video channel.
- motion: Static viewport capture. Inspect the source website to assess animation, video, and reduced-motion behavior.
- texture: Let the original photographic or video imagery carry the visual detail.
- dont: Do not reproduce the creator’s identity, claims, copy, or artwork in a new brand.

Useful for: A engineering creator website; study its opening composition, identity, and paths into the creator’s work.

## Acceptance criteria
- Existing project conventions, design tokens, working functionality, and unrelated changes are preserved.
- Two or three reference principles clearly support the user's task; conflicts are resolved in favor of usability and the existing product.
- Reusable components and semantic HTML express the interface. Available licensed assets are used; important UI text is never rendered as a bitmap.
- Every visible control has a defined behavior. Loading, empty, error, success, disabled, and long-content states are specified where relevant. Demo data is clearly labeled.
- Navigation and content adapt at 375px, 768px, and 1440px without horizontal page overflow. Keyboard use, visible focus, labeled inputs, at least 44px touch targets, readable contrast, and reduced motion are supported.
- Verification distinguishes rendered behavior from proposals and identifies anything still requiring a backend or external service.

## Quality bar
Clear hierarchy, consistent spacing, restrained surfaces, and purposeful motion. Avoid decorative gradients, excessive cards, placeholder buttons, and invented metrics unless the project calls for them. Do not claim a feature is connected or tested without evidence.

Assembled in your browser. No API key or AI request needed. Changing the fields refreshes the preview.

## Objective
Adapt the visual principles below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

Useful for: A engineering creator website; study its opening composition, identity, and paths into the creator’s work.

Adam Savage — Tested

Make it your own

Keep exploring

Help improve Swipefile?