swiftenprofundidad/integrations/config/__tests__/fixtures/skills-compiler/skills/frontend
integrations/config/__tests__/fixtures/skills-compiler/skills/frontend/SKILL.md
# Frontend Guidelines Fixture Do not use empty catch blocks or console.log in production paths.
$ install --global
skillsauthnpx skillsauth add swiftenprofundidad/ast-intelligence-hooks integrations/config/__tests__/fixtures/skills-compiler/skills/frontendInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 21, 2026, 8:54 PM197.6s1 file scanned
SKILL.md
Frontend Guidelines Fixture
Do not use empty catch blocks or console.log in production paths.
Related Skills
swiftenprofundidad/swiftui-expert-skill
development
VerifiedTrustedCommunity
Write, review, or improve SwiftUI code following best practices for state management, view composition, performance, modern APIs, Swift concurrency, and iOS 26+ Liquid Glass adoption. Use when building new SwiftUI features, refactoring existing views, reviewing code quality, or adopting modern SwiftUI patterns.
1SKILL.mdUpdated Apr 21, 2026
swiftenprofundidad/vendor/skills/swift-testing-expert
testing
VerifiedTrustedCommunity
# Swift Testing Expert Use this skill when designing or reviewing modern Swift tests that should align with Swift Testing instead of legacy XCTest-only patterns. ## Focus areas - ✅ Prefer `import Testing` in unit and integration tests. - ✅ Use `#expect` and `#require` instead of `XCTAssert*` and `XCTUnwrap` in modern Swift tests. - ✅ Keep `XCTest` only for UI, performance, or unavoidable legacy compatibility targets. - ✅ Preserve repository-specific test contracts such as `makeSUT()` and memo
1SKILL.mdUpdated Apr 21, 2026
swiftenprofundidad/swift-concurrency
development
VerifiedTrustedCommunity
Expert guidance on Swift Concurrency best practices, patterns, and implementation. Use when developers mention: (1) Swift Concurrency, async/await, actors, or tasks, (2) "use Swift Concurrency" or "modern concurrency patterns", (3) migrating to Swift 6, (4) data races or thread safety issues, (5) refactoring closures to async/await, (6) @MainActor, Sendable, or actor isolation, (7) concurrent code architecture or performance optimization, (8) concurrency-related linter warnings (SwiftLint or similar; e.g. async_without_await, Sendable/actor isolation/MainActor lint).
1SKILL.mdUpdated Apr 21, 2026
swiftenprofundidad/ios-enterprise-rules
tools
VerifiedTrustedCommunity
Reglas iOS/Swift/SwiftUI enterprise del proyecto. Alias canónico neutro.
1SKILL.mdUpdated Apr 21, 2026