# RC-015
## Product Polish & Production Readiness

You are implementing Release Candidate RC-015 for the INVEETAIRE platform.

IMPORTANT

This is NOT feature development.

This is NOT Theme development.

This is NOT Wedding Event development.

This RC focuses on product polish, UX consistency, and production readiness.

The application has completed:

✓ RC-011 Couple Experience

✓ RC-012 Guest Management

✓ RC-013 Wedding Event Management

✓ RC-014 Guest Engagement Center

Do NOT redesign architecture.

Do NOT modify authentication.

Do NOT modify Theme Engine.

Do NOT change business logic.

Reuse existing components and Design System (RC-008).

---

Objective

Refine the entire Couple Workspace into a production-ready experience.

Focus on consistency, usability, responsiveness, accessibility, and visual polish.

No new business features.

---

Scope

## 1. Empty States

Review every Couple page.

Implement elegant empty states where data is unavailable.

Examples:

Dashboard

Guest List

RSVP Center

Guest Wishes

WhatsApp Queue

Wedding Day

Each empty state should include:

• icon

• title

• short description

• primary action (when applicable)

Reuse Design System.

---

## 2. Loading States

Implement loading UI.

Use skeleton components from RC-008.

Apply to:

Dashboard cards

Guest table

RSVP table

Wish list

Statistics cards

Do NOT use generic "Loading..." text.

---

## 3. Flash Messages

Standardize all flash messages.

Success

Information

Warning

Error

Use Design System alert components.

Consistent spacing.

Consistent icons.

Consistent wording.

---

## 4. Confirmation Dialogs

Standardize confirmation dialogs.

Guest delete

Reset WhatsApp Queue

Manual Override

Reject Entry

Logout

Use one modal style.

Consistent buttons.

Primary

Secondary

Danger

Escape closes modal.

Backdrop click configurable.

---

## 5. Form Consistency

Audit every Couple form.

Invitation

Guest

Settings

Import

Ensure:

consistent spacing

same label style

same input height

same button alignment

validation messages

required indicators

disabled state

readonly state

---

## 6. Tables

Audit all tables.

Guest List

RSVP

Wish List

Queue

Ensure:

responsive scrolling

sticky header

hover state

consistent pagination

empty rows

mobile readability

---

## 7. Mobile Experience

Review every Couple page.

Sidebar

Cards

Tables

Forms

Statistics

Timeline

Ensure usability on:

320px

375px

768px

1024px

---

## 8. Accessibility

Verify:

heading hierarchy

button labels

aria-label

aria-expanded

focus ring

keyboard navigation

tab order

contrast

Do NOT reduce accessibility.

---

## 9. Error Pages

Create consistent pages for:

403

404

500

Session Expired

Workspace Not Found

Invitation Not Found

Use Design System.

Maintain branding.

---

## 10. Performance Cleanup

Remove duplicated classes.

Remove dead markup.

Remove unused CSS hooks.

Simplify repetitive Tailwind markup by reusing Design System classes.

Do NOT change appearance.

---

## 11. Visual Consistency Audit

Review:

Landing

Login

Admin

Couple

Crew

Settings

Guest

Invitation

Wedding Day

Guest Engagement

Ensure:

same spacing

same border radius

same shadows

same typography

same colors

same button styles

same cards

No visual regressions.

---

Constraints

Do NOT

Modify authentication

Modify Theme Engine

Modify Event logic

Modify RSVP logic

Modify Guest logic

Modify database schema

Implement new business features

Change routing

Rewrite modules

---

Verification

Verify

Desktop

Tablet

Mobile

Sidebar

Forms

Tables

Dialogs

Empty States

Loading States

Alerts

Accessibility

BASE_PATH compatibility

localhost/inveetaire compatibility

Production compatibility

PHP syntax

---

Acceptance Criteria

PASS only if

UI is visually consistent.

Empty states implemented.

Loading states implemented.

Dialogs standardized.

Forms standardized.

Tables standardized.

Accessibility improved.

Responsive verified.

No business logic changed.

PHP syntax passes.

---

Output

Provide:

1. Files created.

2. Files modified.

3. UI consistency improvements.

4. Empty state implementation.

5. Loading state implementation.

6. Dialog standardization.

7. Accessibility improvements.

8. Responsive verification.

9. Performance cleanup.

10. Acceptance checklist.

11. PHP syntax results.

Stop after implementation.

Wait for Human Approval.