teg-mobile-architecture

Enforce one-way dependency flow from UI & State to Data Sources.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/bitsydarel/BDSkills --skill teg-mobile-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: teg-mobile-architecture
Source: https://github.com/bitsydarel/BDSkills/tree/main/plugins/teg-mobile-architecture/skills/teg-mobile-architecture
Command: npx skills add https://github.com/bitsydarel/BDSkills --skill teg-mobile-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill ensures that mobile applications adhere to the Transport Exchange Group (TEG) architectural standards, promoting consistency, maintainability, and scalability across projects.

Core Features & Use Cases

  • One-Way Dependency Enforcement: Guarantees that dependencies flow strictly from UI & State down to Data Sources.
  • Layered Architecture Guidance: Provides clear guidelines for organizing code into distinct layers (UI, Use Cases, Repositories, Data Sources).
  • Platform-Specific Patterns: Offers code examples and best practices for Android (Kotlin), iOS (Swift), and Flutter (Dart).
  • Use Case: When developing a new feature, developers can consult this skill to understand the correct order of implementation and the expected structure for each layer, preventing architectural drift.

Quick Start

Follow the specified order of implementation for building a new feature, starting with Business Types and ending with UI & State.

Frequently Asked Questions about teg-mobile-architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce one-way dependency flow in mobile architecture?

A layered mobile architecture organizes code into distinct UI, Use Cases, Repositories, and Data Sources layers to promote consistency and maintainability. This skill defines these specific layers and provides a strict one-way dependency flow from UI down to Data Sources.

What is the best way to structure a new feature using clean architecture in Flutter?

Yes, clean architecture standards apply across Android, iOS, and Flutter by providing platform-specific implementation patterns for Kotlin, Swift, and Dart. This skill enforces these standards by defining a strict dependency matrix and layer responsibilities for each mobile platform.

How do I organize code into distinct layers for Android and iOS development?

To start implementing a new feature, begin with Business Types and proceed sequentially through Data Sources, Repositories, Use Cases, and finally UI & State. This skill outlines this specific implementation order to prevent architectural drift and maintain strict one-way dependencies.

When do I need a dependency matrix for mobile project structure?

A dependency matrix for mobile project structure is needed when enforcing strict one-way dependency flow from UI & State down to Data Sources across multiple platforms. This skill provides that matrix to guarantee adherence to layer responsibilities and prevent architectural drift.