# DS001B — Complete Couple Portal Brand Alignment
**Design Sprint | Verification & Completion**

---

# Objective

A previous AI assistant partially implemented DS001 before the session unexpectedly ended.

Your first responsibility is to verify the existing implementation.

Do NOT assume the previous implementation is correct.

Inspect the current codebase and compare it against the official branding package.

If an existing implementation already complies with the branding package, preserve it.

If an implementation is incomplete, inconsistent, or conflicts with the branding package, improve it before continuing.

Only after completing this verification should you finish the remaining DS001 work.

---

# Project Context

Before making any changes, read the official branding package located at:

/assets/branding/

Required documents:

- README.md
- brand-colors.md
- design-system.md
- ai_guide.md

These documents are the single source of truth for all branding decisions.

If any implementation conflicts with the branding package, always follow the branding package.

---

# Phase 1 — Verification

Review the work already completed.

Verify that the following areas comply with the branding package:

- design_system.css
- layouts/couple.php
- Budget Dashboard
- Invitation Dashboard (partial)

Check for:

- Correct brand colors
- Proper typography hierarchy
- Component consistency
- Button hierarchy
- Card styling
- Sidebar styling
- Navigation styling
- Icon containers
- Accessibility
- Contrast
- Reusable component usage

Do not change code that already complies with the branding package.

Improve only where necessary.

---

# Phase 2 — Complete Remaining Work

After verification, complete the remaining Brand Alignment work.

Remaining pages include:

- Invitation Dashboard Hero
- Timeline Dashboard
- Wedding Insights
- Wedding Report

Standardize page headers and breadcrumbs for:

- Budget Settings
- Budget Detail
- Timeline Tasks
- Create Task
- Edit Task
- Invitation Edit
- RSVP Center
- Wishes
- WhatsApp Queue

Replace remaining legacy Tailwind color usage with the official design system where appropriate.

Reuse shared components whenever possible.

Avoid duplicate styling.

---

# Constraints

Do NOT:

- redesign layouts
- move sections
- introduce new features
- modify controllers
- modify models
- modify routes
- modify business logic
- modify database structure

This sprint is strictly for visual implementation and branding consistency.

---

# Deliverables

Provide:

## 1. Verification Summary

Summarize whether the previous implementation:

- Fully correct
- Mostly correct
- Partially correct
- Required corrections

Explain any corrections made.

---

## 2. Brand Alignment Completed

Describe the remaining work completed.

---

## 3. Components Standardized

List reusable components or patterns applied.

---

## 4. Files Modified

List every modified file.

---

## 5. PHP Syntax Verification

Verify all modified PHP files are free from syntax errors.

---

# Success Criteria

The Couple Portal should:

- Fully comply with the official branding package located in `/assets/branding/`.
- Present a consistent premium wedding experience.
- Preserve all existing UX and functionality.
- Avoid unnecessary changes to already compliant code.