sirius-cc-wu/ui-flow
skills/ui-flow/SKILL.md
Captures optional UI and UX flows, screen-level requirements, and interaction notes before implementation.
$ install --global
skillsauthnpx skillsauth add sirius-cc-wu/sirius-skills ui-flowInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 22, 2026, 12:48 PM124.2s1 file scanned
SKILL.md
- name:
- ui-flow
- description:
- Captures optional UI and UX flows, screen-level requirements, and interaction notes before implementation.
UI Flow
Use this skill when a project needs screen flows, interaction requirements, or UX notes before implementation work is decomposed.
Responsibilities
- Capture user journeys, states, and interaction boundaries.
- Define screen-level requirements, transitions, and edge cases.
- Record UX constraints that should influence system design or slice breakdown.
- Keep UI decisions in repository documents instead of burying them in ad hoc execution notes.
Required Output
<feature_path>/ui-design.md
Optional companion output:
- updates to
<feature_path>/user-stories.md - links to mockups or external design references
Feature Path Resolution
Resolve <feature_path> as <planning_dir>/<feature-slug>/.
- If
.skills/planning.jsondefinesplanning_dir, use that as<planning_dir>. - Otherwise default to
docs/features.
Workflow
- Read
discover.mdandsystem-design.mdwhen present. - Capture flows, states, and notable UX constraints.
- Write
ui-design.mdwith screen-level requirements and edge cases. - Refine story boundaries or acceptance notes if the UI changes scope.
- Run
python3 skills/guide-planning/scripts/manage_planning.py sync-status <feature-selector> --through design_readywhen the feature requires UI flow so metadata catches up once the design packet is complete. - Stop when the UI work is concrete enough for
breakdown.
Guardrails
- Keep the output lightweight and implementation-relevant.
- Do not create implementation slices from UX notes alone.
- If the project has no meaningful UI surface, skip this skill.
Related Skills
sirius-cc-wu/ship-worktree
tools
VerifiedTrustedCommunity
Create or resume a dedicated git worktree for one feature or subfeature, drive `ship` inside that worktree, and hand the finished branch back as a pull request to the original branch.
4SKILL.mdUpdated May 6, 2026
sirius-cc-wu/reconcile-execution
testing
VerifiedTrustedCommunity
Reviews one completed feature or subfeature against final implementation and slice artifacts, then records a durable reconciliation block before archive.
4SKILL.mdUpdated May 6, 2026
sirius-cc-wu/governance-update
development
VerifiedTrustedCommunity
Tightens durable repo-level rules in AGENTS.md and adjacent governance surfaces when repeated drift reveals a policy gap.
4SKILL.mdUpdated Apr 29, 2026
sirius-cc-wu/ship
data-ai
VerifiedTrustedCommunity
Resolves one reviewed feature or subfeature backlog into remaining planned slices and routes each active slice to the next owning execution step with one commit per completed slice.
4SKILL.mdUpdated Apr 22, 2026