@staff0rd/assist 0.1106.0 → 0.1107.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.
@@ -23,7 +23,7 @@ Skip questions the user has already answered. Stop asking as soon as you have en
23
23
 
24
24
  ## Step 3: Design the UI change
25
25
 
26
- Read the **Designing a new backlog item's UI change** section of `/design` (`~/.claude/skills/design/SKILL.md`) and follow its Decide and Design and review steps for the fix. If it decides the fix's UI change is not substantial, skip this step silently. Otherwise its link step applies in Step 4 and its attach step in Step 5.
26
+ Read the **Designing a new backlog item's UI change** section of `/design` (`{{skill:design}}`) and follow its Decide and Design and review steps for the fix. If it decides the fix's UI change is not substantial, skip this step silently. Otherwise its link step applies in Step 4 and its attach step in Step 5.
27
27
 
28
28
  ## Step 4: Compose the bug report
29
29
 
@@ -3,17 +3,17 @@ description: Adopt the vendored design system prompt and apply it to a design ta
3
3
  allowed_args: "<design prompt>"
4
4
  ---
5
5
 
6
- You are being asked to act as an expert designer for the remainder of this task. The design guidance lives in files synced to `~/.claude` by `assist sync`.
6
+ You are being asked to act as an expert designer for the remainder of this task. The design guidance lives in files synced by `assist sync`.
7
7
 
8
8
  ## Step 1: Load the design system prompt
9
9
 
10
- Read `~/.claude/design-system-prompt.md` in full. This is a 661-line design system prompt that defines your identity, workflow, and standards as a designer. Adopt it as your operating context for this task — its instructions take precedence over your default behaviour for the design work that follows.
10
+ Read `{{design.systemPrompt}}` in full, unless it is already part of your instructions (a design session appends it at launch). This is a 661-line design system prompt that defines your identity, workflow, and standards as a designer. Adopt it as your operating context for this task — its instructions take precedence over your default behaviour for the design work that follows.
11
11
 
12
12
  If the file is missing, tell the user to run `assist sync` first and stop.
13
13
 
14
14
  ## Step 2: Note the available skills
15
15
 
16
- The design skills referenced by the system prompt (`discovery-questions`, `frontend-aesthetic-direction`, `wireframe`, `make-a-deck`, `make-a-prototype`, `make-tweakable`, `generate-variations`, `design-system-extract`, `component-extract`, `accessibility-audit`, `ai-slop-check`, `hierarchy-rhythm-review`, `interaction-states-pass`, `polish-pass`) are synced to `~/.claude/skills/`. Each is a phased procedure. When the task matches a skill's trigger (as described in the system prompt's "Available skills" chapter), read the relevant `~/.claude/skills/<name>.md` and follow it.
16
+ The design skills referenced by the system prompt (`discovery-questions`, `frontend-aesthetic-direction`, `wireframe`, `make-a-deck`, `make-a-prototype`, `make-tweakable`, `generate-variations`, `design-system-extract`, `component-extract`, `accessibility-audit`, `ai-slop-check`, `hierarchy-rhythm-review`, `interaction-states-pass`, `polish-pass`) are synced alongside it. Each is a phased procedure. When the task matches a skill's trigger (as described in the system prompt's "Available skills" chapter), read the relevant `{{design.skill}}` and follow it.
17
17
 
18
18
  ## Step 3: Apply it to the request
19
19
 
@@ -25,10 +25,12 @@ Follow the workflow the system prompt lays out — ask clarifying questions firs
25
25
 
26
26
  ## Step 4: Deliver as an artifact
27
27
 
28
- The design system prompt is written for a filesystem-based project, so it talks about saving HTML files. In Claude Code the file is the intermediate, not the deliverable: **publish the finished design as an artifact** so the user gets a URL they can open and share. Do not deliver a scratchpad path.
28
+ The design system prompt is written for a filesystem-based project, so it talks about saving HTML files. When you have the `Artifact` tool, the file is the intermediate, not the deliverable: **publish the finished design as an artifact** so the user gets a URL they can open and share. Do not deliver a scratchpad path.
29
29
 
