Menu
Audits SwiftUI code for accessibility compliance — Dynamic Type, VoiceOver, Voice Control, Reduce Motion, and color-independent UI. Use when reviewing SwiftUI views for a11y issues or adding accessibility support to existing code.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | swiftui-accessibility |
| description | Audits SwiftUI code for accessibility compliance — Dynamic Type, VoiceOver, Voice Control, Reduce Motion, and color-independent UI. Use when reviewing SwiftUI views for a11y issues or adding accessibility support to existing code. |
Respect the user's accessibility settings for fonts, colors, animations, and motion. Flag only genuine problems — do not nitpick.
.font(.body), .font(.headline), etc.).@ScaledMetric..font(.body.scaled(by:)) is also available.Icon-only buttons are bad for VoiceOver. Always include text, even if visually hidden:
// Bad
Button(action: addUser) {
Image(systemName: "plus")
}
// Good
Button("Add User", systemImage: "plus", action: addUser)
SwiftUI usually picks the right label style for context (e.g., toolbar buttons become icon-only). If you must keep an icon-only visual while preserving the text for VoiceOver, apply .labelStyle(.iconOnly).
The same rule applies to Menu: Menu("Options", systemImage: "ellipsis.circle") { } is much better than icon-only.
Decorative images should use Image(decorative:) or accessibilityHidden(true). Meaningful images need accessibilityLabel().
Flag asset names that produce unhelpful VoiceOver readings (e.g., Image(.newBanner2026)).
"AAPL $271.68"), add accessibilityInputLabels(["Apple"]) to give Voice Control a stable hook..accessibilityDifferentiateWithoutColor enabled aren't lost.onTapGesture() unless you specifically need tap location or count. Use Button for everything else.onTapGesture() is unavoidable, add .accessibilityAddTraits(.isButton) (or similar) so VoiceOver reads it correctly.This guidance is adapted from the SwiftUI Pro agent skill by Paul Hudson (MIT-licensed).
Searches public and structured sources for a target company (A-share, HK, US, or private) and produces a Chinese rough-read gate or structured research report. Optimized for price-first company screening: valuation gate, bottom type, red flags, business snapshot, financial quality, and whether the company deserves deeper research. Every quantitative claim must be traceable to a logged source. Use when researching a listed company, supplier, customer, competitor, or acquisition target.
Generates Chinese patent disclosure packages from invention notes, prior-art references, and optional Notion context. Use when researching patent background, drafting disclosure sections, or running an end-to-end patent disclosure workflow.
Designs intuitive Python library APIs following principles of simplicity, consistency, and discoverability. Handles API evolution, deprecation, breaking changes, and error handling. Use when designing new library APIs, reviewing existing APIs for improvements, or managing API versioning and deprecations.
Builds command-line interfaces for Python libraries using Click or Typer. Includes command groups, argument handling, progress bars, shell completion, and CLI testing with CliRunner. Use when adding CLI functionality to a library or building standalone command-line tools.
Improves Python library code quality through ruff linting, mypy type checking, Pythonic idioms, and refactoring. Use when reviewing code for quality issues, adding type hints, configuring static analysis tools, or refactoring Python library code.
Builds and manages open source Python library communities including CONTRIBUTING.md, CODE_OF_CONDUCT.md, issue/PR templates, contributor recognition, and GitHub automation. Use when setting up community infrastructure, improving contributor experience, or managing project governance.