Rauno Freiberg

An oversized typographic card and saturated yellow circle announce an interaction designer’s craft.

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

Why this pattern works

Inviting visitors into interactive work, writing, and contact. Best for a designer whose execution itself is part of the hiring evidence. Selection is based on observable design and conversion paths; conversion rates have not been independently verified.

Design notes

Mood: Interactive Designer Portfolio. An oversized typographic card and saturated yellow circle announce an interaction designer’s craft.
Colors: Light gray and white with black type and a strong yellow accent.
Type: Large left-aligned sans-serif identity text with tiny supporting navigation.
Layout: A horizontal, card-like opening composition that leads toward work and supporting destinations.
Motion: The live composition extends horizontally; preserve clear navigation and support reduced motion.
Texture: Simple geometric shapes and generous empty space.
Imagery: Use original interface experiments and project documentation.
Don't: Provide a clear route to projects and email even when the visual navigation is experimental.

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: Rauno Freiberg
Source: https://rauno.me/
Swipefile reference: https://swipefile.design/ref/personal-rauno-freiberg/
Captured: 2026-09-05. 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: Interactive Designer Portfolio. An oversized typographic card and saturated yellow circle announce an interaction designer’s craft.
- colors: Light gray and white with black type and a strong yellow accent.
- typography: Large left-aligned sans-serif identity text with tiny supporting navigation.
- layout: A horizontal, card-like opening composition that leads toward work and supporting destinations.
- motion: The live composition extends horizontally; preserve clear navigation and support reduced motion.
- texture: Simple geometric shapes and generous empty space.
- dont: Provide a clear route to projects and email even when the visual navigation is experimental.

Useful for: Inviting visitors into interactive work, writing, and contact. Best for a designer whose execution itself is part of the hiring evidence. Selection is based on observable design and conversion paths; conversion rates have not been independently verified.

## 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.

Rauno Freiberg

Make it your own

Keep exploring