- Home
- Skills
- Rshankras
- Claude Code Apple Skills
- Architecture Spec
architecture-spec_skill
- Swift
56
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill rshankras/claude-code-apple-skills --skill architecture-spec- SKILL.md37.0 KB
Overview
This skill generates a complete technical architecture specification for iOS and macOS apps from a Product Requirements Document (PRD). It produces an ARCHITECTURE.md covering architecture pattern, technology stack, data models, and app structure tailored to Apple platform best practices. Use it to accelerate design decisions and produce a shareable architecture artifact for the team.
How this skill works
The skill reads the PRD and any available product plan, extracts core features, non-functional requirements, data model hints, and platform constraints, then selects an opinionated architecture and tech stack (SwiftUI, SwiftData, URLSession, etc.). It outputs a structured ARCHITECTURE.md including high-level diagrams, key decisions, module breakdown, data models, navigation and state management, and persistence strategy. The spec is adjustable by asking for preferences like SwiftUI vs UIKit or third-party library allowances.
When to use it
- When creating ARCHITECTURE.md from a reviewed PRD
- During initial system design for an iOS/macOS MVP
- Before starting implementation to align team on tech choices
- When evaluating trade-offs between frameworks and patterns
- When preparing handoff documentation for engineers
Best practices
- Target iOS 17+/macOS equivalent to leverage @Observable and SwiftData where possible
- Favor SwiftUI and MVVM for most apps; choose TCA or Clean for complex state needs
- Keep third-party dependencies minimal; prefer SPM and Apple frameworks for MVP
- Organize code by feature (Views, ViewModels, Models) with shared Core/Services modules
- Model data with SwiftData @Model, use Keychain for secrets and FileManager for large files
Example use cases
- Generate a draft ARCHITECTURE.md for an iOS app from docs/PRD.md
- Decide between SwiftData and Core Data for persistence given feature needs
- Define navigation and deep-linking strategy using NavigationStack and NavigationPath
- Produce module layout and file examples for onboarding, home, and detail features
- Create data flow and ViewModel examples using @Observable and async/await
FAQ
A reviewed PRD located at docs/PRD.md is required; include product plan or specify preferences if available.
Can I request UIKit or a different pattern instead of MVVM/SwiftUI?
Yes. Provide your preference (UIKit, TCA, VIPER) and the spec will adapt rationale, modules, and tooling accordingly.
Will this include third-party library recommendations?
By default the spec starts with zero third-party dependencies and only recommends packages when they provide clear value; list preferences if you want specific libraries considered.