How nukeop/nuclear works
Main Application Components (Top Level)
• Frontend (Electron Renderer Process)
• Backend (Electron Main Process)
• Core Services
• External APIs/Services
Frontend Layer
• React Components (/packages/app/app/components)
• Redux Store (/packages/app/app/store)
• UI Components Library (/packages/ui)
• State Management
• Actions (/packages/app/app/actions)
• Reducers (/packages/app/app/reducers)
• Selectors (/packages/app/app/selectors)
Backend Layer
• Main Process Services (/packages/main/src/services)
• HTTP Server
• IPC Communication
• System API
• Local Library Scanner
• Download Manager
• Discord Integration
• Configuration Management
Core Services Layer (/packages/core)
• Plugin System
• Stream Providers (YouTube, SoundCloud, etc.)
• Lyrics Providers
• Metadata Providers
• REST Clients
• Last.fm
• Discogs
• Spotify
• YouTube
• Local File Management
• Settings Management
Data Flow
• IPC communication between frontend and backend
• API calls to external services
• Plugin system interactions
• State management flow
• Event handling paths
External Services Integration
• Streaming Sources
• YouTube
• Jamendo
• Audius
• SoundCloud
• Metadata Sources
• Last.fm
• Discogs
• Lyrics Services
• SponsorBlock Integration
Additional Elements
• Database/Storage (Local library, playlists)
• Configuration Management
• Plugin Architecture
• Security Boundaries
• Error Handling Flow
Key Architectural Patterns to Highlight:
• Event-driven architecture (IPC communication)
• Plugin-based system for extensibility
• Redux for state management
• Service-oriented architecture for backend services
• Component-based UI architecture
• Component types
• Data flow directions
• Critical paths
• Integration points
Data flow patterns
This will provide a clear understanding of Nuclear's architecture while maintaining the right level of detail for a principal software engineer to understand the system's components and their interactions.