30
30
  Load the `artifact-design` skill before writing the page, write the HTML to a file, then publish that file with the `Artifact` tool. When iterating, edit the same file and publish again so the URL stays stable. Keep a design on disk only as a working intermediate, or when the user asks for a file specifically.
31
31
 
32
+ Without an `Artifact` tool, the HTML file is the deliverable: write it inside the repo (not a temporary directory) and give the user its absolute path. When iterating, edit the same file.
33
+
32
34
  ## Designing a new backlog item's UI change
33
35
 
34
36
  `/draft` and `/bug` follow this section while creating an item. It is the single source of the design step for both, and `/refine` reuses its `ask-design` review rounds for new and updated designs.
@@ -49,6 +51,7 @@ assist ask-design --url '<artifact-url>' --title '<design title>' --body - < <su
49
51
  - **Rejected** (non-zero, printing the reason and comments) — revise the design to address each one, republish to the same artifact URL, and re-run `ask-design` for the next round. Repeat until approved.
50
52
  - To revise while a round is still pending, re-run `ask-design` directly; the earlier task exits 0 as superseded — ignore its result.
51
53
  - If it prints the design link and exits 0 without `Approved.` (not in an assist web session), ask the user in chat instead and iterate there — editing the same file and republishing to the same URL — until they say they are happy with it.
54
+ - Without an `Artifact` tool there is no artifact URL, and `ask-design` refuses with the reason design review is unavailable on this harness. Review in chat instead: give the user the HTML file's absolute path and iterate on the same file until they say they are happy with it, then skip the link and attach steps below and summarise the design in the item's description.
52
55
 
53
56
  Keep the artifact's URL and name for the two steps below.
54
57
 
@@ -26,7 +26,7 @@ If the harness provides a structured question tool, ask each question with it
26
26
 
27
27
  ## Step 3: Design the UI change
28
28
 
29
- Read the **Designing a new backlog item's UI change** section of `/design` (`~/.claude/skills/design/SKILL.md`) and follow its Decide and Design and review steps for the story. If it decides the change is not substantial, skip this step silently. Otherwise its link step applies in Step 4 and its attach step in Step 5.
29
+ Read the **Designing a new backlog item's UI change** section of `/design` (`{{skill:design}}`) and follow its Decide and Design and review steps for the story. If it decides the change is not substantial, skip this step silently. Otherwise its link step applies in Step 4 and its attach step in Step 5.
30
30
 
31
31
  ## Step 4: Compose the item
32
32
 
@@ -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/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. Then review it with `ask-design` rather than iterating in chat: read the **Designing a new backlog item's UI change** section of `/design` and follow the review rounds in its **Design and review** step, republishing to the same artifact URL between rounds until it is approved.
110
+ When a design is needed, do not ask whether to design it — follow `/design` (`{{skill:design}}`) 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. Then review it with `ask-design` rather than iterating in chat: read the **Designing a new backlog item's UI change** section of `/design` and follow the review rounds in its **Design and review** step, republishing to the same artifact URL between rounds until it is approved.
111
111
 
112
112
  Then keep the item in sync with the design:
113
113
 
@@ -1,5 +1,5 @@
1
1
  ---
2
- description: Sync commands and settings to ~/.claude
2
+ description: Sync commands, skills and settings to every installed harness
3
3
  ---
4
4
 
5
- Run `assist sync --yes 2>&1` to copy command files and settings to ~/.claude. This overwrites settings.json without prompting.
5
+ Run `assist sync --yes 2>&1` to copy command files, design resources and settings to every installed harness. This overwrites the Claude settings.json without prompting.
@@ -1 +1 @@
1
- 0.1106.0
1
+ 0.1107.0