How fleuristes/fleur works
Based on our analysis of the file tree and README, Fleur is a desktop application marketplace for MCPs. This project leverages a full-stack architecture with a clear separation between the frontend and the backend. The frontend is implemented in React/TypeScript (under the “src” directory) and the backend is built with Rust using Tauri (found in “src-tauri”). Additionally, the project makes use of Bun as a package manager and build runner for the Node.js/Yarn ecosystem, while Rust and Cargo handle the backend dependencies.
• Frontend: Represented by the “src” directory, which contains React/TypeScript components, routes, store, and types. This is responsible for the User Interface, application state management, and client-side interactions.
• Tauri Backend: Identify the “src-tauri” directory, which holds all Rust code such as main.rs, lib.rs, and various modules (like clients, file_utils, environment). This layer handles system calls, communicates with the OS, and manages application-level operations.
• Build and Configuration Tools: Include Bun (with its package.json, bun.lock, etc.), Tauri configurations (tauri.conf.json), and scripts (e.g., installation, release, test, sign_app).
• App Registry: Although the actual registry is maintained in a separate repository (app-registry), it is a core part of the system functionality and should be represented in the overall design as an external service.
• External Tools & Services: Consider the roles of GitHub workflows (under .github) for testing/CI and other external integrations such as release scripts for signing and packaging.
Establish the interactions and relationships
• How static assets are loaded and served to the frontend.
• Use of external development tools/build scripts (installation, testing, build processes) that contribute to both the frontend and the backend.
Architectural patterns or design principles
• Separation of Concerns: Clearly separate the UI (React) from the system-level operations (Rust/Tauri).
• Modular Design: Note the modular structure within both “src” and “src-tauri” directories, where each concern (UI components, app configurations, utilities, tests) is handled in its dedicated space.
• Extensibility: Represent how the marketplace is designed to be extensible for non-technical users as well as developers (for example, through the app registry integration).
Relevant technologies, frameworks, and libraries
• React/TypeScript for the frontend.
• Rust with Tauri for desktop application logic.
• Bun as a modern package manager/build tool.
• Cargo for Rust dependency management.
• Additional tools such as VS Code (recommended IDE), as well as test frameworks in Rust (cargo test) and Node/Bun for frontend testing.
Suggested elements
• A representation of “External Services/Repositories”, including the “App Registry”, which may interface with the core marketplace.