This skill should be used for full SB-owned UI/frontend workflow: orient → clarify/decide → test strategy → silver:ui-contract → execute+TDD → silver:ui-review → review → verify → secure → ship
Scanned 9/5/2026
Install to Claude Code
npx -y skills add alo-exp/silver-bullet --skill silver:ui --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Silver:Ui?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/alo-exp-silver-ui-silver-bullet)More formats (shields.io, HTML) on the badges page.
---
name: silver:ui
description: >
This skill should be used for full SB-owned UI/frontend workflow: orient → clarify/decide → test strategy → silver:ui-contract → execute+TDD → silver:ui-review → review → verify → secure → ship
argument-hint: "<UI feature or component description>"
version: 0.2.0
---
# /silver:ui — UI Composition Spec
SB **queue builder** for UI/frontend work. Parent orchestrator seeds the queue and spawns
Task workers per flow — does not implement UI inline.
**Canonical contracts:** `docs/composable-flows-contracts.md`. **Workers:**
`templates/orchestrator-workers/*.md`.
## Standard composition chain
```
FLOW 1 (BOOTSTRAP) [skip if .planning/] → FLOW 2 (ORIENT) → FLOW 3 (CLARIFY) [--spec if no SPEC.md]
→ FLOW 4 (DECIDE) [if design tradeoff] → FLOW 5 (SPECIFY) [compiler if no SPEC.md]
→ FLOW 13 (QUALITY GATE, pre-plan) → FLOW 6 (PLAN) → FLOW 7 (DESIGN CONTRACT)
→ FLOW 8 (EXECUTE) → FLOW 9 (UI QUALITY) → FLOW 10 (REVIEW) → FLOW 12 (VERIFY)
→ FLOW 11 (SECURE) → FLOW 13 (QUALITY GATE, pre-ship) → FLOW 14 (SHIP)
```
FLOW 7 and FLOW 9 are **always** included in this workflow.
Post-execution after FLOW 8: **UI QUALITY → REVIEW → VERIFY → SECURE → VALIDATE →
QUALITY GATE (pre-ship) → SHIP**.
## Conditional insertions
| Signal | Insert / skip |
|--------|----------------|
| `.planning/` exists | Skip FLOW 1 |
| No `.planning/SPEC.md` | **FLOW 3 = `silver:clarify --spec` is mandatory**, then FLOW 5 compiler. Not fuzzy-only. Enforced by `workflow-chain-guard` + `orchestrator-state.sh`. |
| Existing SPEC.md | Skip FLOW 3 `--spec` and FLOW 5 |
| Fuzzy UI intent | FLOW 3 light (not `--spec`) |
| Major UI system / user requests MultAI | Optional multi-AI UX perspectives — not bundled |
| Execution failure | FLOW 15 (DEBUG) |
| Last milestone phase | FLOW 18 via `silver:release` when user confirms |
| `docs/doc-scheme.md` | FLOW 17 checks before FLOW 14 |
## Enforcement queue
**Pre-execution:** `silver:quality-gates` → `silver:context` → `silver:plan`
→ `silver:ui-contract` → `silver:validate` (plus mandatory `silver:clarify --spec` then `silver:spec` when SPEC.md absent)
**Post-execution:** `silver:execute` → `silver:ui-review` → review triad → `silver:verify`
→ `security` → `silver:secure` → `silver:validate` → `silver:quality-gates` (pre-ship)
→ `silver:branch-finish` → `silver:completion-audit` → `silver:ship`
`workflow-chain-guard.sh` enforces pre-execution only at edit time.
## Routing and pre-flight
1. Load preferences from `silver-bullet.md` §10.
2. Banner: `SILVER BULLET ► UI WORKFLOW` + intent + mode.
3. Autonomous default — log `SB ► ui composed {N} paths — orchestrator active`.
## Step-skip protocol
**Non-skippable:** `security`, `silver:quality-gates` pre-ship, `silver:verify`.
## Workflow tracking (fallback)
See `silver:feature` composition spec — same `scripts/workflows.sh` pattern with
`/silver:ui` composer and FLOW names from the chain above.
## Deferred work
File deferred items via `/silver:add` during and after execution.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!