add-screen

Create SwiftUI screens with MVVM navigation patterns in the Popcorn application.

1|Updated Dec 8, 2025
One-click install
npx skills add https://github.com/adamayoung/popcorn --skill add-screen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-screen
Source: https://github.com/adamayoung/popcorn/tree/main/.claude/skills/add-screen
Command: npx skills add https://github.com/adamayoung/popcorn --skill add-screen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of adding new screens to an existing SwiftUI feature by enforcing a consistent MVVM navigation pattern, preventing architectural drift and reducing boilerplate.

Core Features & Use Cases

  • Navigation Standardization: Ensures all new screens follow the established Router and Navigator pattern.
  • Factory Integration: Automates the wiring of new view models into the central ViewModelFactory.
  • Use Case: When adding a new detail view to the Explore tab, this Skill provides the exact steps to define the route, update the navigator, and wire the view into the NavigationStack.

Quick Start

Use the add-screen skill to guide the implementation of a new MovieCredits screen within the ExploreRoot feature.

Frequently Asked Questions about add-screen

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

FAQPage Schema
How do I add a new screen to a SwiftUI MVVM feature module?

To add a new screen to a SwiftUI MVVM feature module, you create a new view model, define a navigation route, and wire them into the central ViewModelFactory using the established Router and NavigationStack patterns.

What is the best way to standardize SwiftUI navigation across multiple feature screens?

Standardizing SwiftUI navigation involves enforcing a consistent Router and Navigating protocol pattern for every new screen, which prevents architectural drift and reduces boilerplate when integrating features.

How do I wire a new view model into a central factory in SwiftUI?

Wiring a new view model into a central factory in SwiftUI requires adding the view model to the ViewModelFactory and defining its corresponding route within the feature module's Navigator.

Does this screen integration pattern require an existing NavigationStack setup?

Yes, this screen integration pattern requires an existing MVVM-based architecture with a defined NavigationStack, Router, and Navigating protocol to properly route and display new views.

Why should I use a Router pattern when adding SwiftUI views?

Using a Router pattern when adding SwiftUI views ensures consistent navigation standardization across feature modules, preventing architectural drift and reducing repetitive boilerplate code.