skills.rest
vjr2005
vjr2005COMMUNITY
Explore all skills by this author →
GitHub

project-structure

Organize iOS project directories into canonical App, AppKit, Libraries, Features, Shared, and Derived sections.

Updated Jan 15, 2026
Search Tags:#architecture#ios#guidelines#project-structure#module-design#directory-layout
One-click install
npx skills add https://github.com/vjr2005/Challenge --skill project-structure-vjr2005
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-structure
Source: https://github.com/vjr2005/Challenge/tree/main/.claude/skills/project-structure
Command: npx skills add https://github.com/vjr2005/Challenge --skill project-structure-vjr2005

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides teams to standardize and understand large iOS codebases by providing a canonical directory layout and naming conventions.

Core Features & Use Cases

  • Defines a canonical project layout (App, AppKit, Libraries, Features, Shared, Derived, Tuist) and consistent naming.
  • Helps new contributors learn the codebase quickly and accelerates feature onboarding.
  • Use case: reorganizing an existing project to align with the recommended structure or bootstrapping a new feature module following the guidelines.

Quick Start

Apply the recommended directory structure when creating new features or reorganizing the codebase.

Frequently Asked Questions about project-structure

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

FAQPage Schema
What is the best way to organize a large iOS codebase for scalable development?▼

A canonical iOS project structure standardizes directory layout using App, AppKit, Libraries, Features, Shared, and Derived sections. This defines consistent folder names and architecture guidelines to enable policy-driven project setup and scalable module wiring.

How do I structure a new iOS feature module following architecture guidelines?▼

Structure a new iOS feature module by placing it within the Features directory section and wiring it through the Shared components. Bootstrap new features following the codified directory patterns to maintain consistent architecture guidelines across the codebase.

When do I need to refactor an existing iOS project directory layout?▼

Refactor an existing iOS project directory layout when onboarding new contributors or accelerating feature development. Reorganizing the codebase to align with canonical folder names like App, AppKit, and Libraries helps teams learn the structure quickly and standardizes module wiring.

Does this iOS directory layout support projects using Tuist for project generation?▼

Yes, the canonical iOS directory layout includes a dedicated Tuist section. This supports policy-driven project setup and integrates codified patterns for projects using Tuist to generate and maintain their Xcode project files.

What are the limitations of standardizing an iOS project structure with codified patterns?▼

The limitation of standardizing an iOS project structure with codified patterns is the requirement to strictly apply canonical folder names across App, AppKit, Libraries, Features, Shared, and Derived sections. Existing projects require significant refactoring to align with these architecture guidelines.

Related Skills

Explore More Software Engineering Skills→
vitalliumvitallium
10

ce-test-xcode

Build, install, launch, and validate iOS app UI flows on the simulator.

Community
Advanced
hammadurrehman2006hammadurrehman2006

codebase-discovery-expert

Map large codebases and produce compact Markdown summaries of modules and entry points.

Community
Advanced
pelithpelith

react-architect-skills

Enforce scalable React module architecture with folder-based feature, container, hook, and domain layers.

Official
Intermediate
harshav167harshav167

swift-architecture

Select architecture patterns for SwiftUI and UIKit apps.

Community
Advanced