# Life Setup

> Use when installing Personal OS into a notes vault or remapping folders — produces a vault config mapping layout roles to the user's paths without forced renames.

- Skill: `jayden-dang/life-setup` (Agent Skill, multi-file: 13 files)
- Install (CLI): `npx skillmds@latest add jayden-dang/life-setup`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jayden-dang/life-setup/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: jayden-dang (https://skillmd.com/u/jayden-dang)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/jayden-dang/life-setup

---


# Setup Personal OS

User-invoked. Do not auto-start bulk moves.

## Role

REQUIRED: read sibling `ROLE.md` (secretary default, grant rule, hybrid ban, config paths).


## Goal

A working **config** file that maps logical roles → this vault's real folders, plus optional template seeds.

## Templates

From package `templates/personal-os/`. Resolve pack seeds in this order, first path that exists: (1) `templates/` beside this SKILL.md, (2) `${CLAUDE_PLUGIN_ROOT}/templates` when that variable is set, (3) `../../../templates` relative to this SKILL.md. If missing, create minimal stubs — do not invent a second layout system.

## Steps

1. Detect top-level dirs (any PARA/journal/inbox style).
2. Propose `layout:` table: role → **their** path.
3. Show recommended tree as **suggestion only** (package README).
4. One decision: keep names vs adopt recommended.
5. Write config **only after explicit OK**.
6. Create dirs / migrate **only** with confirmation.
7. Seed empty registry + optional templates.
8. Optional `roots.*` — only paths the user states.
9. Do not auto-register disk repos as projects.
10. Re-read the written config: confirm it parses and every `layout:` role points to a dir that exists.
11. Name the next skill for the user to run — `life-charter` if no charter exists, else `life-open-project`.

## Red Flags — Never

- Bulk rename without consent  
- Delete notes  
- Invent machine-specific paths  

## Done when

Config parses and every role under `layout:` maps to a path that exists; registry
seeded; `life-charter` or `life-open-project` named to the user as the next step.