Agent skill

Accessible Mobile Developer

by FerroxLabs in FerroxLabs/wayland

Mobile accessibility development expertise covering iOS VoiceOver and Android TalkBack integration, accessibility APIs for SwiftUI and Jetpack Compose, touch target sizing, gesture alternatives…

Apache-2.0Auto-check passedMobile

Install Accessible Mobile Developer

skills CLI
$ npx skills add FerroxLabs/wayland --skill accessible-mobile-developer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install FerroxLabs/wayland accessible-mobile-developer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/web-development/accessible-mobile-developer .claude/skills/accessible-mobile-developer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
accessible-mobile-developer
GitHub stars
608
Token cost
~3.6k tokens
SKILL.md length
537 words
Files
1
Skills in repo
1,194
Repo updated
First seen
Licence
Apache-2.0

At a glance

Mobile accessibility development expertise covering iOS VoiceOver and Android TalkBack integration, accessibility APIs for SwiftUI and Jetpack Compose, touch target sizing, gesture alternatives…

  • Works in 6 steps: Platform: iOS, Android, or… → Framework: SwiftUI/UIKit, Jetpack… → Current state: Building new or… → …
  • The user asks about accessible mobile developer
  • SKILL.md covers When to Use, Questions to Ask the User First, iOS Accessibility (SwiftUI) and Android Accessibility (Jetpack…, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Accessible Mobile Developer is an agent skill from FerroxLabs/wayland. Mobile accessibility development expertise covering iOS VoiceOver and Android TalkBack integration, accessibility APIs for SwiftUI and Jetpack Compose, touch target sizing, gesture alternatives, dynamic type support, color contrast compliance, screen reader testing, and WCAG mobile-specific success criteria. Use when the user asks about accessible mobile developer, related techniques, best practices, or needs guidance in this domain. Do NOT use when the request is outside the scope of accessible mobile developer…

Its SKILL.md is about 3.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Mobile, covering Accessibility, iOS development and Android development. It works with Android, iOS, Jetpack Compose and SwiftUI. The repository describes itself as: Wayland - The AI Agent That Perceives. Reasons. Acts. Evolves. The licence is Apache-2.0.

When your agent uses it

  • The user asks about accessible mobile developer
  • Related techniques
  • Needs guidance in this domain
  • The request is outside the scope of accessible mobile developer

Example prompts

  • “/accessible-mobile-developer”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Platform: iOS, Android, or cross-platform (React Native, Flutter)?
  2. Framework: SwiftUI/UIKit, Jetpack Compose/XML Views, or cross-platform framework?
  3. Current state: Building new or remediating existing app?
  4. Target compliance: WCAG 2.1 AA, Section 508, EN 301 549, or app store guidelines?
  5. Key user flows: Which screens/flows are highest priority for accessibility?
  6. Testing capability: Do you have access to assistive technology users for testing?

What it can do on your machine

Read from SKILL.md and the folder at commit 4c030c7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are swift, kotlin, javascript, dart and template).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Accessible Mobile Developer loads about 3.6k tokens when it runs. Until then it costs about 147 tokens; SKILL.md has 537 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~147
When it runs · the whole SKILL.md, loaded when a task matches
~3.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from FerroxLabs/wayland at commit 4c030c7, republished under its Apache-2.0 licence (© FerroxLabs). 537 words, ~3,588 tokens.

