How does this skill help during code reviews?

It provides a reference for non-negotiable architectural rules and dependency matrices to ensure Pull Requests comply with TEG standards.

In what order should I implement features using this skill?

Implementation follows a specific five-step sequence: Business Types, Use Cases, Repositories, Data Sources, and finally UI & State.

What platforms does this skill support?

It supports Flutter (Dart), native iOS (Swift), and native Android (Kotlin) development using TEG-specific standards.

What is the core principle of the TEG architecture?

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

TEG Mobile Architecture Standards

Name: TEG Mobile Architecture Standards
Author: bitsydarel

bybitsydarel

0•

Mobile Development

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

This skill provides a comprehensive framework for building mobile applications according to TEG's specific architectural guidelines, ensuring strict one-way dependency flow from UI and State through Use Cases and Repositories down to Data Source contracts. It is essential for developers designing new features, organizing project folder structures, or performing code reviews to ensure consistency and maintainability across diverse mobile platforms including Flutter, native iOS, and native Android. By providing platform-specific implementation patterns and non-negotiable architectural rules, it streamlines the development lifecycle and reduces technical debt.

Características Principales

01Standardizes project folder layouts and module organization

020 GitHub stars

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

04Enforces strict one-way dependency flow and layer boundaries

05Guides the sequential implementation of architectural layers from Business Types to UI

06Assists in PR reviews for architectural compliance and code quality

Casos de Uso

01Reviewing pull requests to ensure strict separation of concerns and adherence to TEG policies

02Refactoring existing mobile codebases to align with standardized dependency patterns

03Bootstrapping a new mobile feature following TEG architectural layers

Características Principales

01Standardizes project folder layouts and module organization

020 GitHub stars

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

04Enforces strict one-way dependency flow and layer boundaries

05Guides the sequential implementation of architectural layers from Business Types to UI

06Assists in PR reviews for architectural compliance and code quality

Casos de Uso

01Reviewing pull requests to ensure strict separation of concerns and adherence to TEG policies

02Refactoring existing mobile codebases to align with standardized dependency patterns

03Bootstrapping a new mobile feature following TEG architectural layers