Which mobile platforms does this skill support?

The skill includes specific implementation patterns and syntax for Flutter (Dart), iOS (Swift), and Android (Kotlin).

Does this skill provide guidance on folder structure?

Yes, it includes reference documentation for project folder layouts, module boundaries, and specific file placement for mobile projects.

What is the core principle of the TEG mobile architecture?

The core principle is one-way dependencies, where logic flows strictly from UI and State to Use Cases, then Repositories, and finally Data Source Contracts.

In what order should features be implemented using this skill?

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

Can this skill be used to audit existing code?

Yes, it can be used to compare existing code against TEG's architectural rules and policies to identify dependency violations or structural inconsistencies.

TEG Mobile Architecture Standards

Name: TEG Mobile Architecture Standards
Author: bitsydarel

bybitsydarel

0•

Mobile Development

Enforces Transport Exchange Group (TEG) architectural standards for mobile applications to ensure clean, maintainable, and scalable code.

This skill provides Claude with the specific architectural principles and implementation patterns required by the Transport Exchange Group (TEG). It enforces a strict one-way dependency flow—from UI and State down to Data Source Contracts—ensuring a robust separation of concerns. By guiding developers through a specific implementation order (from Business Types to UI), the skill streamlines feature development across Flutter, iOS, and Android platforms while providing direct access to non-negotiable architectural policies and folder structure guidelines.

Key Features

01Enforces strict one-way dependency flow (UI to Data Source Contracts)

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

03Standardizes project folder layouts and module boundaries

04Guides developers through a specific 5-step feature implementation workflow

05Integrates non-negotiable architectural policies and dependency matrices

060 GitHub stars

Use Cases

01Building a new mobile feature from scratch using TEG-compliant layered architecture

02Refactoring existing mobile code to align with standardized dependency rules

03Ensuring consistency across multi-platform teams using Flutter, Swift, or Kotlin

Key Features

01Enforces strict one-way dependency flow (UI to Data Source Contracts)

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

03Standardizes project folder layouts and module boundaries

04Guides developers through a specific 5-step feature implementation workflow

05Integrates non-negotiable architectural policies and dependency matrices

060 GitHub stars

Use Cases

01Building a new mobile feature from scratch using TEG-compliant layered architecture

02Refactoring existing mobile code to align with standardized dependency rules

03Ensuring consistency across multi-platform teams using Flutter, Swift, or Kotlin