Download SKILL.mdSave it as .claude/skills/accessible-mobile-developer/SKILL.md (or your agent's skills folder).
name
accessible-mobile-developer
description
Mobile accessibility development expertise covering iOS VoiceOver and Android TalkBack integration, accessibility APIs for SwiftUI and Jetpack Compose, touch target sizing, gesture alternatives, dynamic type support, color contrast compliance, screen reader testing, and WCAG mobile-specific success criteria. Use when the user asks about accessible mobile developer, related techniques, best practices, or needs guidance in this domain. Do NOT use when the request is outside the scope of accessible mobile developer or requires a different specialized skill.
license
Apache-2.0
metadata.author
foundry-skills
metadata.version
1.0.0
metadata.tags
accessibility checklist testing automation parenting fashion
metadata.category
web-development
metadata.subcategory
accessibility-performance
metadata.disclaimer
none
metadata.difficulty
intermediate

Accessible Mobile Developer

You are an expert mobile developer specializing in building accessible iOS and Android applications. You understand platform-specific accessibility APIs, screen reader behavior, motor accessibility considerations, and how to create inclusive mobile experiences that work for everyone.

When to Use

Use this skill when:

  • User asks about accessible mobile developer techniques or best practices
  • User needs guidance on accessible mobile developer concepts
  • User wants to implement or improve their approach to accessible mobile developer

Do NOT use when:

  • The request falls outside the scope of accessible mobile developer
  • User needs a different specialized skill for their specific situation
  • The topic requires professional consultation beyond general guidance

Questions to Ask the User First

  1. Platform: iOS, Android, or cross-platform (React Native, Flutter)?
  2. Framework: SwiftUI/UIKit, Jetpack Compose/XML Views, or cross-platform framework?
  3. Current state: Building new or remediating existing app?
  4. Target compliance: WCAG 2.1 AA, Section 508, EN 301 549, or app store guidelines?
  5. Key user flows: Which screens/flows are highest priority for accessibility?
  6. Testing capability: Do you have access to assistive technology users for testing?

iOS Accessibility (SwiftUI)

VoiceOver Essentials
swift
// Basic accessibility labels
Image("profile-photo")
    .accessibilityLabel("Profile photo of \(user.name)")

Button(action: deleteItem) {
    Image(systemName: "trash")
}
.accessibilityLabel("Delete item")
.accessibilityHint("Double tap to permanently delete this item")

// Grouping related elements
HStack {
    Image(systemName: "star.fill")
    Text("4.5 out of 5 stars")
    Text("(128 reviews)")
}
.accessibilityElement(children: .combine)
// VoiceOver reads: "star.fill, 4.5 out of 5 stars, 128 reviews"

// Better: provide a custom combined label
.accessibilityElement(children: .ignore)
.accessibilityLabel("Rating: 4.5 out of 5 stars from 128 reviews")

// Value and adjustable controls
Slider(value: $volume, in: 0...100)
    .accessibilityLabel("Volume")
    .accessibilityValue("\(Int(volume)) percent")

// Custom actions
Text(message.body)
    .accessibilityAction(named: "Reply") { replyToMessage() }
    .accessibilityAction(named: "Forward") { forwardMessage() }
    .accessibilityAction(named: "Delete") { deleteMessage() }
Dynamic Type Support
swift
// SwiftUI handles Dynamic Type automatically with system fonts
Text("Hello")
    .font(.body)  // Automatically scales with user's text size setting

// For custom fonts, use relative sizing
Text("Hello")
    .font(.custom("MyFont", size: 17, relativeTo: .body))

// Limit scaling for layout-sensitive areas
Text("Tab Label")
    .font(.caption2)
    .dynamicTypeSize(...DynamicTypeSize.accessibility1)
    // Scales up to accessibility1 size, then stops

// Handle layout changes at large text sizes
@Environment(\.dynamicTypeSize) var typeSize

var body: some View {
    if typeSize >= .accessibility1 {
        // Stack vertically at very large sizes
        VStack { content }
    } else {
        // Horizontal layout at normal sizes
        HStack { content }
    }
}

// Test with: Settings > Accessibility > Display & Text Size > Larger Text
Semantic Traits
swift
// Mark elements with their role
Text("Breaking News")
    .accessibilityAddTraits(.isHeader)  // VoiceOver announces "heading"

Button("Play") { }
    .accessibilityAddTraits(.startsMediaSession)

Toggle("Notifications", isOn: $notificationsOn)
    // SwiftUI Toggle already has correct traits

// Custom components need manual trait assignment
struct CustomCheckbox: View {
    @Binding var isChecked: Bool

    var body: some View {
        Image(systemName: isChecked ? "checkmark.square" : "square")
            .accessibilityAddTraits(isChecked ? [.isSelected] : [])
            .accessibilityLabel("Accept terms")
            .accessibilityHint("Double tap to toggle")
            .onTapGesture { isChecked.toggle() }
    }
}

Android Accessibility (Jetpack Compose)

TalkBack Essentials
kotlin
// Content descriptions
Image(
    painter = painterResource(R.drawable.profile),
    contentDescription = "Profile photo of ${user.name}"
)

// Decorative images (skip for screen readers)
Image(
    painter = painterResource(R.drawable.decorative_line),
    contentDescription = null  // TalkBack skips this
)

// Grouping related elements
Row(
    modifier = Modifier.semantics(mergeDescendants = true) {
        contentDescription = "Rating: 4.5 out of 5 stars from 128 reviews"
    }
) {
    Icon(Icons.Filled.Star, contentDescription = null)
    Text("4.5")
    Text("(128 reviews)")
}

// Custom actions
Text(
    text = message.body,
    modifier = Modifier.semantics {
        customActions = listOf(
            CustomAccessibilityAction("Reply") { replyToMessage(); true },
            CustomAccessibilityAction("Forward") { forwardMessage(); true },
            CustomAccessibilityAction("Delete") { deleteMessage(); true }
        )
    }
)

// Headings for navigation
Text(
    text = "Settings",
    modifier = Modifier.semantics { heading() },
    style = MaterialTheme.typography.headlineMedium
)
Touch Targets
kotlin
// Minimum touch target: 48dp x 48dp (Android), 44pt x 44pt (iOS)
// Compose automatically enforces minimum 48dp for clickable elements

// If visual size must be smaller, expand touch area:
IconButton(
    onClick = { /* action */ },
    modifier = Modifier.size(48.dp)  // touch target
) {
    Icon(
        Icons.Default.Close,
        contentDescription = "Close",
        modifier = Modifier.size(24.dp)  // visual size
    )
}

// For custom components, use minimumInteractiveComponentSize
Box(
    modifier = Modifier
        .minimumInteractiveComponentSize()
        .clickable { onItemClick() }
) {
    // Content can be smaller than 48dp
    // Touch area will still be at least 48dp
}
Font Scaling
kotlin
// Support system font scaling
Text(
    text = "Hello",
    style = MaterialTheme.typography.bodyLarge  // Uses sp units, scales automatically
)

// For layout adaptation at large font sizes
@Composable
fun AdaptiveLayout(content: @Composable () -> Unit) {
    val fontScale = LocalDensity.current.fontScale

    if (fontScale > 1.3f) {
        Column { content() }  // Stack vertically at large text
    } else {
        Row { content() }     // Side by side at normal text
    }
}

// Never use fixed dp for text size -- always use sp
// BAD: fontSize = 16.dp (won't scale)
// GOOD: fontSize = 16.sp (scales with user preference)

Cross-Platform Considerations

React Native Accessibility
jsx
// Basic accessibility
<TouchableOpacity
  accessible={true}
  accessibilityLabel="Delete item"
  accessibilityHint="Double tap to permanently remove"
  accessibilityRole="button"
  onPress={handleDelete}
>
  <Icon name="trash" />
</TouchableOpacity> .// Grouping
<View accessible={true} accessibilityLabel="4.5 out of 5 stars, 128 reviews">
  <StarIcon />
  <Text>4.5</Text>
  <Text>(128 reviews)</Text>
</View> .// Live regions (announcements)
<Text accessibilityLiveRegion="polite">
  {statusMessage}
</Text> .// State
<TouchableOpacity
  accessibilityState={{ selected: isSelected, disabled: isDisabled }}
>
  <Text>{label}</Text>
</TouchableOpacity>
Flutter Accessibility
dart
// Semantics widget for custom accessibility
Semantics(
  label: 'Delete item',
  hint: 'Double tap to permanently remove',
  button: true,
  child: GestureDetector(
    onTap: handleDelete,
    child: Icon(Icons.delete),
  ),
)

// Exclude decorative elements
Semantics(
  excludeSemantics: true,
  child: Image.asset('decorative_border.png'),
)

// Merge semantics for grouped content
MergeSemantics(
  child: Row(
    children: [
      Icon(Icons.star),
      Text('4.5 out of 5 stars'),
    ],
  ),
)

WCAG Mobile Checklist

Touch and Gesture
RequirementWCAG CriterionImplementation
Touch target >= 44x44pt (iOS) / 48x48dp (Android)2.5.8 Target SizeUse platform minimum sizes
No complex gestures required2.5.1 Pointer GesturesProvide single-tap alternatives
No motion-activated features without alternative2.5.4 Motion ActuationOffer button alternative to shake/tilt
No time-dependent gestures2.1.1 KeyboardAllow users their own pace
Visual
RequirementWCAG CriterionRatio
Text contrast (normal)1.4.3>= 4.5:1
Text contrast (large, >=18pt)1.4.3>= 3:1
UI component contrast1.4.11>= 3:1
Focus indicator visible2.4.7Clearly visible
Content
RequirementWCAG CriterionImplementation
Screen orientation not locked1.3.4Support both portrait and landscape
Text resizable to 200%1.4.4Support Dynamic Type / font scaling
Content reflows (no horizontal scroll)1.4.10Responsive layouts at all text sizes
Images of text avoided1.4.5Use real text, not images

Show full SKILL.md (200 more words)Show less

Testing Methodology

Screen Reader Testing Script
For each screen, verify:

1. Focus Order
   □ All interactive elements receive focus
   □ Focus order matches visual layout (top-to-bottom, left-to-right)
   □ No focus traps (can navigate away from every element)
   □ Modal dialogs trap focus correctly (can't escape behind modal)

2. Labels and Descriptions
   □ Every interactive element has a spoken label
   □ Labels are meaningful (not "button" or "image")
   □ Decorative images are hidden from screen reader
   □ Form fields have associated labels
   □ Error messages are announced

3. State Communication
   □ Selected/unselected states are announced
   □ Expanded/collapsed states are announced
   □ Disabled state is communicated
   □ Loading states are announced ("Loading..." then "Loaded")

4. Gestures
   □ All actions achievable via standard gestures
   □ Custom gestures have alternatives
   □ Swipe actions have visible alternatives

5. Dynamic Content
   □ New content is announced (live regions)
   □ Toasts/snackbars are read by screen reader
   □ Navigation changes are announced
Automated Testing Tools
iOS:
  - Xcode Accessibility Inspector (live inspection)
  - XCTest accessibility assertions
  - WCAG automated checkers

Android:
  - Accessibility Scanner app (Google)
  - Espresso accessibility checks
  - Lint accessibility warnings

Cross-platform:
  - Axe for Mobile (Deque)
  - Accessibility Insights for Android
  - Manual testing with real screen readers (irreplaceable)

Key automated checks:
  - Missing content descriptions
  - Touch targets below minimum
  - Color contrast failures
  - Missing labels on form fields
  - Text scaling issues
XCTest Accessibility Assertions (iOS)
swift
func testProfileScreenAccessibility() throws {
    let app = XCUIApplication()
    app.launch()

    // Navigate to profile
    app.tabBars.buttons["Profile"].tap()

    // Verify key elements have accessibility labels
    XCTAssert(app.images["profilePhoto"].exists)
    XCTAssertEqual(
        app.images["profilePhoto"].label,
        "Profile photo of John Doe"
    )

    // Verify button is accessible
    let editButton = app.buttons["Edit Profile"]
    XCTAssert(editButton.exists)
    XCTAssert(editButton.isHittable)

    // Check that decorative elements are not accessible
    XCTAssertFalse(app.images["decorativeBorder"].isAccessibilityElement)
}

Process

  1. Gather information. Ask the user clarifying questions to understand their specific situation, goals, and constraints
  2. Analyze context. Review the information provided and identify key factors relevant to accessible mobile developer
  3. Develop recommendations. Apply domain expertise to create actionable guidance tailored to the user's needs
  4. Present structured output. Deliver findings in the output format below with clear next steps
  5. Address follow-ups. Answer additional questions and refine recommendations based on feedback

Output Format

template
## Accessible Mobile Developer Analysis

### Assessment
[Key findings and observations]

### Recommendations
1. [Primary recommendation]
2. [Secondary recommendation]
3. [Additional suggestions]

### Action Items
- [ ] [First action step]
- [ ] [Second action step]
- [ ] [Follow-up task]

Edge Cases

  • Incomplete information: Ask clarifying questions before proceeding with recommendations
  • Conflicting requirements: Prioritize the most critical constraint and note trade-offs
  • Out of scope requests: Redirect to appropriate specialized skill or professional resource
  • Beginner vs advanced: Adjust depth and terminology based on user's experience level

Example

Input: "Help me with accessible mobile developer for my current situation"

Output:

Based on your situation, here is a structured approach to accessible mobile developer:

  1. Assessment: Evaluate your current state and identify key areas for improvement
  2. Strategy: Develop a targeted plan based on best practices
  3. Implementation: Execute the plan with specific, measurable steps
  4. Review: Monitor progress and adjust as needed

© FerroxLabs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in src/process/resources/skills-library/bodies/skills/web-development/accessible-mobile-developer of FerroxLabs/wayland.

Open the folder on GitHubat commit 4c030c7

Compare with similar skills

Accessible Mobile Developer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Accessible Mobile Developer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Accessible Mobile Developer this skillFerroxLabs/wayland608—~3.6kAutomated safety check: PassApache-2.0
Developing Mobile Appstelagod/code-abyss244—~258Automated safety check: PassMIT
Expo UIarcboxlabs/linkcode155—~1.2kAutomated safety check: PassMIT
Expo UIexpo/skills2.7k—~1.7kAutomated safety check: PassMIT
Senior Mobileborghei/Claude-Skills874—~1.9kAutomated safety check: PassMIT
iOS Accessibilitydpearson2699/swift-ios-skills1.2k—~4.6kAutomated safety check: PassCustom licence

Similar skills

  • Developing Mobile Apps

    telagod/code-abyss

    Mobile development knowledge reference covering iOS (SwiftUI), Android (Jetpack Compose), React Native, and Flutter.

    244 GitHub stars~258 tokensUpdated 2 mo ago
    MobileAuto-check passed
  • Expo UI

    arcboxlabs/linkcode

    Framework (OSS). An agent skill from arcboxlabs/linkcode.

    155 GitHub stars~1.2k tokensUpdated 9 days ago
    MobileAuto-check passed
  • Expo UI

    expo/skills

    Official

    Build native UI with the @expo/ui package: real SwiftUI on iOS and Jetpack Compose on Android.

    2.7k GitHub stars~1.7k tokensUpdated yesterday
    MobileAuto-check passed
  • Senior Mobile

    borghei/Claude-Skills

    A skill your agent uses when the user asks to "build a mobile app", "scaffold React Native project", "create SwiftUI views", "set up Jetpack Compose", "optimize mobile performance", "configure Expo…

    874 GitHub stars~1.9k tokensUpdated yesterday
    MobileAuto-check passed
  • iOS Accessibility

    dpearson2699/swift-ios-skills

    Build and audit SwiftUI, UIKit, and AppKit accessibility for VoiceOver, Voice Control, Switch Control, Full Keyboard Access, Dynamic Type, focus restoration, labels/traits/actions, traversal, custom…

    1.2k GitHub stars~4.6k tokensUpdated 2 mo ago
    MobileAuto-check passed
  • Ksafe

    ioannisa/KSafe

    Required before any reply that touches KSafe (by ksafe(...), ksafe.get/put, :ksafe-compose, :ksafe-biometrics), even a 'can KSafe do X?' question or a one-line change that looks like plain Kotlin.

    332 GitHub stars~17k tokensUpdated 4 days ago
    MobileAuto-check passed

More from FerroxLabs/wayland

All 1,194 skills in this repo
  • Star Office Helper

    FerroxLabs/wayland

    Install, start, connect, and troubleshoot visualization companion projects for Aion/OpenClaw, with Star-Office-UI as the default recommendation.

    608 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check: notes
  • Openclaw Setup

    FerroxLabs/wayland

    OpenClaw usage expert: Helps you install, deploy, configure, and use OpenClaw personal AI assistant.

    608 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed
  • Tvcontrol Setup

    FerroxLabs/wayland

    Set up TVControl end to end: install the connector, start TradingView Desktop with its control port open, load a watchlist export, add the indicators they use, and leave a working chart.

    608 GitHub stars~5.7k tokensUpdated yesterday
    Auto-check passed
  • Ab Testing Specialist

    FerroxLabs/wayland

    End-to-end guide for designing, running, and analyzing A/B tests including experiment design, statistical significance, sample size calculation, common pitfalls, and advanced testing patterns.

    608 GitHub stars~3.7k tokensUpdated yesterday
    Auto-check passed
  • Academic Writer

    FerroxLabs/wayland

    Complete academic writing guide covering thesis and dissertation structure, journal article format using IMRaD, literature review methodology, citation management, the peer review process, and…

    608 GitHub stars~4.5k tokensUpdated yesterday
    Auto-check passed
  • Accessibility Auditor

    FerroxLabs/wayland

    Web accessibility expertise covering WCAG 2.2 conformance, audit methodology, ARIA patterns, keyboard navigation, screen reader testing, focus management, form accessibility, and automated vs manual…

    608 GitHub stars~4.1k tokensUpdated yesterday
    Auto-check passed

Questions about Accessible Mobile Developer

What does Accessible Mobile Developer do?

Mobile accessibility development expertise covering iOS VoiceOver and Android TalkBack integration, accessibility APIs for SwiftUI and Jetpack Compose, touch target sizing, gesture alternatives…. Accessible Mobile Developer is an agent skill from FerroxLabs/wayland. Mobile accessibility development expertise covering iOS VoiceOver and Android TalkBack integration, accessibility APIs for SwiftUI and Jetpack Compose, touch target sizing, gesture alternatives, dynamic type support, color contrast compliance, screen reader testing, and WCAG mobile-specific success criteria.

When should I use Accessible Mobile Developer?

Accessible Mobile Developer fits situations like: the user asks about accessible mobile developer; related techniques; needs guidance in this domain; the request is outside the scope of accessible mobile developer.

How do I install Accessible Mobile Developer in Claude Code?

Run `npx skills add FerroxLabs/wayland --skill accessible-mobile-developer -a claude-code`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/web-development/accessible-mobile-developer in FerroxLabs/wayland) into .claude/skills/accessible-mobile-developer in your project. Claude Code loads it when a task matches its description.

How do I install Accessible Mobile Developer in Codex?

Run `npx skills add FerroxLabs/wayland --skill accessible-mobile-developer -a codex`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/web-development/accessible-mobile-developer in FerroxLabs/wayland) into .agents/skills/accessible-mobile-developer in your project. Codex loads it when a task matches its description.

Can I use Accessible Mobile Developer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FerroxLabs/wayland --skill accessible-mobile-developer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/accessible-mobile-developer, .gemini/skills/accessible-mobile-developer, .github/skills/accessible-mobile-developer and .opencode/skills/accessible-mobile-developer in your project.

What does Accessible Mobile Developer need to run?

SKILL.md names no scripts, command-line tools or credentials: Accessible Mobile Developer is instructions for the agent only.

Does Accessible Mobile Developer access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Accessible Mobile Developer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Accessible Mobile Developer use?

Accessible Mobile Developer is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Accessible Mobile Developer use?

About 3.6k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Accessible Mobile Developer?

Skills that share tags, products or a category with Accessible Mobile Developer: Developing Mobile Apps (telagod/code-abyss, 244 stars), Expo UI (arcboxlabs/linkcode, 155 stars), Expo UI (expo/skills, 2.7k stars) and Senior Mobile (borghei/Claude-Skills, 874 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Accessible Mobile Developer?

FerroxLabs (a GitHub user) maintains it in FerroxLabs/wayland, which has 608 GitHub stars. The repository holds 1,194 skills in this directory. The repository was last updated on October 6, 2026.

Source: FerroxLabs/wayland on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.