uiux-ops
Improve UI/UX Design Operations
UI and UX work often loses consistency across screens, states, and decisions. This skill gives Claude, Codex, and Claude Code a concise checklist for design reviews and documentation.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "uiux-ops" from https://skillstore.io/skills/a-genno-uiux-ops.md and its manifest at https://skillstore.io/api/skills/a-genno-uiux-ops/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "uiux-ops". Review a checkout form for mobile readiness.
Expected outcome:
The review highlights missing loading feedback after payment, inconsistent error text, cramped spacing, and unclear keyboard behavior.
Using "uiux-ops". Prepare UIUX.md notes for a new settings panel.
Expected outcome:
The notes summarize component choices, color usage, typography rules, interaction states, and the reason for the design change.
Using "uiux-ops". Create a design-system checklist for a dashboard.
Expected outcome:
The checklist covers reusable cards, semantic colors, heading hierarchy, spacing rules, responsive layouts, error states, and documentation tasks.
Security Audit
SafeThe static command findings are false positives caused by Markdown inline code references to UIUX.md on lines 27 and 28. The entropy heuristic is also a false positive because SKILL.md is readable Markdown with Japanese text and no obfuscated payload. No semantic security findings or prompt injection attempts were found.
Risk Factors
⚙️ External commands (2)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/a-genno-uiux-ops/audits/10?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/a-genno-uiux-ops?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/a-genno-uiux-ops?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/a-genno-uiux-ops/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/a-genno-uiux-ops.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
A-Genno. (2026). uiux-ops security audit report (audit version 10) [Author version unspecified]. Skillstore. https://skillstore.io/skills/a-genno-uiux-ops/audits/10BibTeX citation
@techreport{a-genno-a-genno-uiux-ops-2026,
author = {A-Genno},
title = {uiux-ops security audit report (audit version 10)},
institution = {Skillstore},
year = {2026},
number = {10},
url = {https://skillstore.io/skills/a-genno-uiux-ops/audits/10},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "uiux-ops security audit report (audit version 10)"
version: "unspecified"
type: report
authors:
- name: "A-Genno"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/a-genno-uiux-ops/audits/10"
identifiers:
- type: other
value: "skillstore:a-genno-uiux-ops:audit:10"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Standardize design reviews
Use the checklist to review screens for consistency, accessibility, responsive behavior, and interaction states.
Check implementation readiness
Review components, colors, typography, spacing, errors, and loading states before frontend development begins.
Record design decisions
Capture UI/UX rationale and changes in UIUX.md so product and delivery teams share one reference.
Try These Prompts
Use uiux-ops to review this screen description for user goals, consistency, accessibility, and responsive behavior: [screen details].
Create a UI/UX checklist for [feature] using component, color, typography, spacing, feedback, error, and loading considerations.
Draft concise UIUX.md updates for [change]. Include design rationale, affected components, interaction states, and follow-up checks.
Audit [workflow] across desktop and mobile. Identify inconsistencies in components, states, accessibility, responsive layout, and documentation gaps.
Best Practices
- Start each review with the user's primary goal and success criteria.
- Check components, colors, typography, and spacing against the same design system.
- Record design decisions and UI changes in UIUX.md during the same workflow.
Avoid
- Reviewing visual polish without checking error, loading, and feedback states.
- Changing interface patterns without documenting the reason and affected components.
- Treating desktop layouts as complete without testing smaller screens.