Skip to content

Latest commit

 

History

History
67 lines (52 loc) · 3.64 KB

File metadata and controls

67 lines (52 loc) · 3.64 KB

PRD: Project Omnitool

Status: Alpha (v0.2.0) | Author: Principal PM | Date: March 21, 2026

1. Executive Summary

Omnitool is a high-performance, cross-platform, privacy-first developer utility hub. Built on Tauri/Rust, it provides native-level speed on Windows, macOS, and Linux. It features a unique Omni-Chain™ engine that allows users to pipe transformations together natively in Rust, avoiding the overhead and privacy risks of web-based tools.

2. Target Personas

  1. The Privacy-Conscious Dev: Works in regulated industries (FinTech/Health). Refuses to use web-based formatters.
  2. The Cross-Platform Power User: Switches between a Linux workstation and a MacBook. Needs tool parity and synced configurations.
  3. The Data Engineer: Needs to inspect and convert binary formats like Parquet without complex local setups.

3. Problem Statement

  • Privacy Risks: Developers frequently paste sensitive data (JWTs, JSON logs) into untrusted web formatters.
  • Performance: Browser-based tools often hang or crash when processing large datasets (10MB+ JSON/CSV).
  • Platform Fragmentation: Native tools are often macOS-only; Windows/Linux alternatives are usually clunky web-wrappers.

4. Goals & Success Metrics (KPIs)

  • Performance: App launch to "Ready for Input" in < 400ms. (Achieved)
  • Efficiency: RAM usage < 150MB during idle state. (Achieved)
  • Privacy: Zero outbound network calls. (Achieved)
  • Behavioral Coverage: 80%+ coverage focused on user-critical paths. (In Progress)

5. Functional Requirements

5.1 Core Utility Engine (v0.2.0 Status: ✅)

  • Smart Detection: Real-time clipboard monitoring with automatic tool suggestion ("Magic Suggestion").
  • Native Tools: 12+ high-performance tools (JSON, Base64, JWT, SQL, Parquet, etc.).
  • Offline First: All transformations happen locally on-device via Rust.

5.2 The "Omni-Chain" (v0.2.0 Status: ✅)

  • Rust Pipeline: Multi-step tool chains are executed natively in a single Rust pass to minimize IPC latency.
  • UI Workflow: Users can add and remove steps in a visual workspace with real-time feedback.

5.3 Local AI Integration (Planned)

  • Local LLM Interface: Integration with Ollama.
  • Natural Language Transformation: "Convert this list of CSV emails into a JSON array."

5.4 Plugin Architecture (Planned)

  • JavaScript Sandbox: Allow users to define custom transformations in a secure sandbox.

6. Non-Functional Requirements

  • Aesthetics: Support for Dark and Light modes with a persistent design system. (Achieved)
  • Stability: Red-Green TDD enforced for all mathematical and transformation logic.
  • UX: Keyboard-centric navigation via Command Palette (⌘K). (Achieved)

7. The Roadmap

Phase 1: Foundation (COMPLETED)

  • Tauri core with 10+ essential tools.
  • Smart clipboard detection.
  • Dark/Light Mode support.

Phase 2: Power Tools & Data (v0.2.0 - CURRENT)

  • Parquet Suite: Native inspection and conversion using Polars.
  • SQL Formatter: Integrated native prettifier.
  • SEO Landing Pages: Public-facing documentation for all tools.

Phase 3: intelligence & Ecosystem (Upcoming)

  • Local LLM connector (Ollama support).
  • Plugin Sandbox (JS/WASM).
  • CLI companion tool.

8. Risks & Mitigations

  • Risk: Binary size increases with heavy crates like Polars.
  • Mitigation: Use conditional compilation and LTO (Link Time Optimization) to keep binary size under 50MB.
  • Risk: macOS security gatekeeper blocks unsigned builds.
  • Mitigation: Clear documentation for bypass and upcoming notarization implementation.