Component review

Review the component structure of this codebase and help me reorganize it following component library best practices.

Goals:

1. Identify components that should be reusable patterns (layout/styling only, content via props)
2. Identify components that are feature components (complex, stateful, business logic)
3. Identify unused/orphaned components that can be deleted
4. Identify duplicate patterns across page-specific components

Proposed Structure:

• /ui - Primitives (button, input, card, etc.)
• /patterns - Reusable layout patterns (heroes, section headers, grids, CTAs)
• /features - Complex interactive components (forms, calculators, dialogs)
• /[page] - Page-specific sections that compose patterns + features

Process:

1. Explore the current component structure
2. Identify patterns - Find repeated layouts across page-specific folders
3. Check usage - Before migrating, verify components are actually used
4. Create patterns - Extract common layouts into parameterized components
5. Migrate - Update page components to use patterns
6. Cleanup - Delete unused/orphaned components

Key Principles:

• Patterns should be content-agnostic (receive content via props)
• Feature components with business logic stay unique
• Don't lose functionality when consolidating
• Check if components are actually used before migrating

Exclude from review:

• [Add folders to exclude, e.g., unused or design you do not want to clean up]