What is the core principle of TEG Mobile Architecture?

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

Which mobile platforms does this skill support?

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

How does this skill help with code reviews?

The skill can be used to review PRs for compliance against TEG's non-negotiable rules, dependency matrices, and strict layer boundaries.

What is the recommended implementation order for new features?

The recommended order is: Business Types, Use Cases, Repositories, Data Sources, and finally UI & State.

Does it provide guidance on folder organization?

Yes, it includes specific references for folder layout, module boundaries, and file placement to ensure project consistency.

TEG Mobile Architecture

Name: TEG Mobile Architecture
Author: bitsydarel

bybitsydarel

0•

Mobile Development

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

This skill acts as an automated architectural guide for mobile projects following the Transport Exchange Group (TEG) standards. It ensures strict adherence to a one-way dependency flow—moving from UI and State through Use Cases and Repositories to Data Source Contracts. Whether you are bootstrapping a new feature, organizing project folder structures, or performing code reviews, this skill provides platform-specific guidance for Flutter, Swift, and Kotlin to maintain high-quality, scalable, and maintainable mobile codebases.

主な機能

010 GitHub stars

02Provides standardized project structure and folder layout guidance for consistency.

03Automates architectural compliance checks during pull request reviews.

04Offers platform-specific implementation patterns for Flutter, Swift, and Kotlin.

05Enforces strict one-way dependency flow across all mobile architectural layers.

06Guides step-by-step implementation of Business Types, Use Cases, and Repositories.

ユースケース

01Conducting automated architectural reviews to ensure layer boundary compliance in PRs.

02Designing and bootstrapping new mobile features according to TEG's architectural layers.

03Refactoring existing mobile codebases to align with standardized folder and module structures.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add bitsydarel/bdskills teg-mobile-architecture

For use in Claude.ai and ChatGPT

Download Skill