Next.js 15 & TS Enterprise Architect

1. Dependency Analysis: Requires 'zod' for validation. No database schema changes; assumes an existing db utility.
2. Component & Folder Structure: src/app/actions/user-actions.ts and src/lib/validations/user-schema.ts.
3. Data Flow Boundary: Server Action executed via a Client Component form.

Implementation

// Location: src/lib/validations/user-schema.ts
// Context: Zod schema for user profile validation
import { z } from "zod";

export const UserUpdateSchema = z.object({
  id: z.string().uuid(),
  displayName: z.string().min(2).max(50),
  bio: z.string().max(160).optional(),
});

export type UserUpdateInput = z.infer<typeof UserUpdateSchema>;

// Location: src/app/actions/user-actions.ts
// Context: Server Action for secure enterprise handling
"use server";

import { UserUpdateSchema, type UserUpdateInput } from "@/lib/validations/user-schema";
import { db } from "@/lib/db";

interface ActionResponse<T> {
  success: boolean;
  data?: T;
  error?: string;
}

export async function updateUserProfile(
  payload: UserUpdateInput
): Promise<ActionResponse<{ id: string }>> {
  try {
    const validatedFields = UserUpdateSchema.parse(payload);

    const updatedUser = await db.user.update({
      where: { id: validatedFields.id },
      data: {
        name: validatedFields.displayName,
        bio: validatedFields.bio,
      },
    });

    return {
      success: true,
      data: { id: updatedUser.id },
    };
  } catch (err) {
    if (err instanceof Error) {
      return {
        success: false,
        error: err.message,
      };
    }
    return {
      success: false,
      error: "An unknown error occurred while updating the profile.",
    };
  }
}

Next steps

• Import updateUserProfile into your Client Component.
• Use useActionState to handle the standardized response and loading states.
• Ensure the user ID is passed securely from a session-verified source.