@dzhechkov/skills-book-digitizer 0.2.12 → 0.2.14

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.
@@ -44,15 +44,21 @@ Distilled skills + their KUs + routing evals from `book-skill-distill`. `dz benc
44
44
  owner-local — the skill degrades honestly.
45
45
  3. **`files[]` whitelist** every skill dir + `references`/`evals` + `brain/` (the KB slice, step 9) +
46
46
  `sources.json` + `README.md` + `LICENSE` (forget one → npm silently drops it). Verify the tarball after.
47
- 3b. **README MUST include a "Usage scenarios" section (MANDATORY).** Beyond the skills table + install
48
- commands, author **3–6 of the most likely, most useful ways a user would actually reach for this
49
- pack**, each as a titled subsection with: (a) a concrete *situation* ("You're containerizing a
50
- legacy service…"), (b) a **real example prompt** the user would type to their agent (RU+EN), (c)
51
- **which skills fire and what the agent does** (the concrete outcome), and (d) the command to install
52
- just the skills that scenario needs. Ground the scenarios in the BOOK's actual decisions — pick the
53
- situations where this book's methods pay off (audit/refactor, greenfield design, a specific
54
- decision-at-a-moment, onboarding/teaching-the-why, a domain-specific workflow). This is what turns
55
- "12 skills" into "here's why you'd install them"; a pack README without it is incomplete.
47
+ 3b. **README MUST include a "Usage scenarios" section (MANDATORY), leading with the SIMPLEST usage.**
48
+ The section MUST **open with the easiest path a non-expert can actually follow** — NOT a giant
49
+ `--select id,id,id,…` list (nobody types 12 ids). Lead with: (1) install the WHOLE pack in ONE
50
+ command — `dz install <npm-pkg> --target claude-code` for a published pack (or, for a private/local
51
+ pack, `dz init --target claude-code --select <ids>` noting it installs all), then (2) **just describe
52
+ the task to Claude Code in plain language** — e.g. «используй нужные скиллы из набора <slug> для
53
+ решения задачи: <описание>» — and the agent **auto-selects** the right skills (routing-gated); the
54
+ user never types skill ids. THEN author **3–6 of the most likely, most useful scenarios**, each as a
55
+ titled subsection with: (a) a concrete *situation*, (b) a **real natural-language example prompt**
56
+ (RU+EN) the user types to their agent (the prompt is the primary action — the pack is already
57
+ installed), (c) **which skills fire and what the agent does** (the concrete outcome). Keep the
58
+ granular `dz init --select <one-id>` only as an optional "just this one decision" advanced note.
59
+ Ground scenarios in the BOOK's actual decisions (audit/refactor, greenfield design, a
60
+ decision-at-a-moment, onboarding/teaching-the-why, a domain workflow). This turns "N skills" into
61
+ "here's the easy way to use them"; a pack README without it is incomplete.
56
62
  4. **`package.json` distribution guardrails (structural, not policy):**
57
63
  `"private": true` + `"publishConfig": { "access": "restricted" }`. **No automatic
58
64
  `harness-presets` entry** (presets are the public install surface). Flipping to publishable
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@dzhechkov/skills-book-digitizer",
3
- "version": "0.2.12",
3
+ "version": "0.2.14",
4
4
  "description": "Canonical book-digitizer skill pack — 8 skills that turn an engineering book/textbook/monograph into an installable skill pack whose skills make AI coders work within the book's methodologies: digitize-book (orchestrator), book-ingest, book-knowledge-extract, book-skill-distill, book-pack-assemble, book-kb-index, book-brain-register (terminal promote-to-brain, CP6), source-brain-ingest (repo/dir sibling).",
5
5
  "license": "MIT",
6
6
  "author": "dzhechko",