How does this skill assist with code reviews?

It uses the defined policies and dependency matrices to identify architectural violations and ensure PRs comply with TEG's non-negotiable standards.

What is the recommended implementation order for new features?

Features should be implemented in this order: Business Types, Use Cases, Repositories, Data Sources, and finally UI & State.

What is the core principle of TEG Mobile Architecture?

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

Which mobile platforms does this skill support?

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

Can this skill help with project organization?

Yes, it includes detailed references for folder layouts, module boundaries, and file placement to ensure a consistent project structure.

TEG Mobile Architecture

Name: TEG Mobile Architecture
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 building and maintaining mobile applications according to the TEG architecture standards. It ensures strict one-way dependency flow from UI to Data Sources, guides project folder structuring, and provides platform-specific implementation patterns for Dart, Swift, and Kotlin. By using this skill, developers can maintain high consistency across diverse mobile platforms, streamline the creation of new features, and automate architectural compliance checks during pull request reviews.

Características Principales

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

02Enforces strict one-way dependency flow across all architectural layers

030 GitHub stars

04Guides the implementation order from Business Types to UI and State

05Standardizes project folder structures and module boundaries

06Automates architectural policy checks during development and PR reviews

Casos de Uso

01Reviewing code contributions for adherence to TEG architectural guidelines

02Designing and implementing new mobile features from the ground up

03Refactoring existing mobile codebases into a standardized, layered structure

Características Principales

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

02Enforces strict one-way dependency flow across all architectural layers

030 GitHub stars

04Guides the implementation order from Business Types to UI and State

05Standardizes project folder structures and module boundaries

06Automates architectural policy checks during development and PR reviews

Casos de Uso

01Reviewing code contributions for adherence to TEG architectural guidelines

02Designing and implementing new mobile features from the ground up

03Refactoring existing mobile codebases into a standardized, layered structure