Files
kfpa-cx-dash-front/.agent/project.md

1.6 KiB

KFPA CX Dashboard Frontend Repository Rules

Deliverable and User Experience

  • This Next.js frontend visualizes KFPA CSI summaries, ranks, business and object-type comparisons, comments, and related survey results.
  • Treat approved planning and acceptance material as the scope boundary. Preserve section navigation, survey-date context, filters, labels, chart/table values, rankings, comment workflows, and export behavior.
  • A visual change must not silently alter the represented score, denominator, rank, tie handling, ordering, rounding, tooltip meaning, or empty-data behavior.
  • Keep customer survey data, comments, exported workbooks, and planning material out of logs, fixtures, screenshots, and external services.

Frontend Implementation

  • 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.
  • Preserve accessibility, responsive layout, loading, empty, error, unauthorized, confirmation, success, and administrative-edit states.
  • Coordinate API request, response, authentication, statistics, comment, and error changes with the backend 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 existing npm scripts and focused lint, type-check, test, or production build checks. Do not call production APIs, modify real comments, or export customer data during validation.