# RC-008
## Shared Design System Foundation

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

IMPORTANT

This is NOT feature development.

This is NOT authentication work.

This is NOT landing page redesign.

This is NOT dashboard redesign.

This patch creates the shared visual design system that will be reused across the entire platform.

The application has already completed:

✓ RC-005 Dashboard Layout Recovery

✓ RC-006 Landing Page Architecture

✓ RC-007 Brand Identity & Visual Refinement

Do NOT modify business logic.

Do NOT modify routing.

Do NOT modify authentication.

Do NOT modify controllers unless absolutely required for shared UI rendering.

---

Objective

Create a reusable design system for all future pages.

This design system will become the visual foundation for:

• Landing Page

• Admin Panel

• Couple Panel

• Crew Panel

• Theme Engine

• Public Invitation Themes

The goal is consistency.

---

Brand Identity

Keep the existing RC-007 palette.

Base

White

Primary

Soft Lavender

Secondary

Soft Periwinkle Blue

Accent

Soft Rose

Neutral

Slate Gray

Do NOT introduce new colors.

---

Create Shared Components

Standardize these UI components.

Buttons

Primary

Secondary

Outline

Danger

Success

Small

Medium

Large

Loading state

Disabled state

---

Cards

Default Card

Feature Card

Dashboard Card

Pricing Card

Statistics Card

Hover Card

---

Forms

Input

Textarea

Select

Checkbox

Radio

Toggle

Validation State

Disabled State

Readonly State

---

Alerts

Success

Info

Warning

Danger

---

Badges

Primary

Secondary

Success

Warning

Danger

Neutral

---

Tables

Header

Rows

Hover

Empty State

Pagination Style

---

Empty States

No Data

No Guest

No Invitation

No Workspace

---

Loading States

Button Loading

Card Skeleton

Table Skeleton

Spinner

---

Typography

Standardize

Display

H1

H2

H3

H4

Paragraph

Small

Caption

Muted Text

Links

---

Spacing

Standardize spacing scale.

Use consistent Tailwind spacing.

Avoid arbitrary values.

---

Border Radius

Use consistent radius.

Small

Medium

Large

Extra Large

Avoid mixing many radius values.

---

Shadow System

Create one consistent shadow scale.

Small

Medium

Large

Hover

No excessive shadows.

---

Icons

Standardize icon sizing.

Button icons

Navigation icons

Feature icons

Status icons

Do NOT change icon library.

---

Forms

All forms should visually match.

Landing

Admin

Couple

Crew

Settings

Workspace Provision

Guest Import

Invitation

Messaging

---

Dashboard

Do NOT redesign dashboard.

Only ensure components use the same design system.

---

Landing

Do NOT redesign landing.

Only replace duplicated component styles with shared ones where applicable.

---

Theme Compatibility

IMPORTANT

The shared design system must be reusable by future invitation themes.

Do NOT build theme-specific styles.

Instead create neutral reusable components.

Future themes must inherit these components naturally.

---

Implementation

Prefer:

Reusable Tailwind utility classes

Shared partials

Reusable Blade/PHP partials (if applicable)

Centralized CSS utilities

Avoid duplicated component styling.

---

Constraints

Do NOT

Modify business logic

Modify routing

Modify authentication

Modify database

Modify Theme Engine

Modify invitation rendering

Modify controllers unnecessarily

Introduce CSS frameworks

Replace Tailwind

Introduce JavaScript frameworks

---

Verification

Verify

Landing

Admin

Couple

Crew

Workspace

Settings

Buttons

Cards

Forms

Alerts

Tables

Badges

Responsive

Accessibility

BASE_PATH compatibility

localhost/inveetaire compatibility

Production compatibility

PHP syntax passes

---

Acceptance Criteria

PASS only if:

Shared design system established.

Components visually consistent.

No duplicated styling.

Landing unchanged structurally.

Dashboard unchanged structurally.

Business logic untouched.

Authentication untouched.

Ready for RC-009 Theme Engine.

PHP syntax passes.

---

Output

Provide:

1. Files created.

2. Files modified.

3. Shared components created.

4. Design tokens standardized.

5. Component consistency report.

6. Responsive verification.

7. Accessibility verification.

8. Acceptance checklist.

9. PHP syntax results.

Stop after implementation.

Wait for Human Approval.