## GWCF Monitoring Frontend Repository Rules ### Deliverable and User Workflows - This Next.js frontend supports GWCF performance records, monitoring assignments, schedules and visits, reviews, users, file preview, and related operational workflows. - Its product character is similar to KriContact, but its requirements, API, permissions, terminology, and deliverables remain project-specific. - Preserve selected performance context, assignment state, review state, visit information, filters, file-preview behavior, and user/role boundaries across navigation and mutations. - Keep personal information, monitoring details, uploaded documents, and exported data out of logs, fixtures, screenshots, and external services. ### Frontend and Local Next.js Guidance - Use the consumed KRI frontend common and UI registry contracts. Prefer an existing shadcn/ui or registry component before creating a new foundational component. - Do not create new TypeScript type or interface names ending in `Dto` or `DTO`. - This repository may use Next.js APIs and conventions newer than model training data. Read the relevant local guide under `node_modules/next/dist/docs/` before changing a Next.js API, routing convention, or file structure, and follow deprecation notices. - Preserve accessibility, loading, empty, error, unauthorized, confirmation, success, and file-preview states. - Coordinate request, response, authentication, file, and error changes with the backend without requiring an unsafe simultaneous deployment. ### Harness and Verification - The previous standalone `AGENTS.md` Next.js guidance has been preserved in this project source. `AGENTS.md` and `CLAUDE.md` are now harness-generated outputs. - Edit `.agent/profile.yml` or `.agent/project.md`, then recompose instead of editing generated files. - Use existing npm scripts and focused checks. Do not call production APIs, process customer documents, or submit real monitoring/review data during validation.