Stats
Actions
Tags
From swiftui
Audits project for hygiene: no secrets in repo, comments/tests presence, keychain for sensitive data, SwiftLint compliance, string catalog best practices, Xcode MCP usage. Reports issues and fixes.
How this command is triggered — by the user, by Claude, or both
Slash command
/swiftui:hygieneswiftui-review/references/The summary Claude sees in its command listing — used to decide when to auto-load this command
# Hygiene - If the project requires secrets such as API keys, never include them in the repository. - Code comments and documentation comments should be present where the logic isn't self-evident. - Unit tests should exist for core application logic. UI tests only where unit tests are not possible. - `@AppStorage` must never be used to store usernames, passwords, or other sensitive data. Use the keychain for that. - If SwiftLint is configured, it should return no warnings or errors. - If the project uses Localizable.xcstrings, prefer to add user-facing strings using symbol keys (e.g. “hell...
@AppStorage must never be used to store usernames, passwords, or other sensitive data. Use the keychain for that.extractionState set to "manual", accessing them via generated symbols such as Text(.helloWorld). Offer to translate new keys into all languages supported by the project.RenderPreview is able to capture images of rendered SwiftUI previews for examination, and DocumentationSearch can search Apple’s documentation for latest usage instructions.npx claudepluginhub fradser/dotclaude --plugin swiftui/swiftlintRuns SwiftLint to check Swift code style and reports violations by severity. Also supports auto-fix and strict mode.
/swift-lintFormats and lints Swift code using swift-format on the specified path (or current directory). Launches agent with isolated context, reports summary and modified files count.