CrashBytes/claude-role-skills / skills/ux-ui-developer
ux-ui-developer
VerifiedAct as a UX/UI Developer to design user interfaces, build design systems, conduct usability reviews, and implement accessible, responsive front-end components. Use when users need help with wireframing, prototyping, design system creation, component library architecture, accessibility audits (WCAG), responsive design patterns, user flow mapping, usability heuristic evaluation, color theory, typography, or front-end UI implementation. Trigger on mentions of UI design, UX review, wireframes, design system, component library, accessibility, WCAG, responsive layout, user flows, or usability testing.
| File | Kind | Size |
|---|---|---|
| LICENSE.txt | markdown | 11.1 KB |
| SKILL.md | skill md | 9.8 KB |
| references/integrations.md | markdown | 3.0 KB |
| references/ui-patterns.md | markdown | 7.1 KB |
references/integrations.md
View on GitHub# Design and Development Integrations
This skill works best when connected to development platforms via MCP (Model Context Protocol) servers. MCP servers give Claude direct access to repositories, issue trackers, and real-time collaboration channels.
Browse available servers: [MCP Registry](https://registry.modelcontextprotocol.io)
## Detecting Available Integrations
Before performing UI development actions, check what tools are available:
1. **MCP servers** — If GitHub, GitLab, or communication MCP servers are connected, use them directly
2. **CLI tools** — Fall back to `gh`, `glab`, or `npx` via Bash if available
3. **Manual input** — If no integrations detected, ask the user to provide design specs or suggest connecting an MCP server
## GitHub
**Official:** [github/github-mcp-server](https://github.com/github/github-mcp-server)
```bash
claude mcp add github -- npx -y @modelcontextprotocol/server-github
```
Requires `GITHUB_PERSONAL_ACCESS_TOKEN` env var.
**UX/UI actions:** Create issues for accessibility bugs with WCAG references, review PR diffs for design system compliance, query component library repositories, manage design-related labels and milestones.
## GitLab
**Official:** [GitLab MCP Server](https://docs.gitlab.com/user/gitlab_duo/model_context_protocol/mcp_server/)
```bash
claude mcp add gitlab -- npx -y @modelcontextprotocol/server-gitlab
```
Requires `GITLAB_PERSONAL_ACCESS_TOKEN` and `GITLAB_API_URL` env vars.
**UX/UI actions:** Review merge requests for UI changes, manage design system issues, track accessibility audit findings, query component documentation in wikis.
## Jira / Atlassian
**Official:** [atlassian/atlassian-mcp-server](https://github.com/atlassian/atlassian-mcp-server)
```bash
claude mcp add atlassian-mcp-server \
--transport streamable-http \
--url https://mcp.atlassian.com/v1/sse
```
**UX/UI actions:** Track UX research findings in Confluence, manage design task workflows in Jira, link design decisions to implementation stories, query usability testing results.
## Pusher Channels (Real-Time UI)
**Registry:** [Pusher MCP on registry](https://registry.modelcontextprotocol.io/?q=pusher&all=1)
```bash
claude mcp add pusher -- npx -y @AshDevFr/pusher-channels-mcp-server
```
Requires `PUSHER_APP_ID`, `PUSHER_KEY`, `PUSHER_SECRET`, `PUSHER_CLUSTER` env vars.
**UX/UI actions:** Debug real-time UI updates (live notifications, collaborative editing, presence indicators), test WebSocket event flows, verify real-time component behavior, monitor channel subscriptions for live features.
## Integration Detection Pattern
When a user asks for help with UI development or design reviews:
1. Check if any development platform MCP servers are available
2. If yes, use them to review code, manage issues, or access documentation
3. If no MCP tools available, check for CLI tools
4. If nothing available: "I can connect to your development tools via MCP server — see the [MCP Registry](https://registry.modelcontextprotocol.io). Otherwise, share your code or design specs directly."
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |