shadcn/ui v3 — Account preferences

Forms & OnboardingSee it livev3.shadcn.com

Account preferences pair personal details with date and language controls in a short settings form.

shadcn/ui v3 — Account preferences — captured interface — Page excerpt · scroll inside to explore

Public demo · 2026-09-04Open full image ↗

Forms & onboarding Navigation

Why this pattern works

Keep personal details and locale preferences together while explaining how each value is used.

Design notes

Surface: Account preferences
Navigation: Account is selected in the persistent settings list alongside profile and appearance.
Layout: A local navigation rail sits beside a constrained form for name, date of birth, and preferred language.
Density: A constrained form column leaves room between groups while keeping labels and controls together.
Color: White surfaces, subtle borders, and a dark update action.
Type: Keep short fields aligned and place helper text directly below its control.
Pattern: Keep personal details and locale preferences together while explaining how each value is used.
States: Public v3 account-settings demo with sample fields; no personal data was submitted.
Don't: Adapt the interaction pattern to your own product. Do not copy brand assets, sample identities, proprietary text, or assume unseen states. Specify keyboard behavior, loading, empty, error, and narrow-screen layouts for your implementation.

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: shadcn/ui v3 — Account preferences
Source: https://v3.shadcn.com/examples/forms/account
Swipefile reference: https://swipefile.design/ref/shadcn-account/
Captured: 2026-09-04. This is a dated reference, not a claim about the current live product.
Capture scope: a page excerpt. Do not infer unseen sections or interactions.

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

## Reference notes
- surface: Account preferences
- nav: Account is selected in the persistent settings list alongside profile and appearance.
- layout: A local navigation rail sits beside a constrained form for name, date of birth, and preferred language.
- density: A constrained form column leaves room between groups while keeping labels and controls together.
- color: White surfaces, subtle borders, and a dark update action.
- typography: Keep short fields aligned and place helper text directly below its control.
- pattern: Keep personal details and locale preferences together while explaining how each value is used.
- states: Public v3 account-settings demo with sample fields; no personal data was submitted.
- dont: Adapt the interaction pattern to your own product. Do not copy brand assets, sample identities, proprietary text, or assume unseen states. Specify keyboard behavior, loading, empty, error, and narrow-screen layouts for your implementation.

Useful for: Keep personal details and locale preferences together while explaining how each value is used.

## 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 interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

Useful for: Keep personal details and locale preferences together while explaining how each value is used.

shadcn/ui v3 — Account preferences

Make it your own

Keep exploring