app-planner

Creates planning documents for new macOS apps and analysis reports for existing projects.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/RavitejaKarra24/dotfiles --skill app-planner-ravitejakarra24
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: app-planner
Source: https://github.com/RavitejaKarra24/dotfiles/tree/main/agents/.agents/skills/macos-development/app-planner
Command: npx skills add https://github.com/RavitejaKarra24/dotfiles --skill app-planner-ravitejakarra24

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a macOS app without a clear plan leads to architecture mistakes, scope creep, and rework, while auditing an existing codebase manually is slow and inconsistent. This Skill produces structured planning and analysis documents covering architecture, data models, UI/UX, testing, and distribution. ## Core Features & Use Cases - New App Planning: Generates 8 planning documents covering feature specification, architecture decisions (SwiftUI vs AppKit, MVVM), SwiftData data models, UI/UX wireframes, tech stack, project structure, testing strategy, and distribution plan. - Existing App Analysis: Produces 10 audit documents covering architecture, code quality (SOLID/DRY), Liquid Glass and HIG compliance, performance, accessibility, security, dependencies, test coverage, and a modernization roadmap. - Use Case: You have an idea for a menu-bar productivity app. Ask the Skill to plan it, and receive a complete document set including SwiftData schema design, SwiftUI navigation structure, and a Mac App Store distribution checklist. ## Quick Start Ask the assistant to plan a new macOS app or analyze an existing macOS project, then answer its questions about requirements and goals.

Frequently Asked Questions about app-planner

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

FAQPage Schema
How do I plan a new macOS app before writing code?

Start by defining features, architecture, and data models before implementation. This Skill generates 8 planning documents covering feature specification, SwiftUI vs AppKit decisions, SwiftData schema design, UI/UX wireframes, testing strategy, and distribution planning.

How to audit an existing macOS project for code quality?

Audit a macOS project by reviewing architecture, SOLID and DRY compliance, dependencies, and test coverage. This Skill produces 10 analysis documents including performance profiling, accessibility review, security checks, and a modernization roadmap.

Should I use SwiftUI or AppKit for a new macOS app?

SwiftUI suits most new apps with declarative UI and modern framework integration, while AppKit fits apps needing fine-grained control or legacy compatibility. The planning documents include an architecture decision section comparing SwiftUI, AppKit, and hybrid approaches.

Does the analysis cover migration from Core Data to SwiftData?

Yes, the existing app analysis includes a data layer review and a modernization roadmap covering Core Data to SwiftData migration, Objective-C to Swift conversion, Intel to Apple Silicon, and Liquid Glass adoption with a priority timeline.

What are the limitations of automated app planning documents?

Planning documents reflect the requirements you provide, so vague answers produce generic output. They guide architecture and scope decisions but do not replace prototyping, user research, or hands-on performance benchmarking on real devices.