swiftenprofundidad
13 verified skills13 total stars
enterprise-operating-system
Activa el método enterprise reusable de arquitectura e ingeniería cuando un repo necesita arrancar, gobernarse o ejecutarse con disciplina profesional: freeze de release, contrato de arquitectura, vertical slices, gates, evidencias, enforcement y consumo correcto por AGENTS.md, .agents/skills y vendor/skills. Úsalo tanto en proyectos greenfield como brownfield, V2, refactors grandes, reducción de deuda técnica o rescates arquitectónicos.
development1
integrations/config/__tests__/fixtures/skills-compiler/skills/backend
# Backend Guidelines Fixture Do not use empty catch blocks or console.log in runtime paths.
development1
frontend-enterprise-rules
Reglas frontend enterprise (React/Next.js/TypeScript) del proyecto. Alias canónico neutro.
development1
vendor/skills/core-data-expert
# Core Data + SwiftData Expert Use this skill when auditing or implementing Core Data or SwiftData code that must remain safe across contexts, layers, and async boundaries. ## Focus areas - ✅ Prefer `NSManagedObjectID` or mapped DTO/domain models over passing `NSManagedObject` across boundaries. - ✅ Avoid returning or accepting `NSManagedObject` in async APIs that cross actor or context boundaries. - ✅ Keep Core Data orchestration inside infrastructure or repository layers instead of presenta
development1
swift-concurrency
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).
development1
vendor/skills/swift-testing-expert
# 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
testing1
integrations/config/__tests__/fixtures/skills-compiler/skills/android
# Android Guidelines Fixture Do not use Thread.sleep or GlobalScope in production code.
development1
android-enterprise-rules
Reglas Android/Kotlin/Compose enterprise del proyecto. Alias canónico neutro.
tools1
backend-enterprise-rules
Reglas backend enterprise (NestJS/TypeScript) del proyecto. Alias canónico neutro.
development1
integrations/config/__tests__/fixtures/skills-compiler/skills/frontend
# Frontend Guidelines Fixture Do not use empty catch blocks or console.log in production paths.
development1
integrations/config/__tests__/fixtures/skills-compiler/skills/ios
# iOS Guidelines Fixture Do not use force unwrap or force try in production code. Avoid AnyView in SwiftUI layers.
development1
swiftui-expert-skill
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.
development1
ios-enterprise-rules
Reglas iOS/Swift/SwiftUI enterprise del proyecto. Alias canónico neutro.
tools1