Seán Halpin

Personal PortfolioVisit siteseanhalpin.software

A playful canvas places a personal introduction among examples of software design.

Seán Halpin — captured interface — Viewport capture · opening screen

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

Why this pattern works

Making the work itself explorable while keeping a short introduction, Say Hi action, and CV route accessible. Selection is based on observable design and conversion paths; conversion rates have not been independently verified.

Design notes

Mood: Canvas Portfolio. A playful canvas places a personal introduction among examples of software design.
Colors: Bright blue, pink, yellow, dark panels, and light software surfaces.
Type: Friendly sans-serif text inside a compact introductory panel.
Layout: An explorable field of project panels replaces a conventional long landing page.
Motion: The page invites visitors to move around its canvas; include accessible alternatives to spatial exploration.
Texture: Rounded software windows and colorful interactive objects.
Imagery: Use real interface work with distinct silhouettes and readable labels.
Don't: Do not rely on dragging alone; keep contact and résumé links easy to reach.

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: Seán Halpin
Source: https://www.seanhalpin.software/
Swipefile reference: https://swipefile.design/ref/personal-sean-halpin/
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: Canvas Portfolio. A playful canvas places a personal introduction among examples of software design.
- colors: Bright blue, pink, yellow, dark panels, and light software surfaces.
- typography: Friendly sans-serif text inside a compact introductory panel.
- layout: An explorable field of project panels replaces a conventional long landing page.
- motion: The page invites visitors to move around its canvas; include accessible alternatives to spatial exploration.
- texture: Rounded software windows and colorful interactive objects.
- dont: Do not rely on dragging alone; keep contact and résumé links easy to reach.

Useful for: Making the work itself explorable while keeping a short introduction, Say Hi action, and CV route accessible. 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.

Seán Halpin

Make it your own

Keep exploring