@adia-ai/adia-ui-factory 0.2.3 → 0.2.4

package/skills/adia-ui-kit/references/teach-protocol.md

@@ -14,9 +14,9 @@
 - "absorb this lesson into adia-ui-kit"
 - "teach the skill about [the new component / pattern / discipline]"
 
-**Companion:** `references/feedback-authoring.md` (when the new knowledge originated from a FEEDBACK ticket loop) and the §SkillHygiene section of `SKILL.md` (run hygiene audit after any §Teach landing).
+**Companion:** `feedback-authoring.md` (when the new knowledge originated from a FEEDBACK ticket loop) and the §SkillHygiene section of `SKILL.md` (run hygiene audit after any §Teach landing).
 
-**Anti-companion:** `docs/journal/YYYY/MM/<date>.md` (arc-specific stories belong in the journal, not the skill — see decision tree below).
+**Anti-companion:** `.claude/docs/journal/YYYY/MM/<date>.md` (arc-specific stories belong in the journal, not the skill — see decision tree below).
 
 ---
 
@@ -71,7 +71,7 @@ echo "add a recipe for composing an editor-shell inside an admin-page-body" \
 # → branch: B (recipe)
 ```
 
-If the script's confidence is **low**, re-read the prose tree below and classify by hand — the keyword vocabulary missed the payload's shape and you should consider adding the payload to `evals/teach-routing-cases.json` so future runs catch it. If the script's confidence is **high** or **medium**, trust the landing.
+If the script's confidence is **low**, re-read the prose tree below and classify by hand — the keyword vocabulary missed the payload's shape and you should consider adding the payload to `../evals/teach-routing-cases.json` so future runs catch it. If the script's confidence is **high** or **medium**, trust the landing.
 
 Behavioral eval suite: `node scripts/teach-route.mjs --eval=evals/teach-routing-cases.json` runs all canonical cases and reports pass/fail. v3.1.0 baseline: 9/9 (100%).
 
@@ -141,7 +141,7 @@ Is it a FEEDBACK RESOLUTION (upstream ticket landed, skill should reflect)?
 
 Is it a one-off ARC STORY, LESSON LEARNED, OR HISTORICAL CONTEXT?
   → NO landing in the skill (branch G — the NEGATIVE case).
-    It belongs in `docs/journal/YYYY/MM/<date>.md` where future
+    It belongs in `.claude/docs/journal/YYYY/MM/<date>.md` where future
     archeology will find it (per AGENTS.md's journal discipline).
     Skipping the skill here is a feature, not a gap.
     (See Worked Example G — the negative case.)
@@ -258,10 +258,10 @@ npm run check:corpus-rules-format  # no malformed bullets
 
 **Request:** "train adia-ui-kit on the editor inspector pane pattern — a right-pane inside `<editor-shell>` that hosts `<tabs-ui>` + `<inspector-ui>` for live A2UI doc state inspection."
 
-**Decision tree:** Recipe — cross-component composition pattern. → **`references/patterns-recipes.md`** (or `patterns-shells.md` if editor-cluster-specific).
+**Decision tree:** Recipe — cross-component composition pattern. → **`patterns-recipes.md`** (or `patterns-shells.md` if editor-cluster-specific).
 
 **Action:**
-1. Open `references/patterns-recipes.md`.
+1. Open `patterns-recipes.md`.
 2. Add a new H2 section "## Editor inspector pane" with: triggers, when to use, composition (HTML + A2UI JSON), token contract, anti-patterns.
 3. Cross-link from SKILL.md §Patterns table (one row: pattern name, file, when-to-load).
 4. Bump version PATCH (vN.M.x+1) since reference-file augment, not new section.
@@ -272,7 +272,7 @@ npm run check:corpus-rules-format  # no malformed bullets
 
 **Request:** "teach the skill about the new agent onboarding wizard flow — 3 pages (welcome → persona pick → tool consent) using `<simple-shell>` + `<stepper-ui>`."
 
-**Decision tree:** Flow — multi-page user journey. → **`references/flows-auth.md`** or new `flows-onboarding.md`.
+**Decision tree:** Flow — multi-page user journey. → **`flows-auth.md`** or new `flows-onboarding.md`.
 
 **Action:**
 1. Decide: does this fit existing `flows-auth.md` (which covers registration wizards)? If yes, augment. If the onboarding wizard has distinct lifecycle hooks (telemetry, persona persistence) that don't fit auth, create `flows-onboarding.md`.
@@ -329,10 +329,10 @@ npm run check:corpus-rules-format  # no malformed bullets
 
 **Request:** "the skill should remember how we shipped Arc D today — the catalog-renderer bug, the dict-stringification, the 12-day silence."
 
-**Decision tree:** One-off arc story / historical context. → **`docs/journal/YYYY/MM/<date>.md`, NOT the skill.**
+**Decision tree:** One-off arc story / historical context. → **`.claude/docs/journal/YYYY/MM/<date>.md`, NOT the skill.**
 
 **Action:**
-1. The journal entry already exists (§408 in `docs/journal/2026/05/2026-05-22.md`).
+1. The journal entry already exists (§408 in `.claude/docs/journal/2026/05/2026-05-22.md`).
 2. **Do nothing in the skill.** The skill is procedural ("what to do"), not historical ("what happened"). Future archeology grep'ing for "catalog-renderer" or "[object Object]" finds the journal entry; that's where it belongs.
 3. The structural lesson (axis 1 of the audit-corpus-rules-format gate) is already captured procedurally by Example E above.
 
@@ -393,7 +393,7 @@ Receiving a §Teach request and landing the content without asking "should this
 - **§Mission** (SKILL.md) — defines the three postures (Author / Consultant / Correction). §Teach is a fourth posture, narrower than Author (which is forward-generation from scratch).
 - **§SkillHygiene** (SKILL.md) — the audit gate that catches §Teach landing regressions. Always run after.
 - **§LoadingProtocol** (SKILL.md) — defines the reference-file extraction discipline. §Teach respects it by routing content > ~50 LOC to `references/`.
-- **`references/feedback-authoring.md`** — companion when §Teach is triggered by a FEEDBACK resolution (Example F).
+- **`feedback-authoring.md`** — companion when §Teach is triggered by a FEEDBACK resolution (Example F).
 - **AGENTS.md** (repo root) — defines the journal discipline that §Teach defers to for arc stories (Example G).
 - **`scripts/skills/audit-skill-hygiene.mjs`** — the eight-axis audit; run after any §Teach landing.
 - **`scripts/audit/audit-yaml-rules-coverage.mjs`** + siblings (§409) — the regression gates that catch yaml-SoT drift when §Teach lands in yaml instead of the skill (Example A).
@@ -413,7 +413,7 @@ When in doubt, the table below routes by request shape.
 | "new methodology / posture" | inline in SKILL.md (near §Mission / §ReasoningMethodologies) | MINOR | `audit:skill-hygiene` |
 | "new audit / verification script" | cross-link from SKILL.md harness manifest | PATCH | `audit:skill-hygiene` |
 | "FEEDBACK-NN resolved + skill reflected" | patch the misdiagnosed section + bug-shape taxonomy entry | PATCH | manual review |
-| "arc story / lesson learned" | `docs/journal/YYYY/MM/<date>.md` (NOT skill) | n/a | journal-date sanity hook |
+| "arc story / lesson learned" | `.claude/docs/journal/YYYY/MM/<date>.md` (NOT skill) | n/a | journal-date sanity hook |
 | "absorb sibling-skill knowledge" | route to peer skill OR defend inclusion in CHANGELOG | varies | `audit:skill-hygiene` + peer review |
 
 ---

package/skills/adia-ui-kit/scripts/audit-kit-roster.mjs

@@ -47,7 +47,7 @@ USAGE
   node scripts/audit-kit-roster.mjs [--json] [--strict] [--dir <skill-root>]
 
 AXES (1-8 universal, inlined; 9 kit-specific)
-  1  Manifest enforcement     — skill.json files[] matches disk (docs/ excluded)
+  1  Manifest enforcement     — skill.json files[] matches disk (.claude/docs/ excluded)
   2  Reference graph          — every markdown link in SKILL.md resolves
   3  Capability-menu drift    — §ColdStartTriage entry refs exist (skipped if absent)
   4  Version-literal parity   — SKILL.md frontmatter version == skill.json

package/skills/adia-ui-migration/CHANGELOG.md

@@ -11,7 +11,7 @@ audit/sweep incantations inline + §"What's covered, by version" table + §Forwa
 looking surfaces + §Anti-patterns + §Worked example. The inversion to
 `references/migrations/v0.0.X.md` per-version recipes and bundling of
 `scripts/migrate.mjs` are Round 2+/Round 3+ work per the per-skill
-REFACTOR-SPEC at `docs/REFACTOR-SPEC.md`.
+REFACTOR-SPEC at `.claude/docs/REFACTOR-SPEC.md`.
 
 Cleans up dangling cross-reference to `bespoke-shell-children` (the skill
 was absorbed into `adia-ui-authoring/references/shell-patterns.md` v1.1.1

package/skills/adia-ui-migration/SKILL.md

@@ -7,7 +7,7 @@ description: Migrate consumer code between AdiaUI versions — sweep deprecated
 
 Bring consumer code current with a newer release of `@adia-ai/web-components`. Sweeps the repo for deprecated attributes, renamed events, removed tokens, and tag-name changes; applies mechanical search-and-replace; verifies the build still passes.
 
-The canonical source of truth for what each version's BREAKING surface looks like is [`MIGRATION GUIDE.md`](../../../../../docs/MIGRATION%20GUIDE.md) at the repo root. This skill consumes that guide — read the relevant version section before sweeping.
+The canonical source of truth for what each version's BREAKING surface looks like is the AdiaUI monorepo's `.claude/docs/MIGRATION GUIDE.md` (in the monorepo's `.claude/docs/` directory, outside this plugin). This skill consumes that guide — read the relevant version section before sweeping.
 
 ## When to use
 
@@ -37,7 +37,7 @@ The canonical source of truth for what each version's BREAKING surface looks lik
 
 Always start here. The guide lists each version's BREAKING items with code-diff examples and search-and-replace incantations. Read the section for the target version (or the merged span if the consumer is jumping multiple versions).
 
-The guide is at `/Users/kimba/Projects/adia/gen-ui-kit/docs/MIGRATION GUIDE.md` (the space in the filename is intentional).
+The guide is at `.claude/docs/MIGRATION GUIDE.md` in the AdiaUI monorepo (the space in the filename is intentional).
 
 If the target version's section doesn't exist yet, the migration is undocumented and the skill should pause, ask the user to clarify the breaking surface, and offer to draft a guide section first.
 
@@ -237,7 +237,7 @@ done
 **Category D — Inventory tables in cross-cutting docs** (README, AGENTS.md, ROADMAP) often pre-date the change and don't follow obvious path patterns.
 
 ```bash
