@owlmeans/agent-skills 0.1.12 → 0.1.15

package/agent-meta/skills/scaffolding/SKILL.md

@@ -23,7 +23,9 @@ npx @owlmeans/create-app my-app
 
 By default it copies the template, runs `git init`, installs dependencies, and **deploys agent
 guidance** into the project via [[bun]]-installed `@owlmeans/agent-skills` (`.claude/skills/` +
-`.github/instructions/`).
+`.github/instructions/`). With `--no-install` the deploy still runs — the installer's own bundled
+extras give the project its general/harness guidance; only the package-specific skills wait for
+`npx @owlmeans/agent-skills` after the install.
 
 Flags: `--name <name>`, `--pm <bun|npm|yarn>` (default `bun`), `--no-install`, `--no-skills`,
 `--no-git`, `--yes`/`-y`, `--help`.
@@ -50,29 +52,38 @@ primitives + layout/nav/screens). Finish with `npx @owlmeans/agent-skills` to ad
 ```
 my-app/
 ├── package.json            # bun workspaces: sources/*
-├── CLAUDE.md               # agent context: memory + skill directives + project-purpose placeholder
+├── CLAUDE.md               # git/reporting/memory/self-education rules + project-purpose placeholder
 ├── .github/
 │   ├── copilot-instructions.md   # same directives for Copilot
-│   └── memory/MEMORY.md          # starter memory index
-├── .claude/memory/MEMORY.md      # starter memory index
+│   └── instructions/             # seeded harness instructions (+ deployed ones)
+├── .claude/skills/               # seeded harness skills (+ deployed ones)
+├── .agents/memory/MEMORY.md      # starter shared memory graph index (both tools)
 ├── sources/common/         # consts, types, schemas, config, modules (entrypoints)
 ├── sources/api/            # context.ts (appendStaticResource), app/session/*, modules.ts, index.ts
 └── sources/web/            # vite + tailwind v4, components/ui/*, layout, nav, screens, render.tsx
 ```
 
+Memory lives **only** in `.agents/memory/` — the legacy `.claude/memory/` and `.github/memory/`
+starters are gone (see [[agent-memory]]; [[memory-recompact]] migrates a project that still has them).
+
 The session demo stores items in `@owlmeans/static-resource`, namespaced by a client-generated
 `sid` kept in `localStorage` — no database, no authentication. See [[static-resource]],
 [[server-app]], [[web-panel]].
 
 ## Generated agent guidance
 
-`CLAUDE.md` and `.github/copilot-instructions.md` carry the same memory and skill directives as a
-real OwlMeans project, plus a **project-purpose placeholder** (`<!-- OWLMEANS:PROJECT-PURPOSE -->`).
-On the first agent session that block instructs the agent to ask the user what the project is for and
-replace it in both files. The deployed skills include the general management skills
-[[skill-authoring]], [[agent-memory]] and the mandatory [[reuse-code]] (find an existing `@owlmeans/*`
-package or code before proposing third-party libraries or custom solutions) so the project can grow its own guidance.
-`CLAUDE.md` and `.github/copilot-instructions.md` reference [[reuse-code]] as mandatory. After adding any
-`@owlmeans/*` dependency, re-run `npx @owlmeans/agent-skills` — discovery scans **every**
-`node_modules/@owlmeans` in the workspace (root and nested under `sources/*`), so package-specific
-skills are picked up even though bun nests them.
+`CLAUDE.md` and `.github/copilot-instructions.md` carry the same four mandatory sections as a real
+OwlMeans monorepo — **Git Workflow**, **Reporting**, **Memory** (the `.agents/memory/` graph store),
+**Self-Education** — plus the mandatory [[reuse-code]] section and a **project-purpose placeholder**
+(`<!-- OWLMEANS:PROJECT-PURPOSE -->`). On the first agent session that block instructs the agent to
+ask the user what the project is for and replace it in both files.
+
+The harness guidance is **seeded into the template** as generated, banner-carrying copies, so a
+project has it even before the installer runs: [[agent-memory]], [[memory-promotion]],
+[[memory-recompact]], [[self-education]], [[skill-authoring]], `git`, [[reuse-code]],
+[[getting-started]]. Regenerate the seed with `sync-agent-meta --seed-only` in the library-manager;
+never hand-edit a seeded copy. The installer adds the remaining general skills
+([[scaffolding]], [[router-plugins]], [[shadcn-web]], [[shadcn-versions]]) and every
+package-specific one. After adding any `@owlmeans/*` dependency, re-run `npx @owlmeans/agent-skills`
+— discovery scans **every** `node_modules/@owlmeans` in the workspace (root and nested under
+`sources/*`), so package-specific skills are picked up even though bun nests them.

package/agent-meta/skills/self-education/SKILL.md

