How phatelot/fehwgc works
Main Application Components
a. Core Application Layer:
• App.svelte as the root component
• Main.ts as the application entry point
b. Feature Modules (Group these in logical containers):
Component Module:
• Character Management (character_chart.svelte, character_popup.svelte)
• Outfit System (outfit_chart.svelte, outfit_popup.svelte)
• Statistics (bmi_chart.svelte, global_stats.svelte)
Business Logic Module:
• State Management (state.ts)
• Change Engine (change_engine.ts)
• Donation Engine (donation_engine.ts)
• Metadata Handler (metadata.ts)
Data Flow Layer
• Data Import System (data_import directory)
• Asset Management (asset_utils.ts)
• State Management
• View Models (view_model.ts)
Asset Structure
Static asset organization:
• Public Assets (public directory)
• Character Assets
• Frames
• Traits
Utility Services
Utility functions:
• RNG Service (rng.ts)
• Stats Utilities (stats_utils.ts)
• Weight Utilities (weight_utils.ts)
• General Utilities (utils.ts)
Use these visualization guidelines:
Testing Integration
• Test files (.test.ts) as parallel structures
• Use a different border style for tested components
Build/Deploy Pipeline
• Vite configuration
• GitHub workflow integration
• DevContainer setup
Development Tools
• TypeScript configuration
• Svelte compiler
• Development server
Keep the following in mind:
How assets are managed and utilized
• High-level architecture visibility
• Component relationships
• Data flow patterns
• Development/deployment infrastructure
This will give other developers a clear understanding of:
• How components interact
• Where to find specific functionality
• How data flows through the application
• How the testing infrastructure is organized
• How the build and deployment process works