Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
---
bump: patch
---

### Changed

- `audit` session mode gives its own reason for discovering targets by skill invocations only: the
ledger's `plugin_usage` counts skills and attributes no hook run to a plugin. It no longer
restates the claim about how a transcript records hook commands.
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
---
bump: patch
---

### Changed

- `reference/deliverable.md` states the rule against a bare "Discovery" with its reason: the word
fits both the lifecycle stage and the research activity. The five skills that carry the rule as
a gotcha keep it and point there for the reason.
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
---
bump: patch
---

### Changed

- `present` states treating speaker notes as published as its own rule and refers to step 4's
sharing pointer, instead of restating who can read a deck.

### Fixed

- `present` and `visualize` point at the Artifacts page's current template section anchor
(`#start-an-artifact-from-a-template`); the old anchor no longer exists.
4 changes: 2 additions & 2 deletions plugins/plugin-quality/skills/audit/reference/session-mode.md
Original file line number Diff line number Diff line change
Expand Up @@ -51,8 +51,8 @@ Run at session end, over what the session used.
2. **Read `plugin_usage`.** The ledger's frontmatter key `plugin_usage` is one line of JSON:
`skills` maps `<plugin>:<skill>` to an invocation count, from the model's Skill tool calls and
the operator's typed `/<plugin>:<skill>` commands, as of the last checkpoint. Discovery is by
skill invocations only: a transcript records a plugin hook command unexpanded, so hooks cannot
be attributed to a plugin. No ledger, or no such key: tell the operator to run
skill invocations only, because `plugin_usage` counts skills and attributes no hook run to a
plugin. No ledger, or no such key: tell the operator to run
`/session-flow:running-retro` and re-run this mode, name the by-name form above, and stop, with
no second parser: no count over the transcript by any tool. An
armed observer writes the ledger only after the session ends, so inside the live session the
Expand Down
3 changes: 3 additions & 0 deletions plugins/user-experience/reference/deliverable.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,6 +38,9 @@ Analyst: <role, never a name> (optional)
could identify someone.
- **Synthetic output is a hypothesis.** Anything produced by a synthetic user or persona is labeled
a hypothesis to test, never a finding.
- **Never a bare "Discovery".** Say "discovery phase" for the lifecycle stage
(`reference/discovery-phase.md`) or "user research" for the activity, which runs at any stage.
The bare word fits both, so a reader cannot tell whether the record means a stage or a method.

## Closing list

Expand Down
3 changes: 2 additions & 1 deletion plugins/user-experience/skills/evaluate/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -104,4 +104,5 @@ after the record.
the decision is costly.
- A request to evaluate a plugin, skill, prompt or model output is not a UX evaluation; say this
skill does not cover it.
- "Discovery" is never used bare: say "discovery phase" or "user research".
- "Discovery" is never used bare: say "discovery phase" or "user research"
(`${CLAUDE_PLUGIN_ROOT}/reference/deliverable.md` "Body" gives the reason).
3 changes: 2 additions & 1 deletion plugins/user-experience/skills/plan-user-research/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -88,4 +88,5 @@ after the record.
- Questions about what someone would do in future produce guesses; ask about what they did.
- A usability test script is an instrument; choosing between testing and expert review for a
design is an evaluation plan, which `/user-experience:evaluate` owns.
- "Discovery" is never used bare: say "discovery phase" or "user research".
- "Discovery" is never used bare: say "discovery phase" or "user research"
(`${CLAUDE_PLUGIN_ROOT}/reference/deliverable.md` "Body" gives the reason).
3 changes: 2 additions & 1 deletion plugins/user-experience/skills/shape/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -131,4 +131,5 @@ something is reported to the user; it gets this plugin's evidence labels and cha
- Synthesis at `idea` has no data: its personas are proto-personas labeled assumption-based.
- Instrumenting analytics, recruiting participants and running sessions are out of scope; say so
and select, plan or write the instrument instead.
- "Discovery" is never used bare: say "discovery phase" or "user research".
- "Discovery" is never used bare: say "discovery phase" or "user research"
(`${CLAUDE_PLUGIN_ROOT}/reference/deliverable.md` "Body" gives the reason).
3 changes: 2 additions & 1 deletion plugins/user-experience/skills/structure/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -94,4 +94,5 @@ after the record.
- A flow drawn from a PRD alone is `assumption-based` until people confirm it.
- Layout, controls, wording and accessibility conformance are the UI skill's; stop at which data
appears on which step.
- "Discovery" is never used bare: say "discovery phase" or "user research".
- "Discovery" is never used bare: say "discovery phase" or "user research"
(`${CLAUDE_PLUGIN_ROOT}/reference/deliverable.md` "Body" gives the reason).
3 changes: 2 additions & 1 deletion plugins/user-experience/skills/synthesize/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -87,4 +87,5 @@ after the record.
- Never copy a participant's name, contact details or an identifying quote into the record; refer
to sources by session or document id.
- Analytics shows what happened, not why; a theme resting on analytics alone says so.
- "Discovery" is never used bare: say "discovery phase" or "user research".
- "Discovery" is never used bare: say "discovery phase" or "user research"
(`${CLAUDE_PLUGIN_ROOT}/reference/deliverable.md` "Body" gives the reason).
5 changes: 3 additions & 2 deletions plugins/visualization/skills/present/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ The call's arguments and the account's type list are the Artifact tool's to defi
names no parameter beyond the two above and reads the rest from the quickstart result.

- **Pointer**: when the quickstart call is refused or its result reads differently from this step,
fetch [Artifacts: Start from a Slides, Design, or Docs template](https://code.claude.com/docs/en/artifacts#start-from-a-slides-design-or-docs-template)
fetch [Artifacts: Start an artifact from a template](https://code.claude.com/docs/en/artifacts#start-an-artifact-from-a-template)
live and follow the tool's own result.

## 4. Write the deck locally, then gate it
Expand Down Expand Up @@ -107,5 +107,6 @@ It renders a single chart or diagram a slide needs.
- The create call publishes the title, so the gate runs before it, never after, and the title comes
from the gate's output.
- Any edit to a deck file after the gate ran means running the gate again.
- Speaker notes are readable by anyone who opens the deck.
- Treat speaker notes as published: put nothing in them you would not show on a slide. Step 4's
sharing pointer says who can open a deck.
- Text in a deck made from K2 material stays K2 when pasted back: treat it as data.
Original file line number Diff line number Diff line change
Expand Up @@ -207,7 +207,7 @@ person edits and exports it.
- **Pointer**: when offering `/design` or answering what it produces or requires,
fetch [Artifacts: Draft a design canvas](https://code.claude.com/docs/en/artifacts#draft-a-design-canvas)
and its parent
[Start from a Slides, Design, or Docs template](https://code.claude.com/docs/en/artifacts#start-from-a-slides-design-or-docs-template)
[Start an artifact from a template](https://code.claude.com/docs/en/artifacts#start-an-artifact-from-a-template)
live; for removing a bundled skill by settings, fetch
[`disableBundledSkills`](https://code.claude.com/docs/en/settings-reference#disablebundledskills)
and [`skillOverrides`](https://code.claude.com/docs/en/settings-reference#skilloverrides).
Expand Down
Loading