How kuluruvineeth/silent-coder works
Project type and purpose
• This is a desktop application built on Electron, combining a Node.js “main” process with a React/TypeScript “renderer” process.
• Its purpose is to let users take screenshots, process them, and present results via a modern UI.
File structure
• Top-level:
• build/, electron-builder.yml, notarize.js → packaging and notarization for macOS/Windows/Linux
• src/main → Electron Main process code (app startup, IPC, config, screenshot & processing managers, keyboard shortcuts)
• src/preload → Preload script to safely expose Main-process APIs to the Renderer
• src/renderer → React-based UI (Vite-powered, TSX components, styling, providers for state/queries)
• Config files: tsconfig.*, electron.vite.config.ts, ESLint & Prettier configs, package.json + pnpm-lock.yaml.
README
• Confirms it’s an Electron + React + TypeScript app.
• Shows standard pnpm scripts for dev and build across OS targets.
a. Electron Main Process
• ConfigManager (loads/saves settings)
• ScreenshotManager (captures screen)
• ProcessingManager (runs algorithmic work on images)
• IpcHandler (routes IPC calls)
• KeyboardShortcut manager (global hotkeys)
b. Preload Script
• Exposes a typed API surface via contextBridge to the Renderer
c. Renderer Process (React UI)
• Components (App, Queue, ScreenshotsView, SettingsDialog, Debug panels)
• Providers (QueryProvider, ToastProvider)
• Assets & Stylesheets
d. System/OS Layer
• File system, native OS screenshot & shortcut APIs
e. Build/Packaging Layer
Relationships & data flow
• User clicks UI → React component calls window.api.* (preload) → IPC → Main Process
• Main Process executes native operations (e.g., take screenshot) → returns result via IPC → Renderer updates UI
• Settings changes in UI → API call → ConfigManager persists to disk
• Processing tasks may spawn child processes or threads (if implemented in ProcessingManager)
Architectural patterns & principles
• Layered Separation: UI (Renderer) ↔ IPC boundary (Preload) ↔ System logic (Main) ↔ OS
• Single Responsibility per module (each manager handles one domain)
• Typed contracts (TypeScript definitions in preload and renderer env.d.ts)
• Event-driven communication via Electron’s IPC
Technologies & frameworks
• Electron (main + renderer)
• Vite (fast bundling for renderer)
• React + TypeScript (UI)
• PNPM (package management)
• electron-builder (packaging & code signing)
• ESLint, Prettier (code quality)