[OPS] Route LifeOS work — today brief, week skeleton, personal OS setup —
to the LifeOS project. Use when the user says "LifeOS", "life OS",
"personal OS", "what's today", "morning OS", or "set up LifeOS".
Installs into .claude/skills of the current project.
Are you the author of Lifeos?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/edagher92-coder-lifeos)
---
name: lifeos
description: |
[OPS] Route LifeOS work — today brief, week skeleton, personal OS setup —
to the LifeOS project. Use when the user says "LifeOS", "life OS",
"personal OS", "what's today", "morning OS", or "set up LifeOS".
---
# LifeOS — load the right repo
LifeOS is Elie's personal operating system. It is **not** this father repo
and it is **not** Snow Flow HQ.
## Where the work lives
1. **After extract:** open `edagher92-coder/LifeOS` alone. Run `/lifeos-today`
or `/lifeos-week` there.
2. **Until that GitHub repo exists:** the seed is `lifeos/` in
`edagher92-coder/.github`. Work there, then follow `lifeos/EXTRACT.md`.
Do not copy LifeOS procedures into brand repos. Do not invent cash, overdue,
prices, or dates. Money snapshots stay owned by `Claude-code-` (`/money-snapshot`).
Health stays owned by `VitalSignalResearch`.
## If the user asked to set up the repo
The seed, project-map entry, and sync list are the father-side setup. Creating
`edagher92-coder/LifeOS` on GitHub is a human step (private repo + Cursor
GitHub App Contents write). This skill does not create GitHub repositories.
