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.

Can this skill help with existing codebases?

Yes, it can be used to review existing projects for architectural compliance and to help refactor folder structures to meet TEG standards.

What is the core architectural principle of this skill?

It enforces a strict one-way dependency flow where the UI and State depend on Use Cases, which depend on Repositories, which finally depend on Data Source Contracts.

What platforms does this skill support?

The TEG Mobile Architecture skill supports Flutter (Dart), iOS (Swift), and Android (Kotlin) development environments.

TEG Mobile Architecture Standards

Name: TEG Mobile Architecture Standards
Author: bitsydarel

bybitsydarel

0•

Mobile Development

Enforces Transport Exchange Group (TEG) architectural standards and one-way dependency patterns for Flutter, iOS, and Android development.

This skill provides a comprehensive framework for designing and auditing mobile applications according to TEG’s strict one-way dependency model. It guides developers through the implementation of layered architectures—spanning Business Types, Use Cases, Repositories, Data Sources, and UI—to ensure consistency across project structures and platform-specific syntax. By using this skill, teams can automate architectural compliance during PR reviews and ensure that new features follow a standardized implementation sequence across Flutter, Swift, and Kotlin environments.

Características Principales

01Enforces strict one-way dependency flow between architectural layers

02Guides the sequential implementation of Business Types, Use Cases, and Data Sources

030 GitHub stars

04Provides platform-specific implementation patterns for Flutter, iOS, and Android

05Standardizes project folder layouts and module boundaries

06Automates architectural compliance checks during pull request reviews

Casos de Uso

01Conducting automated code reviews to ensure compliance with TEG mobile policies

02Designing and bootstrapping new mobile features using standardized architectural layers

03Restructuring existing mobile projects to align with standardized folder conventions

Características Principales

01Enforces strict one-way dependency flow between architectural layers

02Guides the sequential implementation of Business Types, Use Cases, and Data Sources

030 GitHub stars

04Provides platform-specific implementation patterns for Flutter, iOS, and Android

05Standardizes project folder layouts and module boundaries

06Automates architectural compliance checks during pull request reviews

Casos de Uso

01Conducting automated code reviews to ensure compliance with TEG mobile policies

02Designing and bootstrapping new mobile features using standardized architectural layers

03Restructuring existing mobile projects to align with standardized folder conventions