senior-mobile

borghei/claude-skills · updated Apr 10, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/borghei/claude-skills --skill senior-mobile
0 commentsdiscussion
summary

Expert mobile application development across iOS, Android, React Native, and Flutter.

skill.md

Senior Mobile Developer

Expert mobile application development across iOS, Android, React Native, and Flutter.

Keywords

mobile, ios, android, react-native, flutter, swift, kotlin, swiftui, jetpack-compose, expo-router, zustand, app-store, performance, offline-first


Quick Start

# Scaffold a React Native project
python scripts/mobile_scaffold.py --platform react-native --name MyApp

# Build for production
python scripts/build.py --platform ios --env production

# Generate App Store metadata
python scripts/store_metadata.py --screenshots ./screenshots

# Profile rendering performance
python scripts/profile.py --platform android --output report.html

Tools

Script Purpose
scripts/mobile_scaffold.py Scaffold project for react-native, ios, android, or flutter
scripts/build.py Build automation with environment and platform flags
scripts/store_metadata.py Generate App Store / Play Store listing metadata
scripts/profile.py Profile rendering, memory, and startup performance

Platform Decision Matrix

Aspect Native iOS Native Android React Native Flutter
Language Swift Kotlin TypeScript Dart
UI Framework SwiftUI/UIKit Compose/XML React Widgets
Performance Best Best Good Very Good
Code Sharing None None ~80% ~95%
Best For iOS-only, hardware-heavy Android-only, hardware-heavy Web team, shared logic Maximum code sharing

Workflow 1: Scaffold a React Native App (Expo Router)

  1. Generate project -- python scripts/mobile_scaffold.py --platform react-native --name MyApp
  2. Verify directory structure matches this layout:
    src/
    ├── app/              # Expo Router file-based routes
    │   ├── (tabs)/       # Tab navigation group
    │   ├── auth/         # Auth screens
    │   └── _layout.tsx   # Root layout
    ├── components/
    │   ├── ui/           # Reusable primitives (Button, Input, Card)
    │   └── features/     # Domain components (ProductCard, UserAvatar)
    ├── hooks/            # Custom hooks (useAuth, useApi)
    ├── services/         # API clients and storage
    ├── stores/           # Zustand state stores
    └── utils/            # Helpers
    
  3. Configure navigation in app/_layout.tsx with Stack and Tabs.
  4. Set up state management with Zustand + AsyncStorage persistence.
  5. Validate -- Run the app on both iOS simulator and Android emulator. Confirm navigation and state persistence work.

Workflow 2: Build a SwiftUI Feature (iOS)

  1. Create the View using NavigationStack, @StateObject for ViewModel binding, and .task for async data loading.
  2. Create the ViewModel as @MainActor class with @Published properties. Inject services via protocol for testability.
  3. Wire data flow: View observes ViewModel -> ViewModel calls Service -> Service returns data -> ViewModel updates @Published -> View re-renders.
  4. Add search/refresh: .searchable(text:) for filtering, .refreshable for pull-to-refresh.
  5. Validate -- Run in Xcode previews first, then simulator. Confirm async loading, error states, and empty states all render correctly.

Example: SwiftUI ViewModel Pattern

@MainActor
class ProductListViewModel: ObservableObject {
    @Published private(set) var products: [Product] = []
    @Published private(set) var isLoading = false
    @Published private(set) var error: Error?

    private let service: ProductServiceProtocol

    init(service: ProductServiceProtocol = ProductService()) {
        self.service = service
    }

    func loadProducts() async {
        isLoading = true
        error = nil
        do {
            products = try await service.fetchProducts()
        } catch {
            self.error = error
        }
        isLoading = false
    }
}

Workflow 3: Build a Jetpack Compose Feature (Android)

  1. Create the Composable screen with Scaffold, TopAppBar, and state collection via collectAsStateWithLifecycle().
  2. Handle UI states with a sealed interface: Loading, Success<T>, Error.
  3. Create the ViewModel with @HiltViewModel, MutableStateFlow, and repository injection.
  4. Build list UI using LazyColumn with key parameter for stable identity and Arrangement.spacedBy() for spacing.
  5. Validate -- Run on emulator. Confirm state transitions (loading -> success, loading -> error -> retry) work correctly.

Example: Compose UiState Pattern

sealed interface UiState<out T> {
    data object Loading : UiState<Nothing>
    data class Success<T>(val data: T) : UiState<T>
    data class Error(val message: String) : UiState<Nothing>
}

@HiltViewModel
class ProductListViewModel @Inject constructor(
    private val repository: ProductRepository
) : ViewModel() {
    private val _uiState = MutableStateFlow<UiState<List<Product>>>(UiState.Loading)
    val uiState: StateFlow<UiState<List<Product>>> = _uiState.asStateFlow()

    fun loadProducts() {
        viewModelScope.launch {
            _uiState.value = UiState.Loading
            repository.getProducts()
                .catch { e -> _uiState.value = UiState.Error(e.message ?: "Unknown error") }
                .collect { products -> _uiState.value = UiState.Success(products) }
        }
    }
}

