architecture-spec

What it does

Generates technical architecture specification for iOS/macOS app.

How it works

• Activates when the user says any of: "generate architecture", "create technical spec", "write architecture document", "generate architecture spec", "design technical architecture", or "create ARCHITECTURE.md".
• Reads PRD from docs/PRD.md and optional inputs like a Product development plan and User preferences to inform decisions.
• Outputs a Markdown document docs/ARCHITECTURE.md with a structured layout including: Overview, Architecture Pattern, High-Level Component Diagram, Key Architectural Decisions, Technology Stack, App Structure, Data Models, Navigation Architecture, and Data Flow (State Management, Persistence, Networking).
• Applies an opinionated selection within Apple best practices across UI framework, data persistence, architecture pattern, networking, and state management, while detailing rationale for choices.
• Uses a SwiftUI-based architecture with MVVM-like considerations, SwiftData for persistence, URLSession for networking, and NavigationStack for navigation.
• Produces a detailed component diagram and code snippets illustrating how to organize the project and how data flows from user actions to persistence.

When to use it

• Use when you have a PRD and MVP scope clearly defined and you want a documented technical architecture to guide implementation.
• Use when you need to specify architectural pattern, data models, app structure, and technology decisions for an iOS/macOS Apple platform project.

What it can touch

• Reads: docs/PRD.md
• Writes: docs/ARCHITECTURE.md
• No external file creation beyond ARCHITECTURE.md, as described in the output section.

Caveats

• Assumes PRD exists at docs/PRD.md and MVP scope is clear.
• Content is based on the provided inputs and stated preferences; changes to PRD can alter the recommended architecture.