How mitskiyu/capycut works
Project type and purpose
• It is not a client-server or multi-tier web app; it’s a desktop command-line/GUI tool that interacts with the Steam installation and the Windows file system.
File structure
• Top-level files:
• build.lua – build script
• src/main.cpp – entry point
• src/shortcut.cpp/.hpp – shortcut-generation logic
• src/steam.cpp/.hpp – Steam-integration logic
• No frontend/backend split: everything lives in one codebase.
• No database, no web APIs, no microservices.
README for additional insights
• Confirms Windows-only support.
• Outputs to Start Menu\Programs\Capycut.
a. Main components:
• User Interface (CLI or minimal GUI wrapper in main.cpp)
• Core Application Logic
• Steam Integration Module (steam.cpp/.hpp)
• Shortcut Generation Module (shortcut.cpp/.hpp)
• Windows File System / Start Menu Target
• Build System (Lua script, optional)
b. Relationships and interactions:
1. User invokes capycut.exe (UI) →
2. UI calls Core Logic →
3. Core Logic queries Steam Integration Module for installed games →
4. Core Logic passes game metadata to Shortcut Generation Module →
5. Shortcut Module writes .lnk files into the Windows Start Menu folder via Windows Shell API →
6. UI reports success/failure to the user.
c. Architectural patterns or design principles:
• Single executable; layered within: presentation (main.cpp) → domain (steam + shortcut modules) → infrastructure (Windows API).
• Separation of concerns: Steam data retrieval separated from .lnk file creation.
d. Key technologies/frameworks/libraries:
• C++17 (or later)
• Windows Shell COM interfaces for link creation
• Steam’s local config files or registry for game enumeration
• Lua build script (build.lua)
Detailed breakdown
• Middle tier: “Core Application” package containing two sub-packages: Steam Integration and Shortcut Generation
• Right side: two external targets:
• “Local Steam Installation / Registry”
• “Windows Start Menu Folder”