the shape of it
How it works
A rule is three parts, a skill is a stack of them, and nothing reaches your repository until you say so.
what a rule is
Three parts, always
An instruction you can check, the failure it prevents, and where it stops applying.
how it behaves
Nothing is written without asking
It reads your project, proposes, and waits. Everything it does is reviewable and reversible.
- 01
It proposes
scan prints what it matched, what it ruled out, and the token cost. It writes nothing.
- 02
You confirm
nothing lands until you say so. --yes exists, for scripts that already know.
- 03
It is recorded
skyl.lock holds a hash of every file, so a reinstall is no diff and a pull request shows exactly what moved.
- 04
It is reversible
remove takes layers back out, and refuses to orphan one that another still needs.
$ skyl add compose
android/core required by another skill
android/compose
3 skills, ~5,500 tokens into .claude/skills
Write them? [y/N] y
Done. Recorded in skyl.lock.
shortcuts
Or take a known shape
core · kotlin · compose · mvvm
4 layers · ~6,300 tokensA legacy codebasecore · java · xml · mvvm
4 layers · ~7,200 tokensAn app with a backendcore · kotlin · networking · db · security
5 layers · ~8,900 tokensA media-heavy appcore · kotlin · compose · images · permissions
5 layers · ~8,100 tokensA team adding testscore · kotlin · testing · di
4 layers · ~5,800 tokensEvery android skillcompose · core · db · di · images · java · kotlin · mvvm · networking · permissions · security · testing · xml
13 layers · ~20,200 tokens