-grep -ln 'old-name' README.md AGENTS.md docs/ROADMAP.md docs/specs/INDEX.md
+grep -ln 'old-name' README.md AGENTS.md .claude/docs/ROADMAP.md .claude/docs/specs/INDEX.md
 ```
 
 **Pre-rename snapshot pattern** for diffable verification:
@@ -298,7 +298,7 @@ GUIDE author:
    - chat: `<section data-chat-messages>` → `<chat-thread>`; `<chat-input-ui data-chat-input>` → `<chat-composer><chat-input-ui>`; `[data-chat-empty]` → `<chat-empty>`
    - editor: `<header>` → `<editor-toolbar>`; `<div data-canvas>` → `<editor-canvas>`; `<pane-ui data-left>` → `<editor-sidebar slot="leading"><pane-ui resizable>`; `<footer>` → `<editor-statusbar>`
 
-   Documented in [`MIGRATION GUIDE.md` `§ v0.4.0`](../../../../../docs/MIGRATION%20GUIDE.md#migrating-to-adia-aiv040-2026-05-10) + the `adia-ui-authoring` skill's Mode 3 `shell-patterns` reference (which absorbed the bespoke-shell-children content) + v0.3.4/v0.3.5/v0.3.6 release notes.
+   Documented in the monorepo's `MIGRATION GUIDE.md` (its `§ v0.4.0` section, outside this plugin) + the `adia-ui-authoring` skill's Mode 3 `shell-patterns` reference (which absorbed the bespoke-shell-children content) + v0.3.4/v0.3.5/v0.3.6 release notes.
 
    Trigger attributes that **still work** in v0.4.0+: `[data-sidebar-toggle="<name>"]`, `[data-command-trigger]`, `[data-toolbar-action="<name>"]` — these wire through to the bespoke children's public APIs (`.toggle()`, `.show()`, `toolbar-action` event). Emitted events that are part of the consumer contract: `sidebar-toggle`, `sidebar-resize`, `composer-submit`, `toolbar-action`, `command-select`, `editor-mode-change`. Renames = sweeps.