peaks-cli 1.0.13 → 1.0.15

package/skills/peaks-ui/SKILL.md

@@ -7,6 +7,16 @@ description: UI and experience skill for Peaks. Use when a workflow touches UI/U
 
 Peaks UI handles experience, interaction, visual direction, and UI-specific refactor artifacts.
 
+## Skill presence (MANDATORY first action)
+
+Before any analysis or tool call, immediately run:
+
+```bash
+peaks skill presence:set peaks-ui --mode <mode> --gate startup
+```
+
+Then display: `Peaks Skill: peaks-ui | Gate: startup | Next: <one short action>`. Update with `peaks skill presence:set peaks-ui --mode <mode> --gate <gate>` when gates change. When the role's work ends, run `peaks skill presence:clear`.
+
 ## Responsibilities
 
 - identify when UI involvement is necessary;
@@ -30,6 +40,7 @@ The default sequence the UI skill should execute. Skip steps that do not apply;
 ```bash
 # 0. confirm UI's own runbook integrity before driving any phase
 peaks skill runbook peaks-ui --json
+peaks skill presence:set peaks-ui               # show persistent skill presence every turn
 
 # 1. capture the UI request as a durable artifact tied to the same PRD request id
 peaks request init --role ui --id <request-id> --project <repo> --json
@@ -55,6 +66,7 @@ peaks mcp apply --capability playwright-mcp.browser-validation --yes --json   #
 # 5. hand off to RD / QA via the cross-linked request id
 peaks request list --project <repo> --json
 peaks request show <request-id> --role ui --project <repo> --json
+peaks skill presence:clear                      # handoff complete, remove presence indicator
 ```
 
 Handoff is blocked until the UI artifact's `state` reaches `direction-locked` or `handed-off`.