Brittany Chiang

Personal PortfolioVisit sitebrittanychiang.com

A dark, readable portfolio keeps identity in one column and detailed evidence in the other.

Brittany Chiang — captured interface — Page capture · scroll inside to explore

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

Why this pattern works

Helping a hiring manager scan experience, project outcomes, and the full résumé without a long introductory funnel. Selection is based on observable design and conversion paths; conversion rates have not been independently verified.

Design notes

Mood: Engineer Portfolio. A dark, readable portfolio keeps identity in one column and detailed evidence in the other.
Colors: Deep navy with pale text, muted blue-gray secondary copy, and turquoise tags.
Type: Clear sans-serif hierarchy with compact dates and strong project headings.
Layout: Persistent identity and section navigation at left; biography, experience, and projects form a long right column.
Motion: Keep navigation and reading immediate; motion should support the work rather than delay access.
Texture: Subtle light, thin separations, and small project thumbnails.
Imagery: Use actual product screenshots and concise role descriptions.
Don't: Avoid burying experience behind full-screen transitions or substituting skill meters for evidence.

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: Brittany Chiang
Source: https://brittanychiang.com/
Swipefile reference: https://swipefile.design/ref/personal-brittany-chiang/
Captured: 2026-09-05. This is a dated reference, not a claim about the current live product.

## 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: Engineer Portfolio. A dark, readable portfolio keeps identity in one column and detailed evidence in the other.
- colors: Deep navy with pale text, muted blue-gray secondary copy, and turquoise tags.
- typography: Clear sans-serif hierarchy with compact dates and strong project headings.
- layout: Persistent identity and section navigation at left; biography, experience, and projects form a long right column.
- motion: Keep navigation and reading immediate; motion should support the work rather than delay access.
- texture: Subtle light, thin separations, and small project thumbnails.
- dont: Avoid burying experience behind full-screen transitions or substituting skill meters for evidence.

Useful for: Helping a hiring manager scan experience, project outcomes, and the full résumé without a long introductory funnel. 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.

Brittany Chiang

Make it your own

Keep exploring