How ayfri/atom-clicker-svelte works
High-Level Architecture Components
a) Frontend Application (Svelte-based)
• Client-side rendering
• Component hierarchy (Atomic Design Pattern)
• State management
• Game engine integration
Component Structure (Using Atomic Design)
Components hierarchically:
• Atoms (basic components)
• Molecules (composite components)
• Organisms (complex components)
• Pages/Routes
Core Systems
Create distinct sections for:
• Game Engine System
• State Management System
• Rendering System (PIXI.js integration)
• Save System
• Particle System
Specific Implementation Details
Key relationships:
Game Engine (gameManager.ts)
↓
State Stores (gameStore.ts, protons.ts, etc.)
↓
UI Components (Atom.svelte, Buildings.svelte, etc.)
Component Relationships
Interactions:
• Game loop → State updates → UI renders
• User interactions → State mutations → Game state updates
• Save system ↔ Game state persistence
Data Flow Patterns
Represent:
• Store subscriptions
• Component communication
• Game state updates
• Particle system interactions
Key Elements to Include:
Core Systems
• Game Manager
• Particle System
• Save System
• Canvas Renderer
State Stores
• Game Store
• Protons Store
• Canvas Store
• Window Store
• Toast Store
UI Component Hierarchy
• Atoms (Modal, StatItem, etc.)
• Molecules (Canvas, Counter, etc.)
• Organisms (Atom, Buildings, SkillTree, etc.)
Data Sources
• achievements.ts
• buildings.ts
• currencies.ts
• skillTree.ts
• upgrades.ts
Important Considerations:
Clear boundaries between
• Game logic
• UI components
• State management
• Data configuration
Reactive nature of
• Store updates
• Component rendering
• Game state changes
Interaction patterns
• User input handling
• Game loop updates
• State propagation