- C# 52.5%
- Swift 43.5%
- PowerShell 2.2%
- HTML 1.6%
- Shell 0.2%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
|
|
||
| docs | ||
| eng | ||
| mac | ||
| src | ||
| tests | ||
| .gitignore | ||
| AGENTS.md | ||
| CLAUDE.md | ||
| Directory.Build.props | ||
| notes.md | ||
| README.md | ||
| Tendlore.slnx | ||
| Tendlore_PRD.md | ||
Tendlore
The private home maintenance coach for Windows. Tendlore teaches homeowners what maintenance their home needs, reminds them when to do it, walks them through each task, and keeps a durable local record — no accounts, no cloud, no subscription.
A Volarra product. Product requirements live in Tendlore_PRD.md.
Documentation: see docs/ — architecture, data model, recurrence semantics, content authoring, UI map, and the user guide.
Layout
| Path | What it is |
|---|---|
src/Tendlore.Core |
Domain models, recurrence engine, plain-text YAML store (versioned files, atomic writes), playbook content library, plan generator, backup/CSV/search services. No UI dependencies. |
src/Tendlore.App |
WPF (.NET 10) desktop app — MVVM, first-run wizard, dashboard, plan, binder, ledger, runbook, settings. |
tests/Tendlore.Core.Tests |
xUnit tests: recurrence edge cases, plan generation, store round-trips, backup/restore. |
Build & run
dotnet build Tendlore.slnx
dotnet test Tendlore.slnx
dotnet run --project src/Tendlore.App
User data lives in Documents\Tendlore\ as plain, human-readable YAML files plus an
Attachments folder — inspectable and editable outside the app (see
docs/data-model.md).
Dev conveniences (environment variables):
TENDLORE_DATA_DIR— use a different data directory (demos/tests).TENDLORE_START_VIEW— open straight to a section (plan,areas,history, …).
Content library
Maintenance playbooks are structured data in
src/Tendlore.Core/Content/playbooks.json, embedded in the Core assembly and
versioned with the app (local-first: content updates ship in app updates).
Each playbook carries what/why/where/how, difficulty, time, tools & supplies,
safety notes, hire-a-pro thresholds, steps, done criteria, recurrence
(calendar-anchored or floating), and applicability rules (systems, climates,
household-condition interval overrides).