How giant-heart/recipes works
Main Components
a) User Interface Layer:
• Command Palette (central control mechanism)
• Multiple Writing Surfaces (markdown, poem, plain)
• Help Screen
• Editor Screen
b) Core Application Logic:
• Recipe Engine (manages writing guides)
• State Management
• Storage Handler
c) External Integration:
• File System Interface
• Configuration Management
┌─ UI Components ─────────────────────┐
• ┌─────────┐ ┌────────┐ ┌─────────┐ │
• Command │ │Writing │ │ Help │ │
• Palette │ │Surface │ │ Screen │ │
• ┘ └────────┘ └─────────┘ │
• ┘
┌─ Core Logic ──────────────────────┐
• ┌─────────┐ ┌────────┐ │
• Recipe │ │ State │ │
• Engine │ │Manager │ │
• ┘ └────────┘ │
• ┘
┌─ Storage & Configuration ─────────┐
• ┌─────────┐ ┌────────────────┐ │
• File │ │ Configuration │ │
• System │ │ Manager │ │
• ┘ └────────────────┘ │
• ┘
Important Relationships
• Command flow from Command Palette to Recipe Engine
• Data flow between State Manager and UI Components
• Storage operations between Core Logic and Storage Layer
• Configuration loading path
Technical Stack Indicators
Technology labels:
• ClojureScript as the primary language
• npm for package management
• Local file system integration
• Custom EDN configuration format
Key Design Patterns to Highlight
• Component-based architecture (shown in src/components structure)
• Interface-based design (shown in display and surface interfaces)
• State management pattern
• Export strategy pattern
Remember to:
• Keep the main flow clear and visible
• Version/date information
• Notes about configuration paths
• The inability to edit (write-only nature)
• The recipe-driven writing process
• The export-centric workflow
• The keyboard-based navigation system