Workflow 4: Optimize Mobile Performance

  1. Profile -- python scripts/profile.py --platform <ios|android> --output report.html
  2. Apply React Native optimizations:
    • Use FlatList with keyExtractor, initialNumToRender=10, windowSize=5, removeClippedSubviews=true
    • Memoize components with React.memo and handlers with useCallback
    • Supply getItemLayout for fixed-height rows to skip measurement
  3. Apply native iOS optimizations:
    • Implement prefetchItemsAt for image pre-loading in collection views
  4. Apply native Android optimizations:
    • Set setHasFixedSize(true) and setItemViewCacheSize(20) on RecyclerViews
  5. Validate -- Re-run profiler and confirm frame drops reduced and startup time improved.

Workflow 5: Submit to App Store / Play Store

  1. Generate metadata -- python scripts/store_metadata.py --screenshots ./screenshots
  2. Build release -- python scripts/build.py --platform ios --env production
  3. Review the generated listing (title, description, keywords, screenshots).
  4. Upload via Xcode (iOS) or Play Console (Android).
  5. Validate -- Monitor review status and address any rejection feedback.

Reference Materials

Document Path
React Native Guide references/react_native_guide.md
iOS Patterns references/ios_patterns.md
Android Patterns references/android_patterns.md
App Store Guide references/app_store_guide.md
Full Code Examples REFERENCE.md

Troubleshooting

Problem Cause Solution
App crashes on launch after adding a new dependency Incompatible native module version or missing pod install / gradle sync Run npx pod-install (iOS) or cd android && ./gradlew clean (Android). Verify dependency version compatibility in the changelog.
FlatList renders blank or flickers Missing keyExtractor, unstable keys, or inline renderItem causing full re-renders Add a stable keyExtractor, wrap renderItem in useCallback, and supply getItemLayout for fixed-height rows.
iOS build fails with "signing" error Provisioning profile mismatch or expired certificate Open Xcode > Signing & Capabilities, select the correct team and profile. Run security find-identity -v -p codesigning to verify certificates.
Android build OOM during dexing Insufficient JVM heap for large projects Add org.gradle.jvmargs=-Xmx4096m to gradle.properties. Enable dexOptions { javaMaxHeapSize "4g" } in build.gradle.
App Store rejection for missing privacy manifest Apple requires PrivacyInfo.xcprivacy for apps using required reason APIs (UserDefaults, file timestamp, etc.) Add a PrivacyInfo.xcprivacy file declaring each required reason API. Run store_metadata_generator.py to review privacy label guidance.
Slow cold start time (>3 seconds) Too many synchronous operations on the main thread at launch, large bundle size, or unoptimized images Defer non-critical initialization, lazy-load modules, compress images, and use app_performance_analyzer.py to identify bottlenecks.
Hot reload / fast refresh stops working Syntax error in a module boundary, anonymous default export, or class component state Check terminal for error messages, ensure named exports, and restart the Metro bundler or Flutter daemon with a cache clear.

Success Criteria

  • App startup time under 2 seconds on cold launch (measured on mid-range devices, both iOS and Android).
  • Crash-free rate above 99.5% across all supported OS versions, tracked via Crashlytics or Sentry.
  • Frame rendering at 60 fps (16ms per frame) for scrolling lists and animations, with zero jank frames during typical user flows.
  • Bundle size under 50 MB for the initial download (excluding on-demand resources), verified before each release.
  • Performance analyzer score of 75+ (Grade B or above) when running app_performance_analyzer.py against the project.
  • Zero critical issues and fewer than 5 warnings reported by the performance analyzer before submitting to app stores.
  • App Store / Play Store approval on first submission with complete metadata, correct privacy labels, and proper age rating, validated using store_metadata_generator.py.

Scope & Limitations

This skill covers:

  • Scaffolding production-ready mobile projects for React Native (Expo Router), Flutter, iOS native (SwiftUI), and Android native (Jetpack Compose).
  • Static performance analysis including image asset sizing, re-render detection, memory leak patterns, and bundle size estimation.
  • App Store and Play Store metadata generation including titles, keywords, privacy labels, age ratings, and submission checklists.
  • Platform-specific architecture patterns (MVVM, state management, navigation).

This skill does NOT cover:

  • Backend API development or server-side logic (see senio
how to use senior-mobile

How to use senior-mobile on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add senior-mobile
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/borghei/claude-skills --skill senior-mobile

The skills CLI fetches senior-mobile from GitHub repository borghei/claude-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/senior-mobile

Reload or restart Cursor to activate senior-mobile. Access the skill through slash commands (e.g., /senior-mobile) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.564 reviews
  • Ganesh Mohane· Dec 24, 2024

    Keeps context tight: senior-mobile is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Mateo Reddy· Dec 24, 2024

    senior-mobile is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Sakura Sanchez· Dec 20, 2024

    Registry listing for senior-mobile matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Shikha Mishra· Dec 4, 2024

    senior-mobile fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Fatima Jackson· Dec 4, 2024

    senior-mobile reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Olivia Yang· Nov 23, 2024

    I recommend senior-mobile for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Sakshi Patil· Nov 15, 2024

    senior-mobile has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Michael Shah· Nov 15, 2024

    Solid pick for teams standardizing on skills: senior-mobile is focused, and the summary matches what you get after install.

  • Fatima White· Nov 11, 2024

    senior-mobile fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Mateo Patel· Nov 11, 2024

    We added senior-mobile from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

showing 1-10 of 64

1 / 7