21 lines
1.5 KiB
Markdown
21 lines
1.5 KiB
Markdown
## LGE CX Dashboard Frontend Repository Rules
|
|
|
|
### Deliverable and User Experience
|
|
|
|
- This Next.js frontend visualizes LGE appliance penetration, purchase, category, profile, and trend survey statistics.
|
|
- Treat approved planning and design material as the scope boundary. Preserve category navigation, filters, labels, chart/table values, comparison context, and Excel export behavior.
|
|
- A visual change must not silently alter the represented statistic, denominator, ordering, rounding, tooltip meaning, or empty-data behavior.
|
|
- Keep customer survey data, exported workbooks, and internal 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, and export states across every dashboard route.
|
|
- Coordinate API request, response, authentication, 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 the existing npm scripts and focused lint, type-check, test, or production build checks. Do not call production APIs or export real customer data during validation.
|