@sassywares/skills 0.4.1 → 0.4.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -33,7 +33,7 @@ disable-model-invocation: true
|
|
|
33
33
|
5. **Wire the skills.** The suite is installed from upstream with the open `skills` CLI, which vendors the skill files into the project and pins them. Never copy skill files in by hand, never add the suite as a dependency.
|
|
34
34
|
|
|
35
35
|
- **Install it**: `npx -y skills add sassywares/sassy-skills -y`. That writes `.agents/skills/sassy-*` (real files), per-agent links such as `.claude/skills/sassy-*`, and `skills-lock.json`.
|
|
36
|
-
- **
|
|
36
|
+
- **Do not wire updates.** How and when the project refreshes the suite is the project's decision, not setup's: no `skills:*` scripts, no `postinstall` edit. Mention the commands (`npx skills update`, `npx skills experimental_install`) and stop there.
|
|
37
37
|
- **Commit the vendored skills and the lock.** `.agents/skills/sassy-*` and `skills-lock.json` are the pin; a clone then needs no network.
|
|
38
38
|
- **Ignore `.claude/skills` only.** It is a link created at install time. Create `.gitignore` only when there is none — and in `workspace` topology never touch the project's root `.gitignore` at all.
|
|
39
39
|
- **Write `.sassywares/README.md`** from `assets/sassywares-readme.md` when absent. Never overwrite it — it may carry project notes.
|
|
@@ -54,8 +54,8 @@ disable-model-invocation: true
|
|
|
54
54
|
| Version is reported | Setup names the snapshot version it installed; `--check` flags an installed copy older than the skill's. |
|
|
55
55
|
| Never commit | Setup writes files and stops. Committing is `sassy-commit`. |
|
|
56
56
|
| Skills come from upstream | Install with `npx skills add`; never hand-copy skill files or maintain the links yourself. |
|
|
57
|
-
|
|
|
58
|
-
| Write boundary | Only `.sassywares/`, the vendored `.agents/skills/sassy-*`, `skills-lock.json`,
|
|
57
|
+
| Never edit the manifest | No dependencies, no scripts, no `postinstall`. Setup installs the suite; the project decides how it updates. |
|
|
58
|
+
| Write boundary | Only `.sassywares/`, the vendored `.agents/skills/sassy-*`, `skills-lock.json`, and one `.gitignore` line. Never `package.json`, never a root `.gitignore` in a workspace. |
|
|
59
59
|
| Detect, don't guess | An unknown base branch stays unknown and gets asked about. A probed value is reported as probed. |
|
|
60
60
|
| Comments are part of the file | Every key keeps its description and allowed values. A stripped config is an incomplete config. |
|
|
61
61
|
| Hooks are named, not written | Setup records hook skill names. Creating those skills is the project's work. |
|
|
@@ -9,10 +9,12 @@ Installed from upstream with the open `skills` CLI, which vendors the skills int
|
|
|
9
9
|
|
|
10
10
|
```bash
|
|
11
11
|
npx skills add sassywares/sassy-skills # first install
|
|
12
|
-
|
|
13
|
-
|
|
12
|
+
npx skills update -y # pull the latest from upstream
|
|
13
|
+
npx skills experimental_install # restore exactly what the lock pins
|
|
14
14
|
```
|
|
15
15
|
|
|
16
|
+
Refreshing the suite is this project's decision — nothing here updates itself.
|
|
17
|
+
|
|
16
18
|
The vendored skills and the lock are committed; `.claude/skills` is a link and is not.
|
|
17
19
|
|
|
18
20
|
`.agents/skills/` is read by pi and Cursor; Claude Code reads `.claude/skills/` only, which is why that symlink exists. After any change, `/reload` your harness.
|