add-context

Generate clean-architecture package structures for new SwiftUI business domains.

1|Updated Dec 8, 2025

Search Tags:#architecture #scaffolding #swift #domain-driven-design #swiftui #modularization

Ready to run

npx skills add https://github.com/adamayoung/popcorn --skill add-context-adamayoung

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: add-context
Source: https://github.com/adamayoung/popcorn/tree/main/.claude/skills/add-context
Command: npx skills add https://github.com/adamayoung/popcorn --skill add-context-adamayoung

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates architectural drift and boilerplate overhead when adding new business domains to the Popcorn codebase by enforcing a consistent, clean-architecture structure.

Core Features & Use Cases

Automated Scaffolding: Generates the complete directory structure for a new context, including Domain, Application, Infrastructure, and Composition layers.
Dependency Enforcement: Ensures strict adherence to the project's dependency graph by providing templates for Package.swift and factory classes.
Use Case: When adding a new feature like a Watchlist or Reviews system, this skill provides the exact blueprint to ensure the new code integrates seamlessly with existing TMDb adapters and the AppServices dependency graph.

Quick Start

Use the add-context skill to generate the full package structure and boilerplate code for a new business domain named UserProfile.

Frequently Asked Questions about add-context

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

FAQPage Schema

How do I standardize new business domains in a modular SwiftUI architecture?▼

To standardize new business domains in a modular SwiftUI architecture, you can use automated scaffolding to generate clean architecture layers, ensuring consistent directory structures for domain entities, use cases, and infrastructure repositories across feature modules.

What is the best way to prevent architectural drift when adding new feature modules in Swift?▼

Preventing architectural drift when adding new feature modules in Swift requires enforcing a strict clean architecture structure with standardized templates for dependency injection and composition root integration, eliminating inconsistent boilerplate code across the project.

How do I scaffold domain-driven design layers for a new feature in Swift?▼

Scaffolding domain-driven design layers for a new Swift feature involves generating the complete directory structure across Domain, Application, Infrastructure, and Composition layers, providing the exact blueprint for seamless integration with existing adapters.

Does this scaffolding approach support strict dependency enforcement for SwiftUI composition roots?▼

Yes, this scaffolding approach supports strict dependency enforcement for SwiftUI composition roots by providing standardized templates for Package.swift configurations and factory classes, ensuring new business domains adhere to the project's established dependency graph.

Can I integrate new domain contexts with existing infrastructure adapters and AppServices?▼

You can integrate new domain contexts with existing infrastructure adapters and AppServices by using standardized boilerplate generation that ensures seamless compatibility and correct dependency wiring within the modular architecture's composition root.

When do I need to generate clean architecture boilerplate for a new Swift domain?▼

You need to generate clean architecture boilerplate for a new Swift domain when adding complex feature systems like a Watchlist or Reviews module, ensuring the new code maintains strict architectural boundaries and integrates seamlessly with existing TMDb adapters.