iOS platform capability orchestration for biometrics, Bluetooth printing, push notifications, native PDF export, and production networking.
Scanned 5/28/2026
Install to Claude Code
npx -y skills add peterbamuhigire/skills-web-dev --skill ios-platform-capabilities --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Ios Platform Capabilities?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/peterbamuhigire-ios-platform-capabilities)More formats (shields.io, HTML) on the badges page.
---
name: ios-platform-capabilities
description: iOS platform capability orchestration for biometrics, Bluetooth printing, push notifications, native PDF export, and production networking.
metadata:
portable: true
compatible_with:
- claude-code
- codex
---
# iOS Platform Capabilities
Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178.
<!-- dual-compat-start -->
## Use When
- Implementing or reviewing iOS capabilities that require Apple frameworks, entitlements, permissions, device hardware, background delivery, or native export.
- The task references LocalAuthentication, CoreBluetooth, APNs, notification extensions, URLSession, offline queues, certificate pinning, or `UIGraphicsPDFRenderer`.
- A retired capability skill is referenced by name.
## Do Not Use When
- The work is general iOS architecture or UI without a platform framework capability.
- The work is StoreKit monetization; use `ios-monetization`.
- The work is security/RBAC governance rather than capability implementation; use `ios-security-and-rbac`.
## Required Inputs
- Capability scope, target iOS versions, entitlements, permission copy, backend/API contract, offline requirements, privacy disclosures, and relevant device constraints.
## Workflow
1. Load `ios-development` for baseline Swift and app-structure rules.
2. Load `ios-security-and-rbac` when the capability touches secrets, identity, device trust, authorization, or tenant data.
3. Pick the reference for the requested capability and follow its implementation workflow.
4. Verify simulator/device limitations, entitlement setup, fallback behaviour, and user-facing permission states.
## Quality Standards
- Capabilities must handle permission denied, unavailable hardware, offline operation where relevant, and background lifecycle constraints.
- Native framework use must be testable, privacy-compliant, and documented in release notes or app-review evidence when required.
## Anti-Patterns
- Implementing hardware or notification features without real-device verification.
- Hiding entitlement, permission, or App Review requirements inside code comments only.
- Building PDF/report/networking features without retry, failure, and export-state handling.
## Outputs
- Capability implementation guidance, framework integration checklist, entitlement/privacy notes, test plan, or review findings.
## References
- `references/ios-biometric-login.md` for Face ID/Touch ID launch gates and LocalAuthentication.
- `references/ios-bluetooth-printing.md` for CoreBluetooth ESC/POS thermal printing.
- `references/ios-push-notifications.md` for APNs, rich notifications, service extensions, and silent push.
- `references/ios-pdf-export.md` for native multipage PDF export with `UIGraphicsPDFRenderer`.
- `references/ios-networking-advanced.md` for production URLSession, typed errors, refresh, pinning, multipart, and offline queues.
<!-- dual-compat-end -->
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!