## KriContact Front Repository Rules ### Product Purpose and Current Phase - This is the launched Next.js frontend for KRI contact operations. Preserve first-release behavior while planning and delivering approved follow-up features. - The primary workflows include project and contact-list management, interviewer and list assignment, call/contact and event history, survey/contact/interview/message progress, SMS and email templates, result codes, users, companies, and roles. - Prefer product-purpose clarity, workflow consistency, and backward compatibility over broad technical cleanup. ### Domain and Integration Boundaries - Preserve the selected project context and company, project, role, and user access boundaries across navigation, queries, dialogs, and mutations. - Treat list headers/items, assignment state, contact history, call state, progress metrics, result codes, templates, uploaded files, and exported files as coordinated API contracts with contact-server. - Keep server-only credentials and privileged integration logic out of client bundles. Preserve the established Next.js API proxy and server/client boundaries. - Minimize exposure of names, telephone numbers, contact history, and uploaded list data in UI state, logs, errors, screenshots, and test fixtures. - Do not send real SMS or email, initiate real calls, or invoke production integrations during development or validation. ### Frontend Implementation - Use the consumed KRI frontend common and UI registry contracts instead of copying shared utilities, components, or conventions locally. - Prefer an existing shadcn/ui or approved registry component before creating a new foundational UI component. Compose or extend it locally only for project-specific behavior. - Do not create new TypeScript type or interface names ending in `Dto` or `DTO`; use domain- or purpose-specific names. - Preserve accessibility and loading, empty, error, disabled, confirmation, and success states for operational workflows. - Coordinate request, response, validation, authentication, and error-shape changes with contact-server without requiring an unsafe simultaneous deployment. ### Harness and Verification - `AGENTS.md` and `CLAUDE.md` are generated. Edit `.agent/profile.yml` or `.agent/project.md`, then recompose instead of editing generated files. - Use the repository's existing package manager and focused lint, type-check, test, or build commands. Validation must not call real business integrations.