Skip to content
Conduit

skill

mobile-design

RamazanGasratov/mobile-designcommunitylistedunreviewed

Set up

Skills are installed by placing their folder where your agent loads skills.

The download comes from github.com/RamazanGasratov/mobile-design itself, not from our server, so what you get is exactly what its author published.

Install instructions come from the README

Skills do not use an MCP config. Follow the steps in the README below.

README

synced Oct 26, 2026

Mobile Design

A Codex skill for designing, implementing, and reviewing distinctive platform-native mobile interfaces for Apple and Android platforms.

mobile-design helps an AI agent avoid two common failures: copying one platform's conventions onto another and producing generic layouts made from interchangeable cards, gradients, pills, and floating controls. It starts from the product's real content and task, then applies the appropriate platform guidance.

What it covers

AreaApple platformsAndroid
Design languageApple HIG principles and Liquid GlassMaterial 3 and Material 3 Expressive
NavigationiOS and iPadOS navigation and presentationAndroid navigation, predictive back, and system bars
LayoutSafe areas, size classes, and iPad windowsAdaptive windows, tablets, foldables, and multi-pane layouts
InteractionDirect manipulation and interruptible physical motionMaterial motion, gesture feedback, and reduced motion
AccessibilityDynamic Type and Apple accessibility settingsTalkBack, scalable content, keyboard focus, and 48dp targets
ImplementationSwiftUI, UIKit, and Apple-inspired web prototypesJetpack Compose and Compose Material 3 Adaptive

Shared guidance keeps the result specific to the product rather than a reusable “AI app” template. Apple and Android rules stay in separate references so their behaviors and visual systems are not mixed.

Design position

  • Platform conventions define behavior; the product defines character.
  • Content and hierarchy come before materials, effects, and decoration.
  • Liquid Glass belongs mainly to Apple navigation and control layers, not every content container.
  • Material 3 Expressive uses color, shape, size, motion, typography, and containment with purpose; expressive does not automatically mean loud.
  • Native components are the starting point, not a limit on product identity.
  • Accessibility, adaptivity, complete states, and reduced-motion behavior are part of the design.

Install

Clone the repository into the Codex skills directory:

git clone https://github.com/RamazanGasratov/mobile-design.git ~/.codex/skills/mobile-design

Restart or reload Codex if the skill does not appear immediately.

Invoke it explicitly:

$mobile-design Design or review this mobile interface for its target platform.

Codex can also select the skill automatically when a request clearly concerns iOS, iPadOS, Android, Liquid Glass, Material 3 Expressive, SwiftUI, UIKit, Jetpack Compose, mobile navigation, accessibility, or adaptive layout.

Update

Pull the newest version from GitHub:

cd ~/.codex/skills/mobile-design
git pull

Repository structure

mobile-design/
├── SKILL.md
├── agents/
│   └── openai.yaml
└── references/
    ├── anti-template.md
    ├── apple-implementation.md
    ├── apple-platform.md
    ├── liquid-glass.md
    ├── motion.md
    └── android/
        ├── accessibility.md
        ├── adaptive-layout.md
        ├── components.md
        ├── compose-implementation.md
        ├── foundations.md
        ├── material3-expressive.md
        ├── motion.md
        └── navigation.md

SKILL.md contains the shared workflow and routes the agent only to references relevant to the current platform and task. This keeps the active context focused instead of loading one long design manual.

Sources

The guidance is structured from maintained public platform documentation, including:

Individual reference files link to the specific documentation and sessions used for their recommendations.

Contributing

Contributions are welcome. Keep additions focused and actionable:

  • cite the current official platform source;
  • keep Apple- and Android-specific guidance separate;
  • summarize recommendations instead of copying entire documentation pages;
  • explain how a recommendation changes a design or implementation decision;
  • avoid universal rules based on one app, visual trend, or isolated failure.

Independence

This is an independent project and is not affiliated with or endorsed by Apple Inc. or Google LLC.

Apple, iOS, iPadOS, SwiftUI, and Liquid Glass are trademarks or terms associated with Apple Inc. Android, Jetpack Compose, Material Design, and Material 3 are trademarks or terms associated with Google LLC.

License

Released under the MIT License. See LICENSE.

↑↓ navigate openesc close