@@ -0,0 +1,83 @@
+---
+name: self-education
+description: Mandatory post-development guidance updating — after functionality is added or changed, rewrite the project skills/instructions the work touched as current rules (never as change notes), record external-doc findings (URL + gist) in the governing skill, or add skills/instructions for new subsystems and technologies. Required before the completion report whenever development started from a plan agreed with the agent.
+user-invocable: true
+scope: general
+---
+<!-- AUTO-GENERATED — do not edit. Regenerate via sync-agent-meta. -->
+
+# Self-education
+
+After functionality is added or changed, the guidance that describes it must catch up — the agent
+teaches itself for next time. This pass runs after implementation and verification, **before**
+the completion report.
+
+## When (mandatory)
+
+Development "started from planning" when the session produced a plan the operator approved before
+implementation — a plan-mode approval, an agreed written plan/spec, or an explicit "go ahead" on
+a proposed approach. **Approval of a plan is simultaneously approval of its implicit final step:
+this self-education pass.** A planned task is not finishable without it. If guidance files cannot
+be edited (read-only run), list the required updates in the report instead.
+
+Also recommended after any unplanned change that made an existing skill/instruction inaccurate.
+
+## Review checklist
+
+For each area the work touched:
+
+1. Which existing skill/instruction covers it? (Check `.claude/skills/` +
+   `.github/instructions/`.)
+2. Do its commands, paths, APIs, and behavior claims still hold after the change?
+3. Fix in place — rewrite the affected lines so they describe current behavior; never append a
+   note about what this change did. Keep the skill and its instruction twin in sync.
+
+## Shape of an update
+
+Skills and instructions state **current rules, not what changed**. Every edit is a rewrite in
+place of the affected lines.
+
+Never write into a skill or instruction: dated bulletins ("2026-07-05 — …"), phase or migration
+status ("Phase 3 complete", "migration done", "landed"), "formerly X, now Y", incident
+narratives, fixed-bug logs, or point-in-time inventories. If a line only makes sense to someone
+who watched the change happen, it does not belong in guidance — the rule it taught does, stated
+timelessly. Facts too specific to generalize go to `.agents/memory/` (`agent-memory`); the
+rewrite recipe is `memory-promotion` → Distillation.
+
+Test: a finished skill reads as though the feature was always this way.
+
+## Non-project skills
+
+If a general or imported skill gained an important usage pattern during the work, add the pattern
+to the **deployed copy** in this repo and note it in the report as an upstream candidate —
+canonical archive copies change only on explicit operator request.
+
+## External docs
+
+If the work required reading internet documentation for an external API, library, or service,
+the governing skill must record it under an `## External docs` heading:
+
+```
+- <URL> — <one-line gist of what it settled> (<version/date if load-bearing>)
+```
+
+Governing skill = the project skill covering the touched area; else the skill covering that
+library; if none exists and the technology will recur, create one (update-vs-create rule in
+`memory-promotion`). Never leave doc findings only in memory or the conversation.
+
+## New subsystems / technologies
+
+When new technology or a new subsystem entered the repo: create the skill/instruction pair for
+its procedures, and/or the `.agents/memory/` node for its facts — split along the
+memory-vs-skill boundary (`agent-memory` / `memory-promotion`).
+
+## Completion gate
+
+The completion report must contain a Self-education table:
+
+| Item | Action | Path |
+|---|---|---|
+| <area/skill> | updated / created / none-needed | <path> |
+
+"none-needed" requires a one-phrase reason. A post-plan completion report without this table is
+a protocol violation.

package/agent-meta/skills/skill-authoring/SKILL.md

@@ -65,15 +65,20 @@ skill").
 - **Skill / instruction** — a reusable procedure or reference you (or the tools) will want again,
   worth auto-invoking. Lives in `.claude/skills/` + `.github/instructions/`.
 - **Memory** — a fact, decision, or gotcha specific to this project's history/state. Lives in
-  `.claude/memory/` + `.github/memory/`. See the `agent-memory` skill.
+  the shared `.agents/memory/` graph store (both tools). See the `agent-memory` skill; promotion
+  triggers and the update-vs-create rule live in `memory-promotion`.
 
 If you find yourself writing "last time we…", that is memory. If you are writing "to do X, do Y",
 that is a skill.
 
+Never paste memory text into a skill. Memory content enters guidance only as a restated general
+rule — trigger, step, and the failure it prevents, with dates, phase/status markers, versions and
+incident narrative stripped (`memory-promotion` → Distillation).
+
 ## After adding a skill
 
 1. If it replaces an ad-hoc `.claude/<topic>.md`, remove that file.
-2. Mention it in `.claude/memory/MEMORY.md` (and `.github/memory/MEMORY.md`) so future sessions know
-   it exists.
+2. If it distilled memory content into rules, shrink the source `.agents/memory/` node to a
+   pointer line (`memory-promotion`) — the memory index does not list skills.
 3. Reference it from `CLAUDE.md` / `.github/copilot-instructions.md` if it should be discoverable
    every session.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@owlmeans/agent-skills",
-  "version": "0.1.12",
+  "version": "0.1.15",
   "license": "MIT",
   "type": "module",
   "scripts": {
@@ -26,10 +26,10 @@
   },
   "devDependencies": {
     "@owlmeans/dep-config": "workspace:*",
-    "@types/bun": "^1.3.0",
-    "@types/node": "^24.10.1",
-    "nodemon": "^3.1.11",
-    "typescript": "^6.0.2"
+    "@types/bun": "^1.3.14",
+    "@types/node": "^26.1.0",
+    "nodemon": "^3.1.14",
+    "typescript": "^6.0.3"
   },
   "publishConfig": {
     "access": "public"