What is the core principle of the TEG Mobile Architecture?

The core principle is One-Way Dependencies, where data flows strictly from UI & State to Use Cases, then Repositories, and finally Data Source Contracts.

In what order should features be implemented using this skill?

The recommended order is: 1. Business Types, 2. Use Cases, 3. Repositories, 4. Data Sources, and 5. UI & State.

Which mobile platforms are supported by this skill?

This skill provides specific implementation patterns and rules for Flutter (Dart), iOS (Swift), and Android (Kotlin).

How does this skill assist in code reviews?

It provides a reference for non-negotiable architectural rules and dependency matrices to ensure PRs comply with TEG's mobile standards.

TEG Mobile Architecture Standards

Name: TEG Mobile Architecture Standards
Author: bitsydarel

bybitsydarel

0•

Mobile Development

Enforces Transport Exchange Group's architectural standards for cross-platform and native mobile development projects.

The TEG Mobile Architecture skill ensures that mobile applications adhere to a strict architectural blueprint centered on one-way dependencies. By guiding developers through the implementation of specific layers—Business Types, Use Cases, Repositories, Data Sources, and UI—it maintains consistency across Flutter, iOS, and Android platforms. This skill is essential for structuring project folders correctly, implementing domain-specific logic, and conducting rigorous pull request reviews to ensure long-term maintainability and architectural integrity.

주요 기능

01Layered implementation sequencing for new feature development

02Platform-specific implementation patterns for Flutter, Swift, and Kotlin

03Enforcement of strict one-way dependency flow (UI to Data Source)

04Architectural compliance auditing for code reviews and PRs

05Standardized project folder and module layout guidance

060 GitHub stars

사용 사례

01Designing and bootstrapping new mobile features using the TEG blueprint

02Restructuring existing project folders to align with standardized modules

03Performing architectural reviews on PRs to ensure layer boundary compliance

주요 기능

01Layered implementation sequencing for new feature development

02Platform-specific implementation patterns for Flutter, Swift, and Kotlin

03Enforcement of strict one-way dependency flow (UI to Data Source)

04Architectural compliance auditing for code reviews and PRs

05Standardized project folder and module layout guidance

060 GitHub stars

사용 사례

01Designing and bootstrapping new mobile features using the TEG blueprint

02Restructuring existing project folders to align with standardized modules

03Performing architectural reviews on PRs to ensure layer boundary compliance