saipenlisted
Install: claude install-skill vacterro/saipen
# saipen -- skill adapter
Thin entry for skill-reading platforms. The system lives elsewhere:
1. **Read `BOOT.md`** (the file in the same folder as this SKILL.md) -- the
compact cold-start kernel: STATE -> BOARD -> LOG tail -> execute
`next_action`. That is everything a bare `saipen continue` needs. **Read it
once; this list names it once.**
2. **`BOOT.md` loads `STYLE.md` before any output** -- voice governs the first
token, so the kernel's own step 1 opens it. Nothing here overrides that
order.
3. **Rule question? Route through `INDEX.md`** (same folder), the document map.
4. **`CORE.md` only for the exact rule you looked up.** It is the constitution;
do not read it speculatively.
5. **`RFC.md` is a compatibility redirect and nothing else.** It holds no
rules, it is not a destination, and no step above sends you there.
6. **Phase modules in `phases/`** (same folder) -- loaded by boot per STATE.md
phase.
7. UI work: also read `UI.md` (Win95 dark golden, Verdana, no AA).
Platform notes:
- Native task lists mirror `.saipen/BOARD.md`, never replace it.
- `<project_root>/.saipen/` remains the only project memory/checkpoint area.
Global USERPERSON lives in the deterministic user-configuration directory
(`SAIPEN_USER_CONFIG_HOME` override or platform default), never in `.saipen/`
or `saipen_home`; it cannot bootstrap or become an ancestor project root.
- Prefer file tools over shell redirects -- UTF-8 no BOM.
- CORE.md decides. No rule here overrid