skills.rest
NBXXF
NBXXFCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

xxf-coding-arch

Define six-directory iOS feature module architecture with unidirectional dependencies.

6|1|Updated May 22, 2025
Search Tags:#architecture#iOS#repository#presentation#feature#module#di
One-click install
npx skills add https://github.com/NBXXF/xxf_ios --skill xxf-coding-arch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: xxf-coding-arch
Source: https://github.com/NBXXF/xxf_ios/tree/main/skills/xxf-coding-arch
Command: npx skills add https://github.com/NBXXF/xxf_ios --skill xxf-coding-arch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture standardization for iOS feature modules to ensure consistent layering and scalable code organization across Api / Domain/DTO / Repository / Service / Di / Presentation.

Core Features & Use Cases

  • Directory structure and responsibilities for Arch, Api, Domain/DTO, Repository, Service, Di, Presentation (ViewModel + Page).
  • Unidirectional dependencies and DTO placement rules; cross-feature service-based communication; centralized DI registration.
  • Use case: creating a new feature module or refactoring an existing module to align with the six-directory model.

Quick Start

Follow the six-directory template for a new Feature, ensure DI entry exists, and migrate existing code to the prescribed layer boundaries.

Frequently Asked Questions about xxf-coding-arch

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

FAQPage Schema
How do I standardize iOS feature module architecture to ensure consistent layering?▼

Standardize iOS feature module architecture by adopting a six-directory structure across Api, Domain/DTO, Repository, Service, Di, and Presentation layers to enforce unidirectional dependencies and proper separation of concerns.

What is the best way to structure directory responsibilities for an iOS feature module?▼

The best way to structure directory responsibilities is dividing code into Arch, Api, Domain/DTO, Repository, Service, Di, and Presentation (ViewModel + Page) directories. This defines clear boundaries and enforces data-driven UI with centralized DI registration.

Where should DTOs be placed when refactoring an iOS feature module?▼

DTOs belong in the Domain/DTO layer within the six-directory structure. This placement enforces unidirectional dependencies and proper separation of concerns, ensuring data transfer objects remain isolated from the Presentation and Repository layers.

Does this iOS feature module architecture support cross-feature communication?▼

Yes, this iOS feature module architecture supports cross-feature communication through service-based interactions. By enforcing unidirectional dependencies and centralized DI registration, modules communicate via defined Service boundaries without direct dependencies.

Can I use this six-directory model for refactoring existing iOS modules instead of creating new ones?▼

Yes, you can use this six-directory model for refactoring existing iOS modules. Migrate existing code to the prescribed layer boundaries across Api, Domain/DTO, Repository, Service, Di, and Presentation layers while ensuring the dedicated Di entry exists.

Do I need a dedicated DI entry point when setting up an iOS feature module?▼

Yes, a dedicated DI entry point is required when setting up an iOS feature module. Centralized DI registration ensures proper dependency injection management and maintains unidirectional dependencies across the Api, Domain, Repository, Service, and Presentation layers.

Related Skills

Explore More Software Engineering Skills→
cshyangcshyang

trigger-setup

Initialize Trigger.dev with npx trigger init and generate trigger.config.ts.

Community
Intermediate
mazicimertmazicimert

test-generator

Generate Swift test templates for unit, integration, and UI tests.

Community
Advanced
imehrimehr

python-backend-guidelines

Optimize Python backend structure with layered patterns for FastAPI, Django, and Flask.

Community
Basic
algusaemalgusaem

architecture-patterns

Apply Clean Architecture, Hexagonal, and DDD patterns to backend systems.

Community
Basic