In what order should features be implemented using this skill?

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

Can this skill help with code reviews?

Yes, it is designed to review PRs for compliance against TEG's non-negotiable architectural rules and dependency matrices.

What is the core principle of the TEG Mobile Architecture skill?

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

Where can I find the specific folder layout rules?

The skill references a dedicated 'structure.md' file that defines folder layouts, module boundaries, and file placement requirements.

Which mobile platforms does this skill support?

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

TEG Mobile Architecture Standards

Name: TEG Mobile Architecture Standards
Author: bitsydarel

bybitsydarel

0•

Mobile Development

Enforces Transport Exchange Group mobile architecture standards and one-way dependency patterns across Flutter, iOS, and Android projects.

This skill provides a comprehensive framework for implementing the Transport Exchange Group (TEG) mobile architecture standards within Claude Code. It ensures developers adhere to a strict one-way dependency flow—moving from UI and State through Use Cases and Repositories down to Data Source contracts. By leveraging this skill, teams can maintain high code quality and consistency across various platforms, utilizing domain-specific guidance for folder structures, module boundaries, and implementation patterns tailored for Flutter, Swift, and Kotlin.

Características Principales

01Strict enforcement of one-way dependency architectural rules

02Standardized project folder and module boundary organization

03Platform-specific implementation patterns for Flutter, iOS, and Android

04Step-by-step guidance for building features from Business Types to UI

05Automated architectural policy validation for pull request reviews

060 GitHub stars

Casos de Uso

01Onboarding developers to the TEG mobile development standards and folder structures

02Scaffolding new mobile features with compliant architectural layers

03Reviewing existing codebases for architectural consistency and policy compliance

Características Principales

01Strict enforcement of one-way dependency architectural rules

02Standardized project folder and module boundary organization

03Platform-specific implementation patterns for Flutter, iOS, and Android

04Step-by-step guidance for building features from Business Types to UI

05Automated architectural policy validation for pull request reviews

060 GitHub stars

Casos de Uso

01Onboarding developers to the TEG mobile development standards and folder structures

02Scaffolding new mobile features with compliant architectural layers

03Reviewing existing codebases for architectural consistency and policy compliance