app-planner_skill

Overview

This skill guides you through comprehensive iOS/Swift app planning and analysis for both new projects and existing codebases. It covers product definition, architecture and data decisions, UI/UX planning, non-functional requirements, and distribution strategy. Use it to produce a structured plan, documentation files, and actionable recommendations. The goal is a clear roadmap you can implement or hand off to a team.

How this skill works

I first determine whether you’re planning a new app or auditing an existing one, then gather project context like scope, stage, codebase size, and pain points. For new apps I run a phased workflow: product planning, technical planning, UI/UX design, non-functional requirements, and distribution. For existing apps I perform an architecture and tech-stack review, identify risks and technical debt, and recommend refactors and priorities. The skill can generate a set of planning documents (overview, features, architecture, tech stack, UI/UX, data model, personas, roadmap) placed in your chosen folder.

When to use it

• Planning a new iOS/Swift app from concept to MVP
• Choosing architecture, persistence, or UI framework for a project
• Auditing an existing app to find technical debt and refactor paths
• Preparing App Store distribution, monetization, or localization strategy
• Creating documentation and a milestone-based roadmap for development

Best practices

• Start by defining core user value and an MVP feature set before technical choices
• Choose architecture based on team experience, app size, and testability (e.g., MVVM, TCA)
• Pick a persistence solution aligned with data complexity and iOS version support (Core Data, SwiftData, Realm)
• Design a minimal component library and accessibility-first UI patterns from the start
• Document decisions and trade-offs in version-controlled planning files in a clear docs/ folder

Example use cases

• Define MVP scope, user journeys, and prioritized feature list for a startup app
• Recommend architecture and module boundaries for a medium-sized SwiftUI app
• Audit an aging UIKit codebase to surface performance bottlenecks and refactor candidates
• Decide between SwiftData and Core Data and plan data migration strategy
• Prepare App Store metadata, screenshots, and a phased release roadmap