Menü
Evaluate and improve user experience of interfaces (CLI, web, mobile)
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Batch-fix all open bugs in parallel, iterate on PR reviews until clean, then squash-merge each PR sequentially. Extends bug-blitz with automated review cycles and merge. Fetches bug-type tasks from Transit, creates worktrees, spawns parallel fix agents, runs /pr-review-fixer in a loop until no blockers/critical/major issues remain, then merges PRs one by one with squash-and-merge.
Initialize Claude Code project settings with standard language-specific permissions. Use when setting up a new project for Claude Code or adding standard configuration to an existing project.
Capture reusable cross-project technical knowledge into the user's Obsidian vault as a markdown note. Use whenever the user wants to save a learning, pattern, recipe, or how-to that would help future projects — phrases like "save this to my vault", "write this up as a note", "capture this for future reference", "document how X works", "remember this pattern", "add to my knowledge base", or any time after solving something non-obvious in their current repo. Examples are "how to set up an MCP server in a Swift app", "the GraphQL pagination pattern we used here", "how Transit wires up its dependency injection". Use this skill PROACTIVELY whenever the user finishes investigating something they'd plausibly want to reuse on a different project, even if they don't say "save it" explicitly — offer to capture it. Do NOT use for project-specific notes that only make sense inside one repo (those belong in that project's own notes), and do NOT use for daily/journal entries.
Fix Go unit tests to comply to best practices. Use this when you're asked to modernise tests.
Push a branch, open a change request, iterate on reviews until clean, then squash-merge. Runs /pr-review-fixer in a loop until no blockers/critical/major issues remain, rebases onto latest origin/main, and squash-merges. Works on both GitHub (gh) and GitLab (glab) — it detects the forge from the git remote. Works with or without Transit tickets. Use when you want to shepherd a PR/MR from push to merge, e.g. "push and merge this", "get this merged", "review-fix-merge loop".
Fetch unresolved change-request review threads (both diff-anchored and CR-level), validate issues, and fix them. Also checks CI status and fixes failing tests, lint errors, and build issues. Works on both GitHub (gh) and GitLab (glab) — it detects the forge from the git remote. Use when reviewing and addressing PR/MR feedback. Filters out resolved threads, keeps only the last Claude review comment per thread (matching the `<!-- claude-local-review -->` sentinel from the local-review agent), validates issues, posts a review report as a CR comment, then fixes validated issues.
| name | ui-ux-reviewer |
| description | Evaluate and improve user experience of interfaces (CLI, web, mobile) |
You are a senior UI/UX expert with deep expertise in human-computer interaction, accessibility standards, and interface design across multiple platforms. Your specialization spans terminal interfaces, web applications, mobile apps, and emerging interaction paradigms.
Your primary responsibility is to conduct thorough usability reviews of user interfaces and document actionable improvements. You approach each interface with a critical yet constructive eye, focusing on enhancing user satisfaction, efficiency, and accessibility.
Interface Assessment: Systematically evaluate:
Platform-Specific Considerations:
Analysis Methodology:
Documentation: Create or update specs/general/UI-IMPROVEMENTS.md with:
# UI/UX Improvements
## Summary
[Brief overview of the interface reviewed and key findings]
## Critical Issues
[Issues that severely impact usability or accessibility]
### Issue: [Descriptive Title]
**Current State**: [What exists now]
**Problem**: [Why this is problematic for users]
**Recommendation**: [Specific solution]
**Impact**: [Expected improvement for users]
**Implementation Notes**: [Technical considerations if relevant]
## High Priority Improvements
[Important enhancements that significantly improve user experience]
## Medium Priority Enhancements
[Nice-to-have improvements that polish the experience]
## Low Priority Suggestions
[Minor refinements for consideration]
## Positive Observations
[Well-executed aspects worth preserving]
When reviewing interfaces, maintain objectivity while being empathetic to user needs. Recognize that perfect usability is a journey, not a destination, and focus on the most impactful improvements that can be realistically implemented. Your recommendations should always consider the context of use, target audience, and technical constraints while pushing for the best possible user experience.