Bexa Mobile logo

Bexa Mobile

Community
BekhruzTursunboev
bexa-mobile

Premium mobile UI skill for React Native and Expo apps. Enforces native-grade interaction patterns, platform-specific motion, gesture physics, and non-generic visual systems for iOS and Android.

Overview

PublisherBekhruzTursunboev
RepositoryBexa-professional-frontend-design-skills-for-ai-agents
Skill namebexa-mobile
Stars
9
Forks
2
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by BekhruzTursunboev on GitHub. Read the source before you install it.

Installation

Install the Bexa Mobile AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/BekhruzTursunboev/Bexa-professional-frontend-design-skills-for-ai-agents/tree/main/skills/bexa-mobile
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/BekhruzTursunboev/Bexa-professional-frontend-design-skills-for-ai-agents.git /tmp/Bexa-professional-frontend-design-skills-for-ai-agents
mkdir -p .claude/skills
cp -r /tmp/Bexa-professional-frontend-design-skills-for-ai-agents/skills/bexa-mobile .claude/skills/bexa-mobile
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Bexa Mobile in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Bexa Mobile on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Bexa Mobile is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

FORGE MOBILE — Native-Grade Mobile Design Skill

Designing for a human holding glass with their thumbs. Every decision — padding, font, tap target, animation — must honor that physical reality.


DIAL CONFIGURATION

NATIVE_FIDELITY:  8   (1=Web-wrapper / 10=Indistinguishable from OS)
GESTURE_DEPTH:    7   (1=Tap only / 10=Physics swipe, pinch, long-press)
VISUAL_RICHNESS:  6   (1=Minimal / 10=Rich depth layers)

SECTION 1 — MOBILE-FIRST CONSTRAINTS

Thumb Zone: Primary actions in bottom 40% of screen. Destructive actions top. NO hamburger menus.

Touch Targets:

  • Minimum: 44×44pt (iOS) / 48×48dp (Android)
  • Visual can be smaller; hitbox must be padded to minimum
  • Min 8pt gap between adjacent targets

Safe Areas: Always use SafeAreaView. Bottom: 34pt for home indicator. Never place critical content in top 59pt (Dynamic Island zone).


SECTION 2 — TYPOGRAPHY MOBILE SCALE

LevelSize (pt/sp)Weight
Display34700
Title 128700
Title 222600
Headline17600
Body17400
Footnote13400
Caption12400

Font selection: Sora + DM Sans for iOS feel. Plus Jakarta Sans + Geist for Android feel. Never system defaults only.


SECTION 3 — GESTURE PHYSICS

When GESTURE_DEPTH >= 5: use react-native-reanimated + react-native-gesture-handler. Never PanResponder.

Spring configuration:

js
// Premium iOS-like spring
const spring = { damping: 15, stiffness: 150, mass: 0.8 };
// Snappy confirmation
const snap   = { damping: 20, stiffness: 300, mass: 0.5 };

Haptics: Every state change triggers haptic feedback.

  • Button press → ImpactFeedbackStyle.Light
  • Success → NotificationFeedbackType.Success
  • Error → NotificationFeedbackType.Error
  • Drag threshold → ImpactFeedbackStyle.Medium

SECTION 4 — PLATFORM MOTION

iOS: Sheets slide up from bottom with spring. Navigation push slides at 85% finger speed. Action completion scales to 0.95 → overshoot release.

Android: Material You ripple on all pressables. BottomSheetModal with snapPoints ['40%','70%','95%']. Shared element transitions on list→detail.

Universal:

  • Loading: shimmer skeleton matching exact content layout
  • Pull-to-refresh: liquid droplet — NOT a spinner
  • Scroll: honor platform physics, never hard-stop

SECTION 5 — COLOR SYSTEM (MOBILE)

Light — Surface: hsl(220 14% 98%) | Card: hsl(0 0% 100%)
Dark  — Surface: hsl(220 20%  8%) | Card: hsl(220 20% 12%)
OLED  — Background: hsl(0 0% 0%) | Cards remain hsl(220 20% 8%)

Accent: same rules as FORGE core (1 accent, sat ≤ 75%, no AI purple).


SECTION 6 — PERFORMANCE MANDATES

  • Images: expo-image or FastImage. Never plain <Image> in lists.
  • Lists: FlashList with estimatedItemSize. FlatList only for < 50 items.
  • Animations: useSharedValue + useAnimatedStyle (Reanimated 3). JS thread animations = BANNED.
  • Re-renders: React.memo all list items. useCallback all handlers passed as props.
  • Network: Cache responses. Show stale data + refresh indicator, never blank screen.

Frequently asked questions

What does the Bexa Mobile AI skill do?

Premium mobile UI skill for React Native and Expo apps. Enforces native-grade interaction patterns, platform-specific motion, gesture physics, and non-generic visual systems for iOS and Android.

Why use Bexa Mobile on TypingMind?

Because you install it once and use it with any model. Bexa Mobile is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Bexa Mobile in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/BekhruzTursunboev/Bexa-professional-frontend-design-skills-for-ai-agents/tree/main/skills/bexa-mobile. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Bexa Mobile?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Bexa Mobile?

As many as you like. As long as a model supports skills, you can use Bexa Mobile with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Bexa Mobile AI skill free?

Yes. It is published on GitHub by BekhruzTursunboev under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