How jamiepine/voicebox is laid out, and where to start for common changes.
There is no import map for this report yet.
Where to start reading
Repository root
Repository root
Likely public API
Likely public API
Likely start-up file
Likely start-up file
Suggested starting pointAI
Suggested starting pointAI
Find files for a task
AI
Add a new audio effect to the effects chain
Define the effect parameters in the effects picker by examining existing effects in GenerationPicker.tsx to follow the naming and property conventions
Register the effect in EffectsChainEditor.tsx to add it to the available effects list that users can add to their chain
Create a detail configuration component in EffectsTab/EffectsDetail.tsx to allow users to adjust effect-specific parameters
Add a new settings page to the Server tab
Create a new React component file in app/src/components/ServerTab/ following the pattern of existing pages like GeneralPage.tsx or GpuPage.tsx
Use SettingRow.tsx component to maintain consistent UI styling for setting rows throughout your new page
Connect to backend APIs via ServerSettings components (e.g., ServerStatus.tsx pattern) to fetch and send configuration data
Add voice profile capture method (recording, upload, or system)
Create a new sample capture component in app/src/components/VoiceProfiles/ by extending AudioSampleRecording.tsx, AudioSampleUpload.tsx, or AudioSampleSystem.tsx pattern
Export the component from SampleList.tsx or create a new list variant to show available sample collection methods
Add a new data visualization or status display panel
Build your component using shadcn/ui primitives located in app/src/components/ui/ (e.g., card.tsx, badge.tsx, progress.tsx)
Place your component in the appropriate tab container (e.g., EffectsTab, ModelsTab, VoicesTab) to integrate into existing navigation
Connect to backend data via the ServerTab API pattern to fetch real-time metrics or status information
Use AudioBars.tsx as a reference for animated visualizations if displaying time-series or audio-related data
Change the public API
Trace runtime behavior
Add or update tests
Change build or automation
RepoPilot lists up to 500 files, so a file missing here may still exist.
Files marked “likely” are guessed from their names.
Code quality and hotspots
Largest source files
Branch points72 per file on average
Code issues0 errors, 15 warnings
Largest file1,678 lines
Hotspot load0 high-risk files
Static checks on the 15 largest source files.
Tests, CI and tooling
CIGitHub Actions2 workflows
Tests54 test filesPytest · 0.16 test files per source file (file count, not coverage)
Dependency updatesNo config detected
Test folders: backend/tests · backend/tests/fixtures