@staff0rd/assist 0.1013.0 → 0.1015.0

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.
@@ -28,7 +28,7 @@ If the harness provides a structured question tool, ask each question with it
28
28
 
29
29
  From the clarifying answers, decide whether the story involves a **substantial UI change** — a new screen, panel, view or component, or a reworked layout or interaction flow. A trivial UI change (a label, a button, a tweak to an existing control) or no UI change at all is not substantial: skip this step entirely and do not mention it.
30
30
 
31
- If it is substantial, do not ask whether to design it — follow `/design` (`~/.claude/commands/design.md`) for the story's UI, applying it to what the user described and answered. Publish the design as an artifact, give the user its URL, and iterate on it with them — editing the same file and republishing to the same URL — until they say they are happy with it. Only then move on.
31
+ If it is substantial, do not ask whether to design it — follow `/design` (`~/.claude/skills/design/SKILL.md`) for the story's UI, applying it to what the user described and answered. Publish the design as an artifact, give the user its URL, and iterate on it with them — editing the same file and republishing to the same URL — until they say they are happy with it. Only then move on.
32
32
 
33
33
  Keep the artifact's URL and name: the item's description references the design (Step 4), and the artifact is attached to the item once it is created (Step 5).
34
34
 
@@ -107,7 +107,7 @@ Check the item's Activity section (from `assist backlog view <id>`) for an exist
107
107
  - **An existing `design` activity** and this refinement changes the UI substantially — update that design, republishing to its existing artifact URL rather than creating a new one.
108
108
  - Otherwise — skip this step entirely and do not mention it.
109
109
 
110
- When a design is needed, do not ask whether to design it — follow `/design` (`~/.claude/commands/design.md`) for the item's UI, applying it to the item as refined. To update an existing design, read the artifact at its URL first and build on it, publishing back to the same URL. Give the user the artifact's URL and iterate on it with them — editing the same file and republishing to the same URL — until they say they are happy with it.
110
+ When a design is needed, do not ask whether to design it — follow `/design` (`~/.claude/skills/design/SKILL.md`) for the item's UI, applying it to the item as refined. To update an existing design, read the artifact at its URL first and build on it, publishing back to the same URL. Give the user the artifact's URL and iterate on it with them — editing the same file and republishing to the same URL — until they say they are happy with it.
111
111
 
112
112
  Then keep the item in sync with the design:
113
113