A personal, local-first web application designed for building and maintaining daily habits. It targets individuals seeking a private, distraction-free tool to track routines through streak tracking, completion rates, and calendar visualization, without requiring any accounts or external services.

How It Works

The application employs a modern stack with a FastAPI backend serving a React frontend. Data is persisted locally using SQLite, ensuring all operations occur on the user's machine. This architecture prioritizes privacy and simplicity, eliminating the need for server-side infrastructure or user accounts, and offering direct API documentation via Swagger UI.

Quick Start & Requirements

• Prerequisites: Python 3.11+ (with uv package manager), Node.js 18+ (with npm).
• Backend Setup: Navigate to backend/, run uv sync, then uv run uvicorn app.main:app --reload --port 8000. API documentation is available at http://localhost:8000/docs.
• Frontend Setup: In a new terminal, navigate to frontend/, run npm install, then npm run dev. The frontend is accessible at http://localhost:5173.
• Access App: Open http://localhost:5173 in a web browser.
• Links: API Docs: http://localhost:8000/docs.

Highlighted Details

• Local-First & Private: Operates entirely on the user's machine with data stored in a local SQLite database; no account creation is necessary.
• Core Features: Supports creating habits, one-click completion, detailed streak tracking, and a visual calendar view of habit history.
• Streak Integrity: Includes a "Planned Absences" feature to allow skipping days without interrupting habit streaks.
• Tech Stack: Backend utilizes Python 3.11, FastAPI, SQLAlchemy, and SQLite. Frontend is built with React 18, Vite, TanStack Query, and Tailwind CSS.

Maintenance & Community

The provided README does not detail specific contributors, sponsorships, or community channels (e.g., Discord, Slack). Mentions of "AI Coding Workshop" and "Claude Commands" suggest a potential link to AI-assisted development workflows or educational contexts, but no direct community engagement platforms are listed.

Licensing & Compatibility

The README does not specify a software license. This omission requires clarification regarding usage rights, modification permissions, and compatibility for commercial or closed-source integration.

Limitations & Caveats

The local-first nature inherently limits data synchronization across devices and lacks cloud backup capabilities. The absence of user accounts means no multi-user or collaborative features are supported. The README mentions a "workshop branch" for templates, implying the main branch might serve a different purpose or be less stable.