macos-app-planner

Generate structured planning documents for new and existing macOS apps.

4|1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/AutisticAF/claude-code-apple-dev-plugin --skill macos-app-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: macos-app-planner
Source: https://github.com/AutisticAF/claude-code-apple-dev-plugin/tree/main/skills/macos-app-planner
Command: npx skills add https://github.com/AutisticAF/claude-code-apple-dev-plugin --skill macos-app-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

macOS app planning and governance is often fragmented across documents, leading to misalignment and slow progress. This skill generates a cohesive set of planning artifacts covering architecture, features, UI/UX, and tech stack to accelerate kickoff and maintain consistency.

Core Features & Use Cases

  • New App Planning: Create 8 planning documents for new macOS projects.
  • Existing App Analysis: Create 10 analysis documents for existing macOS apps.
  • Reference-guided templates: Use referenced guidance to ensure consistency and traceability.

Quick Start

Clarify whether this is a new app or an existing app analysis, then generate the full planning package.

Frequently Asked Questions about macos-app-planner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan architecture and UX for a new macOS app?

To plan architecture and UX for a new macOS app, this Skill generates eight structured planning documents covering architecture, features, UI/UX, data, and deployment artifacts to accelerate project kickoff.

Can I generate planning documents to audit an existing macOS SwiftUI project?

Yes, you can audit an existing macOS SwiftUI project by generating ten structured analysis documents that evaluate current architecture, features, and UI/UX for governance and consistency.

What is the best way to structure macOS app project management and governance?

Structuring macOS app project management is best achieved by generating a cohesive set of planning artifacts covering architecture, features, UI/UX, and tech stack, which prevents fragmented documentation and misalignment.

Do I need specific dependencies to generate macOS architecture planning documents?

No specific dependencies are required to generate macOS architecture planning documents; the Skill operates independently using its internal references folder to provide guidance and ensure template consistency.

How does the reference-guided template system work for macOS app planning?

The reference-guided template system works by utilizing an included references folder to ensure traceability and consistency across generated architecture, UI/UX, and deployment planning documents for macOS apps.

What limitations exist when planning tech stack and deployment for macOS apps?

A limitation is that planning focuses specifically on macOS and SwiftUI contexts; it generates static planning artifacts rather than executable code, meaning deployment planning requires manual implementation afterward.