lykke.day

AI experiment + work in progress
This repository is actively changing and may break at any time.
It is an experiment in two directions:

1. Developing software with AI (LLM-first workflows, human direction/review).
2. Building products on top of LLMs that are ethical, practical, and genuinely helpful.

What “Lykke” Means

“Lykke” is the Danish/Norwegian word for happiness (or wellbeing).
The name reflects the product goal: helping people structure days that feel meaningful, sustainable, and humane.

What Lykke Is About

Lykke is about intentional daily living: planning your day around what matters, following through with consistency, and reflecting without turning life into hustle metrics.

The project exists to support wellbeing-first productivity. The core idea is simple: a day should feel purposeful and sustainable, not overloaded.

Development Ethos

This repository is intentionally centered on both process and product values.

LLM Development

• LLMs write essentially all production code in this repo.
• Humans set direction, constraints, and review.
• The goal is to learn what workflows, architecture, and guardrails make this approach reliable.
• The product goal is to explore how to build AI-powered tools that are ethical by design and useful in real life.

This means commits may be frequent, structure may shift, and rough edges are expected.

At the architecture level, the backend follows Clean Architecture with CQRS. The codebase is organized into five layers with strict dependency flow:

• core - shared primitives, constants, config, and cross-cutting utilities
• domain - entities, value objects, domain services, and domain events
• application - commands, queries, protocols, and use-case orchestration
• infrastructure - database/repository/gateway implementations and workers
• presentation - FastAPI routes, request/response schemas, and API wiring

Dependency direction is inward: outer layers depend on inner layers, never the reverse.

Current Status

• Not stable
• Not production-ready
• No compatibility guarantees between commits

If you are reading this, treat the project as a live lab notebook rather than a finished product.

Cursor Quick Links

Important Commands

• Add Feature
• Run Tests
• Run Typecheck
• Commit Message

Important Rules

• Backend Architecture
• Python Help
• Events and Audit Logs
• Domain
• Application
• Infrastructure
• Presentation
• Core

Local Development

Prerequisites

• Docker
• Optional: Python 3.14+ with Poetry (only if running backend commands outside Docker)
• Node.js 18+ with npm

Setup

git clone https://github.com/smartfastlabs/lykke.day.git
cd lykke.day

# Backend
cd backend
poetry install
make docker-up
make init-db
make migrate-dev
make serve

# Frontend (new terminal)
cd frontend
npm install
npm run dev

Common Commands

# backend/
make test
make typecheck
make check

# frontend/
npm run test
npm run type-check
npm run lint

Contributing

Contributions are welcome, especially if you are interested in AI-assisted development practices.

Before opening a PR:

1. Run checks (make check in backend/, tests/lint in frontend/)
2. Keep changes small and explicit
3. Add or update tests when behavior changes
4. Document any prompt, workflow, or guardrail improvements

License

GNU Affero General Public License v3.0 (AGPLv3) - see LICENSE.