Which mobile platforms are supported by this skill?

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

Does this skill provide code templates?

Yes, it includes reference documentation for specific implementation patterns across Dart, Swift, and Kotlin to ensure code consistency.

How does this skill assist in Pull Request reviews?

The skill can be used to review PRs for compliance, ensuring that layer boundaries are respected and the project folder structure follows TEG standards.

What is the core principle of TEG Mobile Architecture?

The core principle is strict one-way dependencies where the flow moves from UI & State to Use Cases, then Repositories, and finally Data Source Contracts.

What is the recommended implementation order for new features?

The skill recommends building in this order: Business Types, Use Cases, Repositories, Data Sources, and finally UI & State.

TEG Mobile Architecture

Name: TEG Mobile Architecture
Author: bitsydarel

bybitsydarel

0•

Mobile Development

Enforces standardized Clean Architecture patterns and folder structures for mobile projects across Flutter, iOS, and Android.

This skill serves as an architectural guardian for mobile development teams following the Transport Exchange Group (TEG) standards. It automates the enforcement of one-way dependency rules, ensuring that UI layers communicate only with Use Cases, which in turn interface with Repositories and Data Sources. By providing specific guidance for Flutter, iOS, and Android, it helps developers build scalable, maintainable mobile applications while maintaining consistency in folder layout and implementation patterns across diverse platforms. It is particularly useful during the initial design phase of a feature and as an automated reviewer during the PR process.

Características Principales

01Standardizes project folder structures and module boundaries

02Assists in PR reviews to ensure compliance with TEG architectural policies

03Enforces strict one-way dependency flow between architectural layers

04Provides platform-specific implementation patterns for Dart, Swift, and Kotlin

050 GitHub stars

06Guides the sequential implementation of Business Types, Use Cases, and UI

Casos de Uso

01Designing a new feature with standardized Clean Architecture layers

02Onboarding developers to the TEG-specific mobile project structure

03Automating architectural compliance checks during code reviews

Características Principales

01Standardizes project folder structures and module boundaries

02Assists in PR reviews to ensure compliance with TEG architectural policies

03Enforces strict one-way dependency flow between architectural layers

04Provides platform-specific implementation patterns for Dart, Swift, and Kotlin

050 GitHub stars

06Guides the sequential implementation of Business Types, Use Cases, and UI

Casos de Uso

01Designing a new feature with standardized Clean Architecture layers

02Onboarding developers to the TEG-specific mobile project structure

03Automating architectural compliance checks during code reviews