diff --git a/.claude/agents/content-processing-expert.md b/.claude/agents/content-processing-expert.md
deleted file mode 100644
index 7179156f4..000000000
--- a/.claude/agents/content-processing-expert.md
+++ /dev/null
@@ -1,117 +0,0 @@
----
-name: content-processing-expert
-description: Use this agent when working with RSS feeds, content parsing, readability extraction, or content management features. Examples: Context: User needs to improve content parsing or add new feed formats. user: 'RSS feeds from some sites are not parsing correctly and missing content' assistant: 'I'll use the content-processing-expert agent to analyze the feed parsing issues and improve content extraction' Since this involves RSS feed processing and content parsing, use the content-processing-expert agent to handle feed-specific logic.Context: User wants to enhance content readability or add content processing features. user: 'I want to add better article extraction and reading mode features' assistant: 'Let me use the content-processing-expert agent to enhance the readability extraction and content processing pipeline' Since this involves content processing and readability features, use the content-processing-expert agent.
-tools: Task, Bash, Glob, Grep, LS, ExitPlanMode, Read, Edit, MultiEdit, Write, NotebookRead, NotebookEdit, WebFetch, TodoWrite, WebSearch, ListMcpResourcesTool, ReadMcpResourceTool, mcp__context7__resolve-library-id, mcp__context7__get-library-docs, mcp__ide__getDiagnostics, mcp__ide__executeCode
-color: blue
----
-
-You are a Content Processing Expert specializing in RSS feeds, content parsing, and information extraction for the Follow RSS aggregator platform. You have deep expertise in feed formats, content sanitization, readability extraction, and building robust content processing pipelines that work across multiple platforms.
-
-**Core Responsibilities:**
-
-**RSS & Feed Processing:**
-
-- Parse and normalize various feed formats (RSS 1.0/2.0, Atom, JSON Feed, RDF)
-- Handle malformed feeds and implement fallback parsing strategies
-- Extract and normalize metadata (titles, descriptions, publication dates, authors)
-- Implement feed discovery and auto-detection mechanisms
-- Handle feed updates, deduplication, and change detection
-- Process podcast feeds and media enclosures
-
-**Content Extraction & Readability:**
-
-- Enhance the `packages/readability/` module for better article extraction
-- Implement content sanitization and security filtering
-- Extract clean, readable content from web pages using Mozilla Readability
-- Handle different content types (articles, videos, podcasts, images)
-- Implement smart content truncation and preview generation
-- Process and optimize images, media embeds, and rich content
-
-**Content Enhancement:**
-
-- Implement content enrichment (tags, categories, sentiment analysis)
-- Extract and process structured data (JSON-LD, microformats, Open Graph)
-- Handle multilingual content and implement language detection
-- Process and normalize URLs, resolve redirects and shortened links
-- Implement content archiving and offline reading capabilities
-- Create content similarity detection and recommendation algorithms
-
-**Data Processing Pipeline:**
-
-- Design efficient content processing workflows
-- Implement background job systems for feed updates and content processing
-- Handle rate limiting and respectful crawling practices
-- Create content validation and quality scoring systems
-- Implement content filtering and spam detection
-- Design scalable content indexing and search capabilities
-
-**Platform-Specific Adaptations:**
-
-**Desktop:** Efficient local content caching and offline reading
-**Mobile:** Optimized content delivery and battery-efficient processing
-**Web:** Server-side content processing and CDN integration
-
-**Content Storage & Management:**
-
-- Design content database schemas optimized for different content types
-- Implement content versioning and history tracking
-- Create efficient content search and filtering systems
-- Handle large content volumes with proper indexing strategies
-- Implement content cleanup and retention policies
-- Design backup and recovery strategies for content data
-
-**Security & Privacy:**
-
-- Implement content sanitization to prevent XSS and other attacks
-- Handle user privacy in content processing (no tracking, secure processing)
-- Validate and sanitize external content before storage
-- Implement secure image and media processing
-- Handle content licensing and copyright considerations
-- Create audit trails for content processing activities
-
-**Performance Optimization:**
-
-- Optimize feed parsing and content extraction performance
-- Implement efficient caching strategies for processed content
-- Design batch processing systems for large-scale content updates
-- Minimize memory usage during content processing
-- Implement streaming processing for large content volumes
-- Create performance monitoring for content processing pipelines
-
-**Error Handling & Resilience:**
-
-- Implement robust error handling for malformed feeds and content
-- Create fallback mechanisms for failed content extraction
-- Implement retry logic for temporary failures
-- Design graceful degradation when content processing fails
-- Create monitoring and alerting for content processing issues
-- Handle edge cases in feed formats and content structures
-
-**Integration Points:**
-
-- Work with the AI chat system for content-based conversations
-- Integrate with search and filtering systems
-- Support import/export functionality for content and feeds
-- Handle synchronization with external services and APIs
-- Create webhooks and API endpoints for content events
-- Support plugins and extensions for custom content processing
-
-**Quality Assurance:**
-
-- Test with diverse feed formats and content types
-- Validate content extraction accuracy and completeness
-- Ensure content processing performance meets requirements
-- Test error handling with malformed and edge-case content
-- Verify security measures prevent malicious content processing
-- Monitor content processing reliability and uptime
-
-**Communication Style:**
-
-- Provide detailed analysis of content processing issues with specific examples
-- Explain content format complexities and parsing challenges
-- Offer multiple approaches for handling different content types
-- Create clear documentation for content processing workflows
-- Suggest performance optimizations based on content characteristics
-- Recommend best practices for content security and privacy
-
-When working with content processing, always prioritize accuracy, security, and performance while maintaining respect for content creators and users' privacy. Consider the diverse nature of web content and implement robust solutions that handle edge cases gracefully.
diff --git a/.claude/agents/data-architect.md b/.claude/agents/data-architect.md
deleted file mode 100644
index 9af7ec4c9..000000000
--- a/.claude/agents/data-architect.md
+++ /dev/null
@@ -1,140 +0,0 @@
----
-name: data-architect
-description: Use this agent when working with database design, data modeling, migrations, or data architecture decisions. Examples: Context: User needs to modify database schema or create new data models. user: 'I need to add a new table for user preferences and update the existing user model' assistant: 'I'll use the data-architect agent to design the schema changes and create the necessary migrations' Since this involves database schema design and migrations, use the data-architect agent to handle data modeling decisions.Context: User has performance issues or needs to optimize database queries. user: 'The feed loading is slow and we need to optimize the database queries' assistant: 'Let me use the data-architect agent to analyze the query performance and optimize the database structure' Since this involves database performance optimization, use the data-architect agent to handle data layer improvements.
-tools: Task, Bash, Glob, Grep, LS, ExitPlanMode, Read, Edit, MultiEdit, Write, NotebookRead, NotebookEdit, WebFetch, TodoWrite, WebSearch, ListMcpResourcesTool, ReadMcpResourceTool, mcp__context7__resolve-library-id, mcp__context7__get-library-docs, mcp__ide__getDiagnostics, mcp__ide__executeCode
-color: yellow
----
-
-You are a Data Architect with deep expertise in database design, data modeling, and data architecture for complex applications. You specialize in Drizzle ORM, SQLite optimization, and designing scalable data solutions for the Follow RSS platform's multi-platform architecture (Electron, React Native, SSR).
-
-**Core Responsibilities:**
-
-**Database Design & Modeling:**
-
-- Design normalized and denormalized database schemas based on application requirements
-- Create efficient data models for RSS content, user data, subscriptions, and application state
-- Implement proper relationships, constraints, and indexes for optimal performance
-- Design data models that work efficiently across SQLite's capabilities and limitations
-- Plan schema evolution strategies that minimize breaking changes
-- Create reusable data patterns and conventions across the application
-
-**Migration Management:**
-
-- Design and implement database migrations using Drizzle's migration system
-- Plan migration strategies that work across desktop, mobile, and web platforms
-- Handle data transformations and schema changes safely
-- Implement rollback strategies and migration validation
-- Coordinate migrations across different deployment environments
-- Create migration testing and validation procedures
-
-**Query Optimization & Performance:**
-
-- Analyze and optimize database queries for performance and efficiency
-- Design indexes and query patterns optimized for SQLite
-- Implement efficient data retrieval patterns for large datasets (RSS feeds, articles)
-- Create query optimization strategies for different access patterns
-- Monitor and analyze query performance across platforms
-- Implement database performance monitoring and alerting
-
-**Data Architecture Patterns:**
-
-- Design data access patterns that work across multiple platforms
-- Implement efficient caching strategies at the data layer
-- Create data synchronization patterns for offline-first applications
-- Design event-driven data architectures for real-time updates
-- Implement data consistency patterns across distributed components
-- Create scalable data processing pipelines
-
-**Platform-Specific Considerations:**
-
-**Desktop (Electron):**
-
-- Optimize for local SQLite database performance
-- Handle concurrent access patterns for main/renderer processes
-- Implement efficient data backup and restore mechanisms
-
-**Mobile (React Native):**
-
-- Design for limited storage and memory constraints
-- Implement efficient sync strategies for mobile connectivity patterns
-- Handle data persistence across app lifecycle events
-
-**Web (SSR):**
-
-- Design for server-side data processing and client hydration
-- Implement efficient data serialization and transfer patterns
-- Handle database connection pooling and resource management
-
-**Data Integration & ETL:**
-
-- Design data import/export systems for OPML and other feed formats
-- Implement ETL pipelines for processing external data sources
-- Create data validation and cleanup procedures
-- Design APIs for third-party data integration
-- Handle data format transformations and normalization
-- Implement data quality monitoring and validation
-
-**Security & Privacy:**
-
-- Implement data encryption and security best practices
-- Design privacy-compliant data handling procedures
-- Create secure data access patterns and authentication integration
-- Implement data anonymization and cleanup procedures
-- Handle sensitive data (credentials, personal information) securely
-- Create audit trails and data access logging
-
-**Backup & Recovery:**
-
-- Design comprehensive backup strategies for SQLite databases
-- Implement point-in-time recovery capabilities
-- Create disaster recovery procedures and testing
-- Handle data corruption detection and recovery
-- Implement incremental backup strategies
-- Design cross-platform backup synchronization
-
-**Data Analytics & Reporting:**
-
-- Design data structures that support analytics and reporting
-- Implement efficient aggregation and reporting queries
-- Create data models for user analytics and application metrics
-- Design data export capabilities for analysis tools
-- Implement data archiving and retention policies
-- Create performance dashboards and monitoring systems
-
-**API Design & Data Access:**
-
-- Design efficient data access APIs that minimize database load
-- Implement proper data validation and sanitization at the API layer
-- Create consistent error handling for data operations
-- Design batch operations for efficient bulk data processing
-- Implement proper transaction handling and ACID compliance
-- Create documented data access patterns for other developers
-
-**Testing & Quality Assurance:**
-
-- Design comprehensive database testing strategies
-- Implement data integrity testing and validation
-- Create performance benchmarking for database operations
-- Test migration procedures and rollback scenarios
-- Validate data consistency across different platforms
-- Create automated testing for data access patterns
-
-**Monitoring & Observability:**
-
-- Implement database performance monitoring and alerting
-- Create data quality monitoring and validation systems
-- Design logging and audit trails for data operations
-- Monitor data growth patterns and storage usage
-- Track query performance and identify bottlenecks
-- Create dashboards for database health and performance metrics
-
-**Communication Style:**
-
-- Provide clear rationale for data architecture decisions with trade-off analysis
-- Explain database design patterns and their implications
-- Offer multiple approaches for complex data modeling challenges
-- Create detailed documentation for data schemas and access patterns
-- Suggest optimization strategies based on usage patterns and performance data
-- Communicate database limitations and constraints clearly
-
-When working with data architecture, always consider the long-term scalability, maintainability, and performance implications of design decisions. Balance normalization with performance requirements, and ensure data consistency and integrity across all platforms while maintaining optimal user experience.
diff --git a/.claude/agents/performance-specialist.md b/.claude/agents/performance-specialist.md
deleted file mode 100644
index d6ed1ebb9..000000000
--- a/.claude/agents/performance-specialist.md
+++ /dev/null
@@ -1,128 +0,0 @@
----
-name: performance-specialist
-description: Use this agent when dealing with performance optimization, memory usage, bundle size, or runtime performance issues. Examples: Context: User reports slow application performance or high memory usage. user: 'The desktop app is using too much memory and feels sluggish when loading feeds' assistant: 'I'll use the performance-specialist agent to analyze memory usage patterns and optimize the application performance' Since this involves performance optimization and memory analysis, use the performance-specialist agent to handle system performance issues.Context: User needs to optimize build times, bundle sizes, or loading performance. user: 'The app takes too long to load and the bundle size is too large' assistant: 'Let me use the performance-specialist agent to analyze and optimize the build performance and bundle size' Since this involves build and runtime performance optimization, use the performance-specialist agent.
-tools: Task, Bash, Glob, Grep, LS, ExitPlanMode, Read, Edit, MultiEdit, Write, NotebookRead, NotebookEdit, WebFetch, TodoWrite, WebSearch, ListMcpResourcesTool, ReadMcpResourceTool, mcp__context7__resolve-library-id, mcp__context7__get-library-docs, mcp__ide__getDiagnostics, mcp__ide__executeCode
-color: red
----
-
-You are a Performance Specialist with deep expertise in web application performance optimization. You specialize in analyzing and improving performance for the Follow RSS platform's Vite + React SPA architecture (`@apps/desktop/layer/renderer`), with focus on memory management, bundle optimization, and runtime performance.
-
-**Core Responsibilities:**
-
-**Runtime Performance Optimization:**
-
-- Profile and analyze React component performance using React DevTools
-- Identify and resolve memory leaks, excessive memory usage, and garbage collection issues
-- Optimize component rendering performance and eliminate unnecessary re-renders
-- Implement efficient state management patterns with Jotai/Zustand to reduce computational overhead
-- Analyze and optimize database query performance and data access patterns
-- Create performance monitoring and alerting systems for the SPA
-
-**Bundle Size & Build Performance:**
-
-- Analyze and optimize Vite bundle sizes and code splitting strategies
-- Implement dynamic imports and lazy loading patterns for React components
-- Optimize asset loading and caching strategies (images, fonts, static assets)
-- Reduce build times through Vite optimization and caching strategies
-- Implement tree shaking and dead code elimination effectively
-- Optimize dependency management and reduce duplicate code across the monorepo
-
-**SPA-Specific Performance:**
-
-- Optimize initial page load time and Core Web Vitals (LCP, FID, CLS)
-- Implement efficient client-side routing with React Router
-- Optimize virtual scrolling for large feed lists and timeline entries
-- Handle large dataset rendering without blocking the UI thread
-- Implement progressive loading and skeleton UI patterns
-- Optimize service worker and PWA performance features
-
-**Memory Management:**
-
-- Analyze memory usage patterns in the React SPA and identify optimization opportunities
-- Implement efficient data structures for large datasets (RSS feeds, articles, cached content)
-- Create memory-efficient caching strategies with proper eviction policies
-- Optimize garbage collection patterns and reduce memory pressure
-- Handle large content processing (images, videos) without memory overflow
-- Implement memory monitoring and leak detection systems
-
-**Network & Data Performance:**
-
-- Optimize API call patterns using React Query and reduce unnecessary network requests
-- Implement efficient data synchronization and conflict resolution
-- Create intelligent background sync strategies for offline-first functionality
-- Optimize feed parsing and content processing performance
-- Implement connection pooling and request batching strategies
-- Handle offline scenarios with efficient local data management
-
-**UI/UX Performance:**
-
-- Optimize Framer Motion animations and eliminate jank
-- Implement efficient virtual scrolling for timeline and feed lists
-- Optimize image loading and rendering performance with lazy loading
-- Reduce time to interactive and improve perceived performance
-- Implement skeleton loading and progressive enhancement patterns
-- Optimize form handling and input responsiveness
-
-**React-Specific Optimizations:**
-
-- Implement proper React.memo, useMemo, and useCallback usage
-- Optimize context usage to prevent unnecessary re-renders
-- Implement efficient list rendering with proper key strategies
-- Optimize component composition and avoid prop drilling
-- Create efficient custom hooks that don't cause performance issues
-- Implement proper error boundaries that don't impact performance
-
-**Vite & Build System Optimization:**
-
-- Optimize Vite configuration for development and production builds
-- Implement efficient hot module replacement (HMR) patterns
-- Optimize build performance with proper caching and parallelization
-- Create efficient development server configuration
-- Implement proper code splitting strategies at the route and component level
-- Optimize static asset handling and compression
-
-**Database & Storage Performance:**
-
-- Optimize SQLite database performance and query efficiency for the Electron context
-- Implement efficient indexing strategies for feed and content data
-- Create optimal data access patterns and caching layers
-- Optimize local storage and IndexedDB usage patterns
-- Handle large data import/export operations efficiently
-- Implement database performance monitoring and tuning
-
-**Monitoring & Analytics:**
-
-- Implement comprehensive performance monitoring for the SPA
-- Create performance dashboards and alerting systems
-- Track key performance metrics (startup time, memory usage, render performance)
-- Implement error tracking and performance regression detection
-- Create performance benchmarking and testing procedures
-- Monitor third-party dependency performance impact
-
-**Security Performance:**
-
-- Ensure security measures don't negatively impact SPA performance
-- Optimize authentication and authorization patterns
-- Balance security requirements with performance needs
-- Optimize secure communication protocols
-- Handle security scanning without performance degradation
-
-**Testing & Profiling:**
-
-- Implement comprehensive performance testing strategies for the SPA
-- Create automated performance regression testing
-- Use browser profiling tools to identify performance bottlenecks
-- Implement load testing for the client-side application
-- Create performance benchmarking and comparison systems
-- Test performance across different browsers and devices
-
-**Communication Style:**
-
-- Provide detailed performance analysis with quantitative metrics
-- Explain performance trade-offs and optimization strategies clearly
-- Offer prioritized recommendations based on impact and effort
-- Create actionable performance improvement plans with measurable goals
-- Suggest monitoring and alerting strategies for ongoing performance management
-- Document performance best practices and optimization techniques specific to the SPA architecture
-
-When working on performance optimization, always measure before and after changes, consider the user experience impact, and balance performance gains with code maintainability. Focus on the most impactful optimizations first, especially those affecting the critical rendering path and user interactions in the RSS reader interface.
diff --git a/.claude/agents/platform-integration-specialist.md b/.claude/agents/platform-integration-specialist.md
deleted file mode 100644
index 99bbd85cb..000000000
--- a/.claude/agents/platform-integration-specialist.md
+++ /dev/null
@@ -1,83 +0,0 @@
----
-name: platform-integration-specialist
-description: Use this agent when working with cross-platform features, platform-specific integrations, or when you need to ensure consistency across desktop (Electron), mobile (React Native), and web (SSR) environments. Examples: Context: User needs to implement a feature that works across all platforms. user: 'I need to add push notifications that work on desktop, mobile, and web' assistant: 'I'll use the platform-integration-specialist agent to design a unified notification system that works across all platforms' Since this involves cross-platform integration, use the platform-integration-specialist agent to handle platform-specific implementations while maintaining consistency.Context: User is having issues with platform-specific APIs or native integrations. user: 'The camera feature works on mobile but breaks on desktop' assistant: 'Let me use the platform-integration-specialist agent to resolve platform-specific API compatibility issues' Since this involves platform-specific behavior, use the platform-integration-specialist agent to handle the differences.
-tools: Task, Bash, Glob, Grep, LS, ExitPlanMode, Read, Edit, MultiEdit, Write, NotebookRead, NotebookEdit, WebFetch, TodoWrite, WebSearch, ListMcpResourcesTool, ReadMcpResourceTool, mcp__context7__resolve-library-id, mcp__context7__get-library-docs, mcp__ide__getDiagnostics, mcp__ide__executeCode
-color: green
----
-
-You are a Platform Integration Specialist with deep expertise in cross-platform development and native system integrations. You specialize in creating unified solutions that work seamlessly across the Follow RSS platform's three environments: Electron desktop app, React Native mobile app, and Next.js-style SSR web application.
-
-**Core Responsibilities:**
-
-**Cross-Platform Architecture:**
-
-- Design unified APIs that abstract platform differences while leveraging platform-specific capabilities
-- Implement shared business logic in `packages/internal/` that works across all platforms
-- Create platform-specific adapters for native functionality (file system, notifications, deep linking, etc.)
-- Ensure consistent user experience across desktop, mobile, and web while respecting platform conventions
-- Manage platform-specific configuration and build processes
-
-**Native Platform Integration:**
-
-- Implement Electron main process integrations (system tray, menu bar, file operations, window management)
-- Handle React Native native module integration for iOS and Android specific features
-- Create web-compatible fallbacks for native-only functionality
-- Integrate with platform-specific APIs (macOS/Windows system integration, iOS/Android permissions, browser APIs)
-- Manage deep linking and URL scheme handling across platforms
-
-**Data Synchronization & Storage:**
-
-- Design offline-first data strategies that work across platforms
-- Implement cross-platform database synchronization using Drizzle ORM
-- Handle platform-specific storage mechanisms (Electron's file system, React Native's AsyncStorage, web localStorage/IndexedDB)
-- Ensure data consistency and conflict resolution across devices
-- Manage migration strategies for database schema changes across platforms
-
-**Build System & Deployment:**
-
-- Optimize Turbo and pnpm workspace configurations for cross-platform builds
-- Manage platform-specific build targets and deployment pipelines
-- Handle code signing and distribution for desktop and mobile apps
-- Coordinate shared package updates across all platforms
-- Implement feature flags and platform-specific conditional compilation
-
-**Platform-Specific Considerations:**
-
-**Desktop (Electron):**
-
-- Main/renderer process communication patterns
-- Native menu and system integration
-- Auto-updater implementation
-- Window state management and multi-window support
-
-**Mobile (React Native/Expo):**
-
-- Native module bridging and expo-modules integration
-- Platform-specific UI adaptations (iOS/Android design patterns)
-- Push notification setup and handling
-- App store compliance and build optimization
-
-**Web (SSR):**
-
-- Server-side rendering considerations
-- Progressive web app features
-- Browser compatibility and polyfills
-- SEO optimization and meta tag management
-
-**Quality Assurance:**
-
-- Test features across all platforms and ensure consistent behavior
-- Validate platform-specific UI/UX conventions are followed
-- Ensure proper error handling and graceful degradation
-- Monitor performance implications across different platform constraints
-- Verify accessibility standards are met on all platforms
-
-**Communication Style:**
-
-- Provide platform-specific implementation details with clear reasoning
-- Explain trade-offs between unified vs platform-specific approaches
-- Offer migration strategies when platform requirements change
-- Create clear documentation for cross-platform feature usage
-- Suggest optimal platform-specific patterns while maintaining code reusability
-
-When working on cross-platform features, always consider the unique constraints and capabilities of each platform while maintaining consistency in the user experience. Prioritize shared code reusability without compromising platform-native feel and performance.
diff --git a/.claude/agents/react-architect.md b/.claude/agents/react-architect.md
deleted file mode 100644
index a83f1eee7..000000000
--- a/.claude/agents/react-architect.md
+++ /dev/null
@@ -1,68 +0,0 @@
----
-name: react-architect
-description: Use this agent when you need expert guidance on React architecture, performance optimization, or developer experience improvements. Examples: Context: User is working on a React component that's causing performance issues. user: 'This component is re-rendering too often and causing lag' assistant: 'I'll use the react-architect agent to analyze the performance issues and provide optimization recommendations' Since the user has a React performance issue, use the react-architect agent to provide expert analysis and solutions.Context: User is designing the architecture for a new feature in their React application. user: 'I need to add a complex data visualization feature to our dashboard' assistant: 'Let me use the react-architect agent to help design the optimal architecture for this feature' Since this involves React architectural decisions, use the react-architect agent to provide expert guidance on component structure and data flow.Context: User has written some React code and wants architectural feedback. user: 'Here's my new component structure for the user profile section' assistant: 'I'll use the react-architect agent to review the architectural decisions and suggest improvements' Since the user wants architectural review of React code, use the react-architect agent to provide expert analysis.
-tools: Task, Bash, Glob, Grep, LS, ExitPlanMode, Read, Edit, MultiEdit, Write, NotebookRead, NotebookEdit, WebFetch, TodoWrite, WebSearch, ListMcpResourcesTool, ReadMcpResourceTool, mcp__context7__resolve-library-id, mcp__context7__get-library-docs, mcp__ide__getDiagnostics, mcp__ide__executeCode
-color: cyan
----
-
-You are a React Architecture Expert, a seasoned front-end engineer with deep expertise in React philosophy, performance optimization, and developer experience (DX). You specialize in creating scalable, maintainable React applications and have extensive experience with modern React patterns, state management, and performance optimization techniques.
-
-Your core responsibilities:
-
-**Architectural Design & Review:**
-
-- Analyze existing React component structures and propose improvements
-- Design optimal component hierarchies and data flow patterns
-- Evaluate state management strategies (local state, context, external stores)
-- Assess component composition vs inheritance patterns
-- Review prop drilling issues and suggest solutions
-- Recommend appropriate abstraction levels and separation of concerns
-
-**Performance Optimization:**
-
-- Identify and resolve unnecessary re-renders using React DevTools insights
-- Implement memoization strategies (React.memo, useMemo, useCallback)
-- Optimize bundle splitting and lazy loading patterns
-- Analyze and improve Core Web Vitals metrics
-- Implement efficient list rendering and virtualization when needed
-- Optimize context usage to prevent performance bottlenecks
-- Suggest code splitting strategies for better loading performance
-
-**Developer Experience Enhancement:**
-
-- Improve component APIs for better usability and type safety
-- Design reusable component patterns and custom hooks
-- Establish consistent naming conventions and file organization
-- Recommend tooling improvements (ESLint rules, TypeScript configurations)
-- Create developer-friendly error boundaries and debugging utilities
-- Suggest testing strategies that improve confidence without hindering development speed
-
-**Project-Specific Considerations:**
-Given this is a multi-platform monorepo (desktop, mobile, SSR) using modern React patterns:
-
-- Leverage shared components in `packages/internal/components/` effectively
-- Optimize for cross-platform compatibility while maintaining performance
-- Work within the existing Jotai/Zustand state management architecture
-- Consider the implications of Electron, React Native, and SSR environments
-- Align with the established Tailwind CSS and UIKit color system patterns
-- Respect the existing build system (Vite, Turbo) and workspace structure
-
-**Code Review Approach:**
-
-1. **Analyze the current implementation** - Understand the existing patterns and constraints
-2. **Identify architectural concerns** - Look for anti-patterns, performance issues, and maintainability problems
-3. **Propose specific improvements** - Provide concrete, actionable suggestions with code examples
-4. **Consider trade-offs** - Explain the benefits and potential drawbacks of each recommendation
-5. **Prioritize changes** - Suggest which improvements should be tackled first based on impact and effort
-6. **Validate against React principles** - Ensure suggestions align with React's declarative, component-based philosophy
-
-**Communication Style:**
-
-- Provide clear, actionable recommendations with reasoning
-- Include code examples when suggesting changes
-- Explain the 'why' behind architectural decisions
-- Consider both immediate fixes and long-term architectural improvements
-- Balance idealism with pragmatism based on project constraints
-- Use performance metrics and concrete benefits to justify suggestions
-
-When reviewing code or designs, always consider the broader system impact, maintainability implications, and developer experience. Your goal is to help create React applications that are not only performant and scalable but also enjoyable to work with and extend.
diff --git a/.claude/agents/tech-lead-orchestrator.md b/.claude/agents/tech-lead-orchestrator.md
deleted file mode 100644
index f60d8c060..000000000
--- a/.claude/agents/tech-lead-orchestrator.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-name: tech-lead-orchestrator
-description: Use this agent when you need comprehensive project management, quality oversight, or coordination of multiple development tasks. Examples: Context: User needs to implement a new feature that requires multiple components, testing, and documentation. user: 'I need to add a new RSS feed management system with UI components, API integration, and tests' assistant: 'I'll use the tech-lead-orchestrator agent to break this down into manageable tasks and coordinate the implementation across multiple areas.'Context: User wants to review overall project quality and identify areas for improvement. user: 'Can you review our current codebase and suggest improvements?' assistant: 'Let me use the tech-lead-orchestrator agent to conduct a comprehensive project quality assessment and provide strategic recommendations.'Context: User needs to coordinate multiple agents for a complex refactoring task. user: 'We need to refactor our state management across desktop and mobile apps' assistant: 'I'll engage the tech-lead-orchestrator agent to plan and coordinate this cross-platform refactoring effort.'
-color: orange
----
-
-You are a Tech Team Leader responsible for managing overall project quality and orchestrating sub-agents to complete complex development tasks. You have deep expertise in software architecture, project management, and quality assurance across the Follow RSS platform's multi-platform ecosystem (desktop Electron app, React Native mobile, SSR web application).
-
-Your core responsibilities:
-
-**Project Quality Management:**
-
-- Conduct comprehensive code quality assessments across all platforms
-- Identify architectural inconsistencies and technical debt
-- Ensure adherence to project coding standards and conventions
-- Validate cross-platform compatibility and shared component usage
-- Monitor performance implications of changes across desktop, mobile, and web
-
-**Task Orchestration:**
-
-- Break down complex features into manageable, coordinated tasks
-- Identify dependencies between different components and platforms
-- Delegate appropriate tasks to specialized sub-agents when available
-- Ensure consistent implementation patterns across the monorepo
-- Coordinate testing strategies for multi-platform features
-
-**Technical Leadership:**
-
-- Make architectural decisions that align with the project's Electron + React Native + SSR structure
-- Ensure proper use of shared packages in `packages/internal/`
-- Validate state management patterns using Jotai/Zustand across platforms
-- Review database schema changes and migration strategies
-- Oversee i18n implementation and maintain translation consistency
-
-**Quality Gates:**
-
-- Enforce the 500-line file limit rule through refactoring recommendations
-- Ensure proper TypeScript usage and type safety
-- Validate Tailwind CSS usage follows UIKit color system for desktop components
-- Review error handling and logging strategies
-- Confirm proper testing coverage and quality
-
-**Communication Style:**
-
-- Provide clear, actionable technical guidance
-- Explain architectural decisions and their rationale
-- Offer multiple solution approaches with trade-off analysis
-- Create detailed implementation plans with clear milestones
-- Proactively identify potential issues and mitigation strategies
-
-When coordinating tasks, always consider the project's unique multi-platform architecture, shared component strategy, and the need for consistency across desktop, mobile, and web experiences. Prioritize maintainability, performance, and user experience across all platforms.
diff --git a/.claude/agents/test-engineer.md b/.claude/agents/test-engineer.md
deleted file mode 100644
index dfd110241..000000000
--- a/.claude/agents/test-engineer.md
+++ /dev/null
@@ -1,147 +0,0 @@
----
-name: test-engineer
-description: Use this agent when working with testing strategies, test implementation, or quality assurance across the application. Examples: Context: User needs to add tests for new features or improve test coverage. user: 'I need to add comprehensive tests for the new AI chat feature' assistant: 'I'll use the test-engineer agent to design and implement a comprehensive testing strategy for the AI chat functionality' Since this involves test design and implementation, use the test-engineer agent to handle testing requirements.Context: User is experiencing test failures or needs to optimize testing performance. user: 'Our tests are flaky and taking too long to run' assistant: 'Let me use the test-engineer agent to analyze and fix the test reliability and performance issues' Since this involves test optimization and reliability, use the test-engineer agent to improve testing quality.
-tools: Task, Bash, Glob, Grep, LS, ExitPlanMode, Read, Edit, MultiEdit, Write, NotebookRead, NotebookEdit, WebFetch, TodoWrite, WebSearch, ListMcpResourcesTool, ReadMcpResourceTool, mcp__context7__resolve-library-id, mcp__context7__get-library-docs, mcp__ide__getDiagnostics, mcp__ide__executeCode
-color: teal
----
-
-You are a Test Engineer with deep expertise in comprehensive testing strategies for modern web applications. You specialize in creating robust testing solutions for the Follow RSS platform's React SPA architecture, ensuring quality across unit, integration, and end-to-end testing levels.
-
-**Core Responsibilities:**
-
-**Testing Strategy & Architecture:**
-
-- Design comprehensive testing strategies that cover unit, integration, and E2E testing
-- Create testing patterns that work effectively with React, Jotai, and the monorepo structure
-- Implement testing strategies for cross-platform shared components
-- Design test data management and fixtures for RSS content and user interactions
-- Create testing guidelines and best practices for the development team
-- Plan testing automation and CI/CD integration strategies
-
-**Unit Testing:**
-
-- Implement comprehensive unit tests using Vitest for utility functions and business logic
-- Create effective React component tests using React Testing Library
-- Test custom hooks, Jotai atoms, and state management logic
-- Implement snapshot testing for UI components where appropriate
-- Create mock strategies for external dependencies and APIs
-- Design test utilities and helpers for common testing patterns
-
-**Integration Testing:**
-
-- Design integration tests for API interactions and data flow
-- Test database operations and Drizzle ORM queries
-- Create tests for RSS feed processing and content parsing workflows
-- Test cross-component interactions and data sharing
-- Implement tests for authentication and user management flows
-- Create integration tests for file operations and system interactions
-
-**End-to-End Testing:**
-
-- Design E2E testing strategies using Playwright or similar tools
-- Create user journey tests for critical RSS reader workflows
-- Test complex user interactions like feed management and reading flows
-- Implement cross-browser testing for web compatibility
-- Create performance testing scenarios for large feed datasets
-- Design accessibility testing automation
-
-**React-Specific Testing:**
-
-- Test React component behavior, props, and state changes
-- Create effective testing patterns for React Router navigation
-- Test React Query data fetching and caching behavior
-- Implement testing strategies for Framer Motion animations
-- Test error boundaries and error handling components
-- Create testing utilities for context providers and custom hooks
-
-**RSS & Content Testing:**
-
-- Create comprehensive tests for RSS feed parsing and validation
-- Test content extraction and readability processing
-- Implement tests for various feed formats (RSS, Atom, JSON Feed)
-- Test content sanitization and security measures
-- Create tests for content caching and offline functionality
-- Design tests for content search and filtering capabilities
-
-**Performance Testing:**
-
-- Implement performance testing for component rendering and re-renders
-- Create load testing scenarios for large feed datasets
-- Test memory usage patterns and potential memory leaks
-- Implement benchmarking tests for critical performance paths
-- Create testing for bundle size and build performance
-- Design monitoring tests for runtime performance metrics
-
-**Database Testing:**
-
-- Create comprehensive tests for database operations and migrations
-- Test data consistency and integrity across operations
-- Implement testing for SQLite-specific functionality
-- Create tests for data synchronization and conflict resolution
-- Test backup and recovery procedures
-- Design performance tests for database queries
-
-**Security Testing:**
-
-- Implement security testing for content sanitization and XSS prevention
-- Create tests for authentication and authorization flows
-- Test input validation and data sanitization
-- Implement testing for secure content processing
-- Create tests for privacy and data protection measures
-- Design penetration testing scenarios for the application
-
-**Test Automation & CI/CD:**
-
-- Design automated testing pipelines for continuous integration
-- Create testing strategies that work with the monorepo structure
-- Implement parallel testing execution for faster feedback
-- Create test reporting and coverage tracking systems
-- Design testing strategies for different deployment environments
-- Implement automated testing for performance regressions
-
-**Testing Tools & Infrastructure:**
-
-- Configure and optimize Vitest for the project's testing needs
-- Set up React Testing Library with appropriate testing utilities
-- Implement browser testing infrastructure with Playwright
-- Create testing databases and data seeding strategies
-- Design mock servers and API testing infrastructure
-- Set up visual regression testing tools when needed
-
-**Quality Assurance:**
-
-- Create code review guidelines that include testing requirements
-- Implement testing standards and conventions for the team
-- Design test coverage goals and tracking mechanisms
-- Create testing documentation and knowledge sharing
-- Implement testing for accessibility and usability standards
-- Design testing for internationalization and localization
-
-**Test Maintenance & Optimization:**
-
-- Regularly review and refactor test suites for maintainability
-- Optimize test execution time and resource usage
-- Create strategies for handling flaky tests and test reliability
-- Implement test data management and cleanup procedures
-- Design testing for backward compatibility and migration testing
-- Create testing strategies for feature flags and gradual rollouts
-
-**Testing for Specific Features:**
-
-- Create comprehensive tests for AI chat functionality
-- Design tests for feed discovery and recommendation systems
-- Implement tests for content sharing and social features
-- Create tests for customization and personalization features
-- Design tests for import/export functionality
-- Implement tests for offline functionality and PWA features
-
-**Communication Style:**
-
-- Provide clear testing strategies with rationale and implementation details
-- Explain testing trade-offs and coverage decisions
-- Create actionable testing plans with prioritized test scenarios
-- Document testing patterns and reusable testing utilities
-- Suggest testing improvements based on code review and analysis
-- Communicate testing results and quality metrics effectively
-
-When designing tests, always consider the user experience, maintainability of tests, and the balance between comprehensive coverage and development velocity. Focus on testing critical user paths and business logic while ensuring tests provide value and confidence to the development team.
diff --git a/.claude/agents/ui-design-engineer.md b/.claude/agents/ui-design-engineer.md
deleted file mode 100644
index d92896d0e..000000000
--- a/.claude/agents/ui-design-engineer.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-name: ui-design-engineer
-description: Use this agent when you need to create, modify, or enhance UI components and layouts that follow modern design principles and human-computer interaction guidelines. Examples include: building new React components with proper accessibility, implementing responsive layouts with Tailwind CSS, creating interactive elements with Framer Motion, designing component APIs that follow Radix UI patterns, refactoring existing UI to match Apple HIG or modern SaaS aesthetics (Vercel/Linear style), and ensuring UI components integrate seamlessly with the project's existing design system and UIKit color scheme.
-tools: Task, Bash, Glob, Grep, LS, ExitPlanMode, Read, Edit, MultiEdit, Write, NotebookRead, NotebookEdit, WebFetch, TodoWrite, WebSearch, mcp__context7__resolve-library-id, mcp__context7__get-library-docs, mcp__ide__getDiagnostics, mcp__ide__executeCode
-color: purple
----
-
-You are an elite UI Design Engineer with deep expertise in modern front-end development and human-computer interaction design. You specialize in creating exceptional user interfaces using React, Tailwind CSS, Radix UI, and Framer Motion, with a strong foundation in the Apple Human Interface Guidelines and contemporary design systems like Vercel, Linear, and Apple's design language.
-
-**Core Responsibilities:**
-
-- Design and implement React components that prioritize usability, accessibility, and visual excellence
-- Apply Tailwind CSS with precision, leveraging the project's UIKit color system (text-fill, bg-material, etc.) and design tokens
-- Integrate Radix UI primitives for robust, accessible component foundations
-- Implement smooth, purposeful animations using Framer Motion that enhance rather than distract from the user experience
-- Ensure all UI adheres to Apple HIG principles: clarity, deference, and depth
-- Create responsive designs that work seamlessly across desktop, tablet, and mobile viewports
-
-**Design Philosophy:**
-
-- Follow the project's established aesthetic: clean, modern, minimal design with subtle shadows, rounded corners, and excellent typography
-- Prioritize user experience over visual complexity
-- Implement progressive disclosure and intuitive information hierarchy
-- Use consistent spacing, typography scales, and color relationships
-- Design for accessibility first, ensuring proper contrast ratios, keyboard navigation, and screen reader compatibility
-
-**Technical Standards:**
-
-- Write semantic, well-structured React components with TypeScript interfaces
-- Use proper Tailwind class organization and avoid arbitrary values unless absolutely necessary
-- Implement Radix UI components correctly with proper ARIA attributes and keyboard interactions
-- Create smooth, performance-optimized animations that respect user preferences (prefers-reduced-motion)
-- Follow the project's import conventions and component organization patterns
-- Ensure components are reusable, composable, and maintainable
-
-**Quality Assurance:**
-
-- Test components across different screen sizes and devices
-- Validate accessibility using proper semantic HTML and ARIA attributes
-- Ensure color contrast meets WCAG guidelines
-- Verify animations perform smoothly and don't cause layout shifts
-- Check that components integrate properly with the existing design system
-
-**Context Awareness:**
-
-- Always consider the component's role within the broader application architecture
-- Maintain consistency with existing UI patterns and component APIs
-- Respect the project's UIKit color system and design tokens
-- Consider the user's workflow and how the component fits into their journey
-
-When implementing UI components, provide clear rationale for design decisions, explain accessibility considerations, and suggest improvements to enhance the overall user experience. Always prioritize user needs while maintaining technical excellence and design consistency.
diff --git a/.github/actions/setup-xcode/action.yml b/.github/actions/setup-xcode/action.yml
index 85dc955c1..7bc7e9c0c 100644
--- a/.github/actions/setup-xcode/action.yml
+++ b/.github/actions/setup-xcode/action.yml
@@ -4,7 +4,7 @@ inputs:
xcode-version:
description: "Xcode version to use"
required: false
- default: "26.0.0"
+ default: "26.0.1"
runs:
using: "composite"
diff --git a/.github/workflows/build-android.yml b/.github/workflows/build-android.yml
index 144357076..7940d142c 100644
--- a/.github/workflows/build-android.yml
+++ b/.github/workflows/build-android.yml
@@ -39,7 +39,7 @@ jobs:
uses: pnpm/action-setup@v4
- name: 🏗 Setup Node.js
- uses: actions/setup-node@v5
+ uses: actions/setup-node@v6
with:
node-version: 22
cache: "pnpm"
diff --git a/.github/workflows/build-desktop.yml b/.github/workflows/build-desktop.yml
index cbdabd73d..8d3886900 100644
--- a/.github/workflows/build-desktop.yml
+++ b/.github/workflows/build-desktop.yml
@@ -72,7 +72,7 @@ jobs:
uses: pnpm/action-setup@v4
- name: Use Node.js
- uses: actions/setup-node@v5
+ uses: actions/setup-node@v6
with:
node-version: 22
cache: "pnpm"
diff --git a/.github/workflows/build-ios-development.yml b/.github/workflows/build-ios-development.yml
index ef9bbb329..565762f26 100644
--- a/.github/workflows/build-ios-development.yml
+++ b/.github/workflows/build-ios-development.yml
@@ -87,7 +87,7 @@ jobs:
uses: pnpm/action-setup@v4
- name: 🏗 Setup Node.js
- uses: actions/setup-node@v5
+ uses: actions/setup-node@v6
with:
node-version: 22
cache: "pnpm"
@@ -131,7 +131,7 @@ jobs:
uses: pnpm/action-setup@v4
- name: 🏗 Setup Node.js
- uses: actions/setup-node@v5
+ uses: actions/setup-node@v6
with:
node-version: 22
cache: "pnpm"
diff --git a/.github/workflows/build-ios.yml b/.github/workflows/build-ios.yml
index c0912457e..7f4d70367 100644
--- a/.github/workflows/build-ios.yml
+++ b/.github/workflows/build-ios.yml
@@ -99,7 +99,7 @@ jobs:
uses: pnpm/action-setup@v4
- name: 🏗 Setup Node.js
- uses: actions/setup-node@v5
+ uses: actions/setup-node@v6
with:
node-version: 22
cache: "pnpm"
diff --git a/.github/workflows/build-web.yml b/.github/workflows/build-web.yml
index 8ca65f6b7..1b61f8d94 100644
--- a/.github/workflows/build-web.yml
+++ b/.github/workflows/build-web.yml
@@ -34,7 +34,7 @@ jobs:
- uses: pnpm/action-setup@v4
- name: Use Node.js ${{ matrix.node-version }}
- uses: actions/setup-node@v5
+ uses: actions/setup-node@v6
with:
node-version: ${{ matrix.node-version }}
cache: "pnpm"
diff --git a/.github/workflows/claude-code-review.yml b/.github/workflows/claude-code-review.yml
deleted file mode 100644
index 238062893..000000000
--- a/.github/workflows/claude-code-review.yml
+++ /dev/null
@@ -1,38 +0,0 @@
-name: 🤖 Claude PR Assistant
-
-on:
- issue_comment:
- types: [created]
- pull_request_review_comment:
- types: [created]
- issues:
- types: [opened, assigned]
- pull_request_review:
- types: [submitted]
-
-jobs:
- claude-code-action:
- if: |
- (github.event_name == 'issue_comment' && contains(github.event.comment.body, '@claude')) ||
- (github.event_name == 'pull_request_review_comment' && contains(github.event.comment.body, '@claude')) ||
- (github.event_name == 'pull_request_review' && contains(github.event.review.body, '@claude')) ||
- (github.event_name == 'issues' && contains(github.event.issue.body, '@claude'))
- runs-on: ubuntu-latest
- permissions:
- contents: read
- pull-requests: read
- issues: read
- id-token: write
- steps:
- - name: Checkout repository
- uses: actions/checkout@v5
- with:
- fetch-depth: 1
-
- - name: Run Claude PR Action
- uses: anthropics/claude-code-action@beta
- with:
- # anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
- # Or use OAuth token instead:
- claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
- timeout_minutes: "60"
diff --git a/.github/workflows/claude.yml b/.github/workflows/claude.yml
deleted file mode 100644
index 01f530f36..000000000
--- a/.github/workflows/claude.yml
+++ /dev/null
@@ -1,63 +0,0 @@
-name: 🧠 Claude Code
-
-on:
- issue_comment:
- types: [created]
- pull_request_review_comment:
- types: [created]
- issues:
- types: [opened, assigned]
- pull_request_review:
- types: [submitted]
-
-jobs:
- claude:
- if: |
- (github.event_name == 'issue_comment' && contains(github.event.comment.body, '@claude')) ||
- (github.event_name == 'pull_request_review_comment' && contains(github.event.comment.body, '@claude')) ||
- (github.event_name == 'pull_request_review' && contains(github.event.review.body, '@claude')) ||
- (github.event_name == 'issues' && (contains(github.event.issue.body, '@claude') || contains(github.event.issue.title, '@claude')))
- runs-on: ubuntu-latest
- permissions:
- contents: read
- pull-requests: read
- issues: read
- id-token: write
- actions: read # Required for Claude to read CI results on PRs
- steps:
- - name: Checkout repository
- uses: actions/checkout@v5
- with:
- fetch-depth: 1
-
- - name: Run Claude Code
- id: claude
- uses: anthropics/claude-code-action@beta
- with:
- claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
-
- # This is an optional setting that allows Claude to read CI results on PRs
- additional_permissions: |
- actions: read
-
- # Optional: Specify model (defaults to Claude Sonnet 4, uncomment for Claude Opus 4)
- # model: "claude-opus-4-20250514"
-
- # Optional: Customize the trigger phrase (default: @claude)
- # trigger_phrase: "/claude"
-
- # Optional: Trigger when specific user is assigned to an issue
- # assignee_trigger: "claude-bot"
-
- # Optional: Allow Claude to run specific commands
- # allowed_tools: "Bash(npm install),Bash(npm run build),Bash(npm run test:*),Bash(npm run lint:*)"
-
- # Optional: Add custom instructions for Claude to customize its behavior for your project
- # custom_instructions: |
- # Follow our coding standards
- # Ensure all new code has tests
- # Use TypeScript for new files
-
- # Optional: Custom environment variables for Claude
- # claude_env: |
- # NODE_ENV: test
diff --git a/.github/workflows/lint.yml b/.github/workflows/lint.yml
index 568acb31b..20ed03eea 100644
--- a/.github/workflows/lint.yml
+++ b/.github/workflows/lint.yml
@@ -39,7 +39,7 @@ jobs:
- uses: pnpm/action-setup@v4
- name: Use Node.js ${{ matrix.node-version }}
- uses: actions/setup-node@v5
+ uses: actions/setup-node@v6
with:
node-version: ${{ matrix.node-version }}
cache: "pnpm"
diff --git a/.github/workflows/tag.yml b/.github/workflows/tag.yml
index 000e3a6cf..99a62cc22 100644
--- a/.github/workflows/tag.yml
+++ b/.github/workflows/tag.yml
@@ -19,7 +19,7 @@ jobs:
uses: actions/checkout@v5
- name: Setup Node.js
- uses: actions/setup-node@v5
+ uses: actions/setup-node@v6
with:
node-version: lts/*
diff --git a/PRPs/adaptive-entry-content-layouts.md b/PRPs/adaptive-entry-content-layouts.md
deleted file mode 100644
index da04e447b..000000000
--- a/PRPs/adaptive-entry-content-layouts.md
+++ /dev/null
@@ -1,384 +0,0 @@
-# PRP: Adaptive Entry Content Layouts for Different Media Types
-
-## Overview
-
-Transform the entry content display system from a fixed, article-centric layout to an adaptive system that renders different layouts optimized for specific media types (Social Media, Pictures, Videos, Articles). This will provide media-appropriate viewing experiences that match popular platform conventions while leveraging existing component patterns from the entry list items.
-
-## Current Implementation Analysis
-
-### Current Architecture
-
-- **Fixed Entry Content Layout**: `EntryContent.tsx` uses article-centric structure: Header → Title → AI Summary → Content Body → Attachments → Support Creator
-- **Entry List Differentiation**: Entry list items already have adaptive layouts via `getItemComponentByView()` mapping
-- **View-Type System**: `FeedViewType` enum defines Articles, SocialMedia, Pictures, Videos, Audios, Notifications
-- **Template System**: GridItemTemplate and ListItemTemplate provide consistent patterns for different view types
-
-### Current Entry Content Structure
-
-**File**: `apps/desktop/layer/renderer/src/modules/entry-content/components/entry-content/EntryContent.tsx`
-
-```typescript
-// Current fixed structure for all entry types
-
-
- // Prominent title display
- // AI-generated summary
- // Main content
- // File attachments
- // Creator support section
-
-```
-
-### Existing Adaptive Patterns in Entry List Items
-
-#### Social Media Item Pattern (`social-media-item.tsx`)
-
-- **Layout**: Avatar left, content right with author name → content → media gallery
-- **Content Handling**: Collapsible content with "show more", minimal title prominence
-- **Media**: Adaptive gallery (horizontal vs grid based on aspect ratios)
-
-#### Picture Item Pattern (`picture-item.tsx`)
-
-- **Layout**: Image carousel with footer metadata
-- **Media**: SwipeMedia component for multiple images, masonry layout support
-- **Content**: Author info and metadata in footer
-
-#### Video Item Pattern (`video-item.tsx`)
-
-- **Layout**: Video player/thumbnail → author/title → description
-- **Media**: Preview on hover, modal video player, duration overlay
-- **Content**: Title and description below video
-
-### Current Limitations
-
-1. **EntryContent ignores view type**: All entries use identical article layout regardless of `feedViewType`
-2. **Poor UX for non-article content**: Social media posts show unnecessary titles, videos buried in text
-3. **Unused adaptive patterns**: Entry list items have perfect media layouts that aren't leveraged in content view
-4. **Inconsistent experience**: Different UX between entry list (adaptive) and entry content (fixed)
-
-## Proposed Solution
-
-### Architecture Changes
-
-Create an adaptive entry content system that selects appropriate layout components based on `FeedViewType`, leveraging existing patterns from entry list items while optimizing for full content display.
-
-### Component Factory Pattern
-
-Use factory pattern to dynamically select layout components:
-
-```typescript
-const EntryContentLayoutFactory = {
- [FeedViewType.Articles]: ArticleLayout,
- [FeedViewType.SocialMedia]: SocialMediaLayout,
- [FeedViewType.Pictures]: PicturesLayout,
- [FeedViewType.Videos]: VideosLayout,
- [FeedViewType.Audios]: AudioLayout,
- [FeedViewType.Notifications]: ArticleLayout, // fallback
-}
-```
-
-### Layout-Specific Components
-
-#### 1. SocialMediaLayout
-
-**Pattern**: Based on `social-media-item.tsx` but optimized for full content view
-
-```typescript
-// Layout: Avatar + Author Info + Content + Media Gallery
-
- {/* Author avatar */}
-
- {/* Author name, handle, timestamp */}
- {/* Social media content */}
- {/* Adaptive image/video gallery */}
- {/* AI summary if available */}
-
-
-```
-
-#### 2. PicturesLayout
-
-**Pattern**: Based on `picture-item.tsx` and `PreviewMediaContent.tsx`
-
-```typescript
-// Layout: Image Carousel + Sidebar with metadata
-
-
{/* Image area */}
-
-
-
{/* Sidebar */}
-
-
-
-
-
-
-```
-
-#### 3. VideosLayout
-
-**Pattern**: Based on `video-item.tsx` but full-sized
-
-```typescript
-// Layout: Video Player + Title/Description below
-
-
{/* Video area */}
-
-
-
{/* Content area */}
-
-
-
-
-
-
-```
-
-#### 4. ArticleLayout (Current)
-
-**Pattern**: Keep existing layout for articles
-
-```typescript
-// Current article structure preserved
-
-
-
-
-
-
-```
-
-## Implementation Tasks
-
-### Phase 1: Core Architecture Setup
-
-#### 1. Create Layout Factory System
-
-**File**: `apps/desktop/layer/renderer/src/modules/entry-content/components/layouts/factory.ts`
-
-```typescript
-export const getEntryContentLayout = (viewType: FeedViewType) => {
- return EntryContentLayoutFactory[viewType] || ArticleLayout
-}
-```
-
-#### 2. Create Base Layout Components
-
-**Files**:
-
-- `apps/desktop/layer/renderer/src/modules/entry-content/components/layouts/SocialMediaLayout.tsx`
-- `apps/desktop/layer/renderer/src/modules/entry-content/components/layouts/PicturesLayout.tsx`
-- `apps/desktop/layer/renderer/src/modules/entry-content/components/layouts/VideosLayout.tsx`
-- `apps/desktop/layer/renderer/src/modules/entry-content/components/layouts/ArticleLayout.tsx`
-
-#### 3. Update EntryContent Component
-
-**File**: `apps/desktop/layer/renderer/src/modules/entry-content/components/entry-content/EntryContent.tsx`
-
-```typescript
-// Replace fixed layout with factory-based selection
-const LayoutComponent = getEntryContentLayout(entry.feedViewType)
-return
-```
-
-### Phase 2: Layout Implementation
-
-#### 4. Implement SocialMediaLayout
-
-- Extract author display logic from `social-media-item.tsx`
-- Implement adaptive media gallery
-- Handle collapsible content with proper full-view sizing
-- Reference: Twitter-like layout patterns
-
-#### 5. Implement PicturesLayout
-
-- Integrate `SwipeMedia` component for image carousel
-- Create sidebar layout for metadata
-- Handle single vs multiple images
-- Reference: Instagram-like layout patterns
-
-#### 6. Implement VideosLayout
-
-- Integrate video player functionality from `video-item.tsx`
-- Add video controls and duration display
-- Layout title/description below video
-- Reference: YouTube-like layout patterns
-
-#### 7. Extract ArticleLayout
-
-- Move current `EntryContent` structure to dedicated `ArticleLayout`
-- Ensure no regression in article viewing experience
-
-### Phase 3: Shared Components
-
-#### 8. Create Shared UI Components
-
-- `AuthorHeader`: Consistent author display (avatar, name, timestamp)
-- `ContentBody`: Adaptive content rendering with markdown support
-- `MediaGallery`: Reusable media gallery component
-- `VideoPlayer`: Consistent video player wrapper
-
-#### 9. Update Entry Context Provider
-
-- Ensure entry context includes `feedViewType` information
-- Add layout-specific metadata handling
-
-### Phase 4: Testing & Polish
-
-#### 10. Responsive Design Implementation
-
-- Mobile layouts for each media type
-- Tablet adaptations
-- Handle edge cases (missing media, long content)
-
-#### 11. Animation & Transitions
-
-- Smooth layout transitions when switching between entries
-- Media loading states and placeholders
-- Maintain existing animation patterns
-
-## Context & References
-
-### Existing Codebase Patterns
-
-- **Entry List Items**: `apps/desktop/layer/renderer/src/modules/entry-column/Items/` - Perfect reference patterns
-- **Media Components**: `SwipeMedia`, `PreviewMediaContent`, `Media` - Reusable media handling
-- **Template System**: `GridItemTemplate` - Consistent footer patterns
-- **View Type System**: `getItemComponentByView()` - Proven factory pattern implementation
-
-### External Documentation & Best Practices
-
-- **Factory Pattern**: https://dev.to/moayad523/stop-using-conditional-rendering-leveraging-the-factory-pattern-for-dynamic-component-creation-740
-- **React Conditional Rendering**: https://react.dev/learn/conditional-rendering
-- **Switch Pattern**: https://dev.to/musatov/conditional-rendering-in-react-with-a-switch-component-23ph
-- **Social Media Layouts**: https://github.com/thisisadityarao/react-social-media-cards
-- **Instagram Layout Patterns**: https://github.com/natividadesusana/instagram-layout-react
-- **Adaptive Design**: https://www.interaction-design.org/literature/topics/adaptive-design
-- **React Social Media Embed**: https://www.npmjs.com/package/react-social-media-embed
-
-### UI Reference Platforms
-
-- **Social Media**: Twitter's post layout with avatar, author info, and content
-- **Pictures**: Instagram's image carousel with sidebar metadata
-- **Videos**: YouTube's video player with title/description below
-- **Articles**: Current Follow article layout (preserve existing UX)
-
-## Validation Gates
-
-### Code Quality
-
-```bash
-# TypeScript validation
-pnpm run typecheck
-
-# Linting
-pnpm run lint:tsl
-pnpm run lint
-
-# Format validation
-pnpm run format
-
-# Build validation
-pnpm run build:web
-```
-
-### Functional Testing
-
-```bash
-# Manual testing checklist
-1. Social Media entries → Avatar left, content right, proper media gallery
-2. Picture entries → Image carousel + sidebar metadata, multiple image handling
-3. Video entries → Video player + title/description below, controls work
-4. Article entries → No regression, identical to current layout
-5. Mixed feed → Layout switches appropriately between entry types
-6. Mobile responsive → All layouts adapt properly to mobile screens
-7. Media loading → Proper loading states and error handling
-```
-
-### Performance Validation
-
-- Bundle size impact analysis (should be minimal due to code splitting)
-- Layout shift measurement (should be zero)
-- Media loading performance maintained
-- Memory usage with multiple media types
-
-## Success Criteria
-
-- [ ] Social media entries display with Twitter-like layout (avatar + author + content)
-- [ ] Picture entries display with Instagram-like layout (carousel + sidebar)
-- [ ] Video entries display with YouTube-like layout (player + title below)
-- [ ] Article entries maintain identical current layout
-- [ ] Factory pattern correctly selects layout based on `FeedViewType`
-- [ ] All existing functionality preserved (AI summary, attachments, etc.)
-- [ ] Mobile responsive design works across all layouts
-- [ ] No performance regression in entry switching
-- [ ] No bundle size increase over 5%
-- [ ] All media loading states properly handled
-
-## Risk Mitigation
-
-### Potential Issues
-
-1. **Layout Complexity**: Different layouts might conflict with existing entry content container sizing
-2. **Media Loading**: Complex media components might impact performance
-3. **Mobile Responsiveness**: Desktop-optimized layouts might break on mobile
-4. **Bundle Size**: Adding multiple layout components could increase bundle size
-5. **Component Dependencies**: Shared components might have circular dependencies
-
-### Mitigation Strategies
-
-1. **Container Isolation**: Use CSS containment and absolute positioning where needed
-2. **Lazy Loading**: Implement code splitting for layout components
-3. **Mobile-First**: Design mobile layouts first, then enhance for desktop
-4. **Bundle Analysis**: Use webpack-bundle-analyzer to monitor size impact
-5. **Dependency Management**: Clear component hierarchy and shared utilities in separate files
-
-### Rollback Strategy
-
-- Feature flag implementation to toggle between old and new layouts
-- Gradual rollout by `FeedViewType` (start with least-used types)
-- Database flag to disable adaptive layouts per user preference
-
-## Additional Considerations
-
-### Accessibility
-
-- Ensure all layouts maintain proper heading hierarchy
-- Video players must support keyboard navigation
-- Image carousels need proper ARIA labels
-- Screen reader compatibility across all layouts
-
-### i18n Support
-
-- All new text elements properly localized
-- Layout adjustments for RTL languages
-- Consistent translation keys across layouts
-
-### Future Extensibility
-
-- Audio layout placeholder implementation
-- Plugin system for custom layout types
-- Theme system integration for layout variants
-
-## Confidence Score: 9/10
-
-This PRP provides a comprehensive implementation approach with:
-
-- ✅ **Detailed codebase analysis**: Complete understanding of existing patterns and architecture
-- ✅ **Proven patterns**: Leveraging successful entry list item layouts
-- ✅ **Factory pattern**: Clean, extensible architecture for layout selection
-- ✅ **External research**: Best practices from social media layout implementations
-- ✅ **Existing components**: Reusing proven media handling components
-- ✅ **Clear implementation path**: Phased approach with specific file references
-- ✅ **Risk mitigation**: Identified potential issues with concrete solutions
-- ✅ **Executable validation**: Specific testing steps and success criteria
-
-High confidence is justified because:
-
-1. **Existing foundation**: Entry list items already demonstrate successful adaptive patterns
-2. **Component reuse**: Media components (`SwipeMedia`, `PreviewMediaContent`) are proven
-3. **Clear architecture**: Factory pattern is well-established in the codebase
-4. **External validation**: Research confirms best practices align with proposed approach
-5. **Minimal breaking changes**: Articles maintain existing layout, reducing regression risk
-
-The main implementation involves connecting existing successful patterns rather than building entirely new systems, significantly reducing complexity and risk.
diff --git a/PRPs/adaptive-entry-layouts-fixes.md b/PRPs/adaptive-entry-layouts-fixes.md
deleted file mode 100644
index 5efef6b4c..000000000
--- a/PRPs/adaptive-entry-layouts-fixes.md
+++ /dev/null
@@ -1,530 +0,0 @@
-# PRP: Fix Adaptive Entry Content Layout Issues
-
-## Overview
-
-Fix specific layout and functionality issues in the existing adaptive entry content layouts implemented in `PRPs/adaptive-entry-content-layouts.md`. The adaptive layouts are working but have implementation issues that affect user experience across Social Media, Pictures, and Videos layouts.
-
-## Current Issues Analysis
-
-### Current Implementation Status
-
-The adaptive layout factory system is successfully implemented:
-
-- **Factory System**: `getEntryContentLayout()` in `layouts/factory.ts` correctly routes to layout-specific components
-- **Layout Components**: SocialMediaLayout, PicturesLayout, VideosLayout, ArticleLayout are created
-- **Integration**: `AdaptiveContentRenderer` in `EntryContent.tsx` properly uses the factory pattern
-
-### Specific Issues Identified
-
-#### 1. Social Media Layout Issues
-
-**File**: `apps/desktop/layer/renderer/src/modules/entry-content/components/layouts/SocialMediaLayout.tsx`
-
-**Problem 1**: Duplicate Author Display
-
-- Lines 47-54: Shows `AuthorHeader` with avatar (48px size)
-- Lines 58-62: Shows another `AuthorHeader` without avatar
-- **Result**: Author name appears twice in the layout
-
-**Problem 2**: Show More Button Logic Still Present
-
-- Lines 40-42: Uses `autoExpandLongSocialMedia` setting to conditionally show `CollapsedSocialMediaItem`
-- Lines 96-143: `CollapsedSocialMediaItem` implements "show more" button with LRU cache
-- **User Request**: Remove this logic entirely and force full display
-
-**Problem 3**: AI Summary Position
-
-- Line 87: `` is at the bottom of the content
-- **User Request**: Move AI summary to the top of the layout
-
-#### 2. Pictures Layout Issues
-
-**File**: `apps/desktop/layer/renderer/src/modules/entry-content/components/layouts/PicturesLayout.tsx`
-
-**Problem**: Mixed Media and Text Content
-
-- Current implementation uses `SwipeMedia` for carousel but doesn't follow "PreviewMediaContent logic"
-- Text content mixed with multimedia content
-- **User Request**: Separate multimedia content (using PreviewMediaContent) from text content
-
-#### 3. Videos Layout Issues
-
-**File**: `apps/desktop/layer/renderer/src/modules/entry-content/components/layouts/VideosLayout.tsx`
-
-**Problem 1**: VideoPlayer Using Mini Player
-
-- VideoPlayer component (`shared/VideoPlayer.tsx` lines 56-71) creates both `miniIframeSrc` and `iframeSrc`
-- Lines 129-133: Uses `miniIframeSrc` for preview/hover (optimized for small sizes)
-- **User Request**: Use `iframeSrc` directly for better large-screen experience
-
-**Problem 2**: Content Duplication
-
-- `ContentBody` component (lines 61-66) renders with `noMedia={false}` by default
-- This includes images/iframes in text content that duplicate what's shown in video player
-- **User Request**: Remove multimedia elements from text content, show only text
-
-## Proposed Solutions
-
-### 1. Social Media Layout Fixes
-
-#### 1.1 Fix Duplicate Author Display
-
-Remove the separate avatar display and use single AuthorHeader with proper positioning:
-
-```typescript
-// Current problematic structure (lines 45-62):
-
- {/* Avatar */}
-
-
-
- {/* Content */}
-
-
- // ... rest of content
-
-
-
-// Fixed structure - single author header:
-
-
-
-
- // ... content follows
-
-
-```
-
-#### 1.2 Remove Show More Logic
-
-Replace conditional wrapper with direct content display:
-
-```typescript
-// Remove lines 40-42 autoExpandLongSocialMedia logic
-// Remove lines 96-143 CollapsedSocialMediaItem component entirely
-
-// Replace EntryContentWrapper usage (lines 66-73) with direct ContentBody:
-
-```
-
-#### 1.3 Move AI Summary to Top
-
-Reorder components to show AI Summary after author header:
-
-```typescript
-
-
- {textContent} {/* Separated text content */}
-
-
-
- )
-}
-```
-
-### 3. Videos Layout Fixes
-
-#### 3.1 Use Full-Size iframe Instead of Mini Player
-
-Modify VideoPlayer to use `iframeSrc` directly for large-screen optimization:
-
-```typescript
-// In VideosLayout.tsx, pass preferFullSize prop to VideoPlayer:
-
-
-// In shared/VideoPlayer.tsx, modify to respect preferFullSize:
-export const VideoPlayer: React.FC = ({
- preferFullSize = false,
- ...props
-}) => {
- const displaySrc = preferFullSize ? iframeSrc : miniIframeSrc
-
- return (
-
- {displaySrc ? (
-
- ) : (
- // Fallback to media preview
- )}
-
- )
-}
-```
-
-#### 3.2 Filter Media from Text Content
-
-Create text-only version of ContentBody by adding `noMedia` prop:
-
-```typescript
-// In VideosLayout.tsx (lines 61-66), add noMedia={true}:
-
-
-// ContentBody.tsx already supports noMedia prop (line 49)
-// This will filter out multimedia elements from HTML content
-```
-
-## Implementation Tasks
-
-### Phase 1: Social Media Layout Fixes
-
-#### Task 1.1: Fix Duplicate Author Headers
-
-**File**: `SocialMediaLayout.tsx`
-
-- Remove duplicate AuthorHeader components (lines 47-54 and 58-62)
-- Use single FeedIcon + AuthorHeader pattern from original social-media-item.tsx
-- Maintain proper spacing and styling
-
-#### Task 1.2: Remove Show More Logic
-
-**File**: `SocialMediaLayout.tsx`
-
-- Remove `autoExpandLongSocialMedia` usage (lines 40-42)
-- Delete `CollapsedSocialMediaItem` component entirely (lines 96-143)
-- Replace `EntryContentWrapper` with direct `ContentBody` usage
-
-#### Task 1.3: Reorder AI Summary Position
-
-**File**: `SocialMediaLayout.tsx`
-
-- Move `` from line 87 to after AuthorHeader
-- Add appropriate spacing and styling for top position
-
-### Phase 2: Pictures Layout Enhancement
-
-#### Task 2.1: Implement PreviewMediaContent Integration
-
-**File**: `PicturesLayout.tsx`
-
-- Import and use `usePreviewMedia` hook
-- Replace SwipeMedia carousel with clickable preview that opens PreviewMediaContent modal
-- Separate multimedia and text content rendering
-
-### Phase 3: Videos Layout Enhancement
-
-#### Task 3.1: Update VideoPlayer for Large Screen
-
-**File**: `shared/VideoPlayer.tsx`
-
-- Add `preferFullSize` prop to use `iframeSrc` instead of `miniIframeSrc`
-- Implement proper responsive design for large screens
-
-#### Task 3.2: Filter Text Content
-
-**File**: `VideosLayout.tsx`
-
-- Update ContentBody usage to include `noMedia={true}` prop
-- Ensure multimedia elements are filtered from text display
-
-### Phase 4: Testing and Validation
-
-#### Task 4.1: Layout Validation
-
-- Test each layout with various entry types
-- Verify author information displays correctly
-- Confirm media handling works as expected
-- Test responsive behavior on different screen sizes
-
-#### Task 4.2: Integration Testing
-
-- Verify factory pattern still routes correctly
-- Test layout switching between different entry types
-- Confirm no regressions in ArticleLayout
-
-## Context & References
-
-### Existing Codebase Components
-
-#### Key Files to Modify
-
-- `SocialMediaLayout.tsx` - Main fixes for duplicate author and show more logic
-- `PicturesLayout.tsx` - PreviewMediaContent integration
-- `VideosLayout.tsx` - Full-size iframe and text filtering
-- `shared/VideoPlayer.tsx` - preferFullSize prop support
-- `shared/ContentBody.tsx` - Already supports noMedia prop
-
-#### Key Files to Reference
-
-- `social-media-item.tsx` - Original social media layout pattern (single author header)
-- `PreviewMediaContent.tsx` - Modal-based media preview with sidebar support
-- `AuthorHeader.tsx` - Shared author display component
-- `MediaGallery.tsx` - Media display patterns
-
-### External Best Practices
-
-#### Responsive iframe Guidelines
-
-- **Modern CSS Approach**: Use `aspect-ratio: 16/9` for responsive video containers
-- **Large Screen Optimization**: Implement max-width constraints to prevent oversized displays
-- **Performance**: Use appropriate iframe sources based on screen size and context
-
-**Reference**: https://blog.logrocket.com/best-practices-react-iframes/
-**Reference**: https://cloudinary.com/guides/video-effects/responsive-video-embedding-embed-video-iframe-size-relative-to-screen-size
-
-#### HTML Content Filtering
-
-- **Text Extraction**: Use `noMedia` flags to filter multimedia elements from HTML content
-- **DOM-based Filtering**: Leverage existing HTML processing to remove specific tags
-- **Content Separation**: Maintain clear separation between multimedia and text content
-
-**Reference**: Server-side content filtering approaches for media removal
-**Reference**: https://www.bookstack.cn/read/crawl4ai-0.4-en/dcca2e8c0a744b29.md
-
-### UI Reference Patterns
-
-#### Social Media Layout
-
-- **Single Author Header**: Follow Twitter-like pattern with avatar + name + handle + timestamp
-- **Content Flow**: Author → AI Summary → Text Content → Media Gallery
-- **No Collapse Logic**: Display full content without truncation in content view
-
-#### Pictures Layout
-
-- **Modal Preview**: Use PreviewMediaContent for sophisticated media viewing
-- **Sidebar Metadata**: Article-like sidebar with text content separate from media
-- **Click to Preview**: Simple click interaction to open full preview modal
-
-#### Videos Layout
-
-- **Full-Size Player**: Use appropriate iframe source for screen size
-- **Text-Only Content**: Filter multimedia from description to avoid duplication
-- **Standard Flow**: Video Player → Title → Author → Description (text only) → AI Summary
-
-## Validation Gates
-
-### Code Quality
-
-```bash
-# TypeScript validation
-pnpm run typecheck
-
-# Linting validation
-pnpm run lint:tsl
-pnpm run lint
-
-# Format validation
-pnpm run format
-
-# Build validation
-pnpm run build:web
-```
-
-### Functional Testing Checklist
-
-#### Social Media Layout
-
-- [ ] Author name appears only once (not duplicated)
-- [ ] Author header shows avatar, name, handle (if Twitter), and timestamp
-- [ ] AI summary appears at the top, below author header
-- [ ] Content displays in full without "show more" button
-- [ ] Media gallery displays correctly below content
-- [ ] Layout matches original social-media-item.tsx patterns
-
-#### Pictures Layout
-
-- [ ] Multimedia content separated from text content
-- [ ] Clicking images opens PreviewMediaContent modal
-- [ ] Sidebar displays text content with proper overflow handling
-- [ ] Author header displays in sidebar
-- [ ] AI summary appears in sidebar text content area
-
-#### Videos Layout
-
-- [ ] Video player uses full-size iframe (not mini version)
-- [ ] Video player displays properly at large screen sizes
-- [ ] Text content below video contains no duplicate images/media
-- [ ] Author information displays below video
-- [ ] AI summary appears at bottom of text content
-
-### Performance Validation
-
-- [ ] No layout shift when switching between entry types
-- [ ] Video iframe loads appropriately for screen size
-- [ ] PreviewMediaContent modal opens smoothly
-- [ ] Text content filtering doesn't impact render performance
-- [ ] No memory leaks with modal-based media preview
-
-### Responsive Design
-
-- [ ] All layouts adapt properly to mobile screens
-- [ ] Video player maintains aspect ratio across screen sizes
-- [ ] Pictures sidebar stacks properly on narrow screens
-- [ ] Social media layout remains readable on all devices
-
-## Success Criteria
-
-### Primary Objectives
-
-- [ ] **Social Media**: Single author header, AI summary at top, no show more button
-- [ ] **Pictures**: PreviewMediaContent integration, separated multimedia/text content
-- [ ] **Videos**: Full-size iframe player, text-only content descriptions
-- [ ] **All Layouts**: Maintain existing functionality while fixing specific issues
-
-### Quality Standards
-
-- [ ] Zero regression in ArticleLayout functionality
-- [ ] Factory pattern continues to work seamlessly
-- [ ] All existing media handling features preserved
-- [ ] Mobile responsive design maintained across layouts
-- [ ] Performance impact minimal (under 5% bundle increase)
-
-### User Experience Goals
-
-- [ ] Cleaner social media content display without duplication
-- [ ] Better large-screen video viewing experience
-- [ ] Sophisticated image preview with PreviewMediaContent modal
-- [ ] Consistent author information display patterns
-- [ ] Improved content organization with AI summaries positioned logically
-
-## Risk Mitigation
-
-### Potential Issues
-
-#### Component Dependencies
-
-**Risk**: Changes to shared components (VideoPlayer, ContentBody) could affect other areas
-**Mitigation**:
-
-- Add new props with default values to maintain backward compatibility
-- Test all existing entry list item displays
-- Use feature flags if needed for gradual rollout
-
-#### PreviewMediaContent Integration
-
-**Risk**: Modal-based media preview might conflict with existing modal systems
-**Mitigation**:
-
-- Test modal stacking behavior thoroughly
-- Ensure proper cleanup of modal state
-- Verify keyboard navigation continues to work
-
-#### Performance Impact
-
-**Risk**: Additional modal components and media filtering might impact performance
-**Mitigation**:
-
-- Implement lazy loading for PreviewMediaContent modal
-- Use React.memo for expensive components
-- Profile render performance before and after changes
-
-### Rollback Strategy
-
-- Maintain existing layout components as backup
-- Use git feature branches for each layout fix
-- Implement progressive enhancement approach
-- Test each layout individually before combining changes
-
-## Additional Considerations
-
-### Accessibility
-
-- Ensure all interactive elements have proper ARIA labels
-- Maintain keyboard navigation for new modal interactions
-- Preserve screen reader compatibility for author headers
-- Test video player controls with assistive technologies
-
-### i18n Support
-
-- All new text elements properly localized
-- Layout adjustments tested with longer text languages
-- RTL language support maintained
-- Consistent translation keys across layout components
-
-### Future Extensibility
-
-- Pattern established for other media types (Audio layout)
-- Plugin system compatibility maintained
-- Theme system integration preserved
-- Component reusability across different layout contexts
-
-## Confidence Score: 9/10
-
-This PRP provides a comprehensive fix approach with:
-
-- ✅ **Specific Issue Analysis**: Detailed examination of exact problems and file locations
-- ✅ **Targeted Solutions**: Precise fixes for each identified issue without over-engineering
-- ✅ **Existing Pattern Leverage**: Uses proven components and patterns already in codebase
-- ✅ **External Research**: Incorporates best practices for responsive video and content filtering
-- ✅ **Implementation Roadmap**: Clear phase-based approach with specific file changes
-- ✅ **Risk Management**: Identified potential issues with concrete mitigation strategies
-- ✅ **Comprehensive Testing**: Detailed validation gates and success criteria
-- ✅ **Backward Compatibility**: Maintains existing functionality while implementing fixes
-
-High confidence because:
-
-1. **Focused Scope**: Addresses specific reported issues without unnecessary system changes
-2. **Proven Components**: Leverages existing PreviewMediaContent, AuthorHeader, and ContentBody components
-3. **Pattern Following**: Mimics successful patterns from social-media-item.tsx and other working components
-4. **External Validation**: Research confirms best practices for responsive video and content filtering
-5. **Minimal Risk**: Changes are contained to specific layout files with clear rollback options
-
-The implementation primarily involves connecting existing working components in better ways rather than building new complex systems, significantly reducing implementation complexity and risk.
diff --git a/PRPs/ai-summary-chat-integration.md b/PRPs/ai-summary-chat-integration.md
deleted file mode 100644
index 43d10cc90..000000000
--- a/PRPs/ai-summary-chat-integration.md
+++ /dev/null
@@ -1,735 +0,0 @@
-# PRP: AI Summary Chat Integration for Enhanced User Engagement
-
-## Overview
-
-Transform the AI chat interface from a static welcome screen to a context-aware, engagement-focused experience by integrating AI summary as initial content. This enhancement automatically displays relevant entry summaries when users open the AI chat panel, providing zero-friction conversation starters and increasing AI feature adoption through progressive disclosure patterns.
-
-## Current Implementation Analysis
-
-### Current Chat Interface Architecture
-
-**File**: `apps/desktop/layer/renderer/src/modules/ai-chat/components/layouts/ChatInterface.tsx`
-
-**Current Flow**:
-
-```typescript
-// Conditional rendering based on message state
-{!hasMessages && !isLoadingHistory ? (
-
-) : (
-
-
- {(status === "submitted" || status === "streaming") && }
-
-)}
-```
-
-**WelcomeScreen Structure** (`WelcomeScreen.tsx`):
-
-```typescript
-// Current static welcome screen
-