mobile-architecture-rules

Evaluate iOS architecture patterns against live repo conventions and archetypes.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/hoshiyar-singh8/SprintPlanner --skill mobile-architecture-rules
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mobile-architecture-rules
Source: https://github.com/hoshiyar-singh8/SprintPlanner/tree/main/skills/mobile-architecture-rules
Command: npx skills add https://github.com/hoshiyar-singh8/SprintPlanner --skill mobile-architecture-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps engineers assess B2C iOS architectural archetypes against live repo conventions and avoid assuming a single module shape.

Core Features & Use Cases

  • Archetype detection: identify patterns such as classic_viper_feature, graphql_feed_feature, modular_sdk_package, and provider_or_bridge_component, and map them to repo structure.
  • DI and data layer guidance: explain dependency injection practices, API clients, and GraphQL usage in typical B2C features.
  • Testing and UI conventions: outline recommended testing targets and layout patterns to ensure consistency across modules.

Quick Start

Classify a feature's architecture against the defined archetypes and report alignment with live repo conventions.

Frequently Asked Questions about mobile-architecture-rules

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

FAQPage Schema
How do I classify an iOS feature's architecture against repo conventions?

To classify iOS architecture, evaluate the feature against defined archetypes like classic_viper_feature, graphql_feed_feature, modular_sdk_package, and provider_or_bridge_component, mapping the module shape directly to your live repo structure.

What are the common iOS architectural archetypes in a B2C app?

Common B2C iOS archetypes include classic_viper_feature, graphql_feed_feature, modular_sdk_package, and provider_or_bridge_component. Identifying these patterns helps avoid assuming a single module shape across different features.

How should dependency injection be applied in VIPER iOS modules?

Dependency injection in VIPER modules should align with live repo conventions, properly providing API clients and GraphQL usage to ensure data and UI layering consistency across typical B2C features.

What testing conventions should I follow for modular iOS SDK packages?

Testing conventions for modular iOS SDK packages involve outlining recommended testing targets and layout patterns that ensure consistency across modules, verifying alignment with provider_or_bridge_component archetypes.

Can I use GraphQL feed features with a classic VIPER architecture?

Yes, you can map GraphQL feed features to a classic VIPER architecture by evaluating the data and UI layering against repo conventions, ensuring the module aligns with the graphql_feed_feature archetype.

Why does my iOS architecture review assume a single module shape?

Architecture reviews often incorrectly assume a single module shape because they fail to detect distinct patterns like modular_sdk_package or provider_or_bridge_component, leading to misalignment with live repo conventions.