Now let me read the existing project files to understand the structure before building.

Let me check the input, badge, and sonner components since I'll need them.

Now I have all the context I need. Let me build this password change interface with a clean, modern SaaS settings aesthetic. I'll create the components and update the theme.

Now let me create the settings sidebar layout and the password change components.

Now let me create the main password change form component that handles both scenarios:

Now let me create the main page that ties everything together with a toggle to demo both states:

Now let me also update the tailwind config to add the custom tokens:

The implementation is complete. Here's what I built:

Password Change Interface for SaaS Platform — a clean settings panel with two distinct flows unified into one interface:

1. Password users see a straightforward form: verify current password → enter new password → confirm. They also get a "Reset via email" fallback link if they forgot their current password.
2. OTP-only users follow a guided 2-step flow: first verify identity via a 6-digit email code (with countdown timer and resend), then create their new password. Steps are visually numbered, and the password fields stay disabled until verification completes.

Both flows share the same password strength indicator (5-segment bar with a checklist for uppercase, lowercase, numbers, special characters, and length), real-time confirm-password matching feedback, and a success animation on completion. A demo toggle at the top lets you switch between the two user types to see both experiences.