Agent skill
Swift Tooling
Standards for SPM, Build Configs, and Code Quality
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/tooling-hoangnguyen0403-agent-skills-standar-3
Metadata
Additional technical details for this skill
- labels
-
swift tooling spm swiftlint
- triggers
-
{ "files": [ "Package.swift", ".swiftlint.yml" ], "keywords": [ "package", "target", "dependency" ] }
SKILL.md
Swift Tooling Standards
Priority: P0
Implementation Guidelines
Swift Package Manager (SPM)
- Package.swift: Define clear targets, products, and dependencies.
- Modularization: Break large projects into local packages for faster builds.
- Versioning: Use semantic versioning (Major.Minor.Patch) for shared packages.
Code Quality
- SwiftLint: Use for consistent style enforcement. Adhere to project-wide
.swiftlint.yml. - Compiler Warnings: Treat warnings as errors in CI to maintain code health.
- Documentation: Use DocC-style comments (
///) for public APIs.
Build Configurations
- Xcconfig: Use external configuration files to manage build settings.
- Environment Flags: Use
#if DEBUGfor development-only code. - Schemes: Maintain separate schemes for Development, Staging, and Production.
Anti-Patterns
- Hardcoded Secrets:
**No API keys in code**: Use environment variables or build configs. - Ignoring Lint Errors:
**No // swiftlint:disable**: Fix the underlying issue. - Manual Dependency Copying:
**No manually added frameworks**: Use SPM.
References
- SPM Setup & Build Configs
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?