By fradser
Review SwiftUI and Swift codebases for modern APIs, best practices, performance, accessibility, data flow, navigation, Clean Architecture, and hygiene issues. Receive prioritized summaries with file-by-file issues and before/after fixes to refactor efficiently.
npx claudepluginhub fradser/dotclaude --plugin swiftuiReviews SwiftUI code for best practices on modern APIs, maintainability, and performance. This skill should be used when the user asks to review SwiftUI code, check for deprecated iOS/macOS APIs, validate data flow patterns, or audit accessibility compliance in Swift projects.
- Respect the user’s accessibility settings for fonts, colors, animations, and more.
- Always use `foregroundStyle()` instead of `foregroundColor()`.
Clean Architecture separates code into layers: Presentation → Domain ← Data. Dependencies point inward.
It is important that SwiftUI body code and logic code be kept separate in order to make code easier to read, write, and maintain. That usually means placing code into methods rather than inline in the `body` property, but often also means carving functionality out into separate `@Observable` classes.
Prefer to place standard fonts, sizes, colors, stack spacing, padding, rounding, animation timings, and more into a shared enum of constants, so they can be used by all views. This allows the app’s design to feel uniform and consistent, and be adjusted easily.
- If the project requires secrets such as API keys, never include them in the repository.
- Use `NavigationStack` or `NavigationSplitView` as appropriate; flag all use of the deprecated `NavigationView`.
- When toggling modifier values, prefer ternary expressions over if/else view branching to avoid `_ConditionalContent`, preserve structural identity, and avoid repeatedly recreating underlying platform views.
- Prefer Swift-native string methods over Foundation equivalents: use `replacing("a", with: "b")` not `replacingOccurrences(of: "a", with: "b")`.
- Strongly prefer to avoid breaking up view bodies using computed properties or methods that return `some View`, even if `@ViewBuilder` is used. Extract them into separate `View` structs instead, placing each into its own file.
English | 简体中文
A curated collection of 15 plugins for Claude Code, providing specialized agents, skills, and automation tools for development and productivity workflows.
Conventional Git automation for commits and repository management with AI code quality checks.
Installation:
claude plugin install git@frad-dotclaude
GitFlow workflow automation for feature, hotfix, and release branches with semantic versioning.
Installation:
claude plugin install gitflow@frad-dotclaude
GitHub project operations with quality gates, TDD workflows, and comprehensive validation.
Installation:
claude plugin install github@frad-dotclaude
Advanced development workflow orchestration with BDD support and Agent Team execution for complex projects.
Installation:
claude plugin install superpowers@frad-dotclaude
Code simplification and refactoring with language-specific patterns and cross-file optimization.
Installation:
claude plugin install refactor@frad-dotclaude
SwiftUI Clean Architecture reviewer for iOS/macOS development with best practices enforcement.
Installation:
claude plugin install swiftui@frad-dotclaude
Generate comprehensive CLAUDE.md configuration files with environment detection and interactive workflow.
Installation:
claude plugin install claude-config@frad-dotclaude
Patent application generation, Feishu document creation, and Product Requirements Documents.
Installation:
claude plugin install office@frad-dotclaude
Validate and optimize Claude Code plugins against official best practices with agent-based fixes.
Installation:
claude plugin install plugin-optimizer@frad-dotclaude
Next.js development tools integration via MCP server for routing, components, and API analysis.
Installation:
claude plugin install next-devtools@frad-dotclaude
Knowledge base for acpx - a headless ACP CLI for agent-to-agent communication.
Installation:
claude plugin install acpx@frad-dotclaude
Manages shadcn components - adding, searching, fixing, debugging, styling, and composing UI.
Installation:
claude plugin install shadcn@frad-dotclaude
Five methods to retrieve code context: DeepWiki, Context7, Exa, git clone, and web search.
Installation:
claude plugin install code-context@frad-dotclaude
General-purpose utility skills for documentation, writing, and project maintenance.
Installation:
claude plugin install utils@frad-dotclaude
Enforces task clarity before execution and requires verified work before exit.
Installation:
claude plugin install meeseeks-vetted@frad-dotclaude
plugin-name/..claude-plugin/plugin.json with required metadata..claude-plugin/marketplace.json./utils:update-readme to sync both README files.Reviews SwiftUI code for best practices on modern APIs, maintainability, and performance.
SwiftUI のレイアウト落とし穴・ベストプラクティスガイド + Hit Area Auditor サブエージェント。ATT呼び出しタイミング、.buttonStyle(.plain) + contentShape、CRUD 機能網羅チェック、アフォーダンスチェックを含む
This skill should be used when writing or reviewing Swift code for iOS or macOS projects. Apply modern Swift 6+ best practices, concurrency patterns, API design guidelines, and migration strategies. Covers async/await, actors, MainActor, Sendable, typed throws, and Swift 6 breaking changes.
Advanced Swift programming skills for iOS and protocol-oriented programming
Agents and skills for Swift app development on iOS.
Runs pre-commands
Contains inline bash commands via ! syntax
Bash prerequisite issue
Uses bash pre-commands but Bash not in allowed tools
Share bugs, ideas, or general feedback.
Expert Swift 6.2 + SwiftUI for iOS 26, macOS 26, iPadOS 26, watchOS 26, visionOS 26, tvOS 26 with Liquid Glass, @Observable, actors, SwiftData inheritance
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claim