Agent skill

iOS Worker

Implements and tests SwiftUI views, navigation flows, and shared iOS design-system work for ADE

AGPL-3.0Auto-check passedMobile

Install iOS Worker

skills CLI

$ npx skills add arul28/ADE --skill ios-worker -a claude-code

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

GitHub CLI

$ gh skill install arul28/ADE ios-worker --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/arul28/ADE.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.factory/skills/ios-worker .claude/skills/ios-worker && 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/

Paste into Claude Code

Install the "ios-worker" agent skill from https://github.com/arul28/ADE/tree/main/.factory/skills/ios-worker into .claude/skills/ios-worker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ios-worker", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/arul28/ADE/tree/main/.factory/skills/ios-worker

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add arul28/ADE --skill ios-worker -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install arul28/ADE ios-worker --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/arul28/ADE.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.factory/skills/ios-worker .agents/skills/ios-worker && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "ios-worker" agent skill from https://github.com/arul28/ADE/tree/main/.factory/skills/ios-worker into .agents/skills/ios-worker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ios-worker", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add arul28/ADE --skill ios-worker -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install arul28/ADE ios-worker --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/arul28/ADE.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.factory/skills/ios-worker .cursor/skills/ios-worker && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "ios-worker" agent skill from https://github.com/arul28/ADE/tree/main/.factory/skills/ios-worker into .cursor/skills/ios-worker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ios-worker", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/arul28/ADE.git --path .factory/skills/ios-worker

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add arul28/ADE --skill ios-worker -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install arul28/ADE ios-worker --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/arul28/ADE.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.factory/skills/ios-worker .gemini/skills/ios-worker && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "ios-worker" agent skill from https://github.com/arul28/ADE/tree/main/.factory/skills/ios-worker into .gemini/skills/ios-worker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ios-worker", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install arul28/ADE ios-worker

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add arul28/ADE --skill ios-worker -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/arul28/ADE.git skills-src && mkdir -p .github/skills && cp -r skills-src/.factory/skills/ios-worker .github/skills/ios-worker && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "ios-worker" agent skill from https://github.com/arul28/ADE/tree/main/.factory/skills/ios-worker into .github/skills/ios-worker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ios-worker", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add arul28/ADE --skill ios-worker -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install arul28/ADE ios-worker --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/arul28/ADE.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.factory/skills/ios-worker .opencode/skills/ios-worker && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "ios-worker" agent skill from https://github.com/arul28/ADE/tree/main/.factory/skills/ios-worker into .opencode/skills/ios-worker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ios-worker", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: ios-worker
GitHub stars: 114
Token cost: ~2.3k tokens
SKILL.md length: 762 words
Files: 1
Skills in repo: 28
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: AGPL-3.0

At a glance

Implements and tests SwiftUI views, navigation flows, and shared iOS design-system work for ADE

Works in 8 steps: Understand the Feature → Plan the Changes → Write Tests First (Red) → …
Tasks that involve iOS development
SKILL.md covers When to Use This Skill, Work Procedure, Example Handoff and When to Return to Orchestrator
Calls xcodebuild

What it does

iOS Worker is an agent skill from arul28/ADE. Implements and tests SwiftUI views, navigation flows, and shared iOS design-system work for ADE

Its SKILL.md is about 2.3k 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 iOS development and Design systems. It works with iOS and SwiftUI. The licence is AGPL-3.0.

When your agent uses it

Tasks that involve iOS development
Tasks that involve Design systems

Example prompts

“Use the ios-worker skill to implement and tests SwiftUI views, navigation flows, and shared iOS design-system work for ADE”
“/ios-worker”

Workflow steps

8 steps, taken from the step headings in SKILL.md.

Understand the Feature
Plan the Changes
Write Tests First (Red)
Implement (Green)
Update Xcode Project
Verify
Manual Verification
Commit

What it can do on your machine

Read from SKILL.md and the folder at commit fbbd974. 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
Shell commands in SKILL.md call:
- xcodebuild
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

iOS Worker loads about 2.3k tokens when it runs. Until then it costs about 27 tokens; SKILL.md has 762 words of instructions outside code blocks.

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

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 arul28/ADE at commit fbbd974, republished under its AGPL-3.0 licence (© arul28). 762 words, ~2,259 tokens.

Download SKILL.mdSave it as .claude/skills/ios-worker/SKILL.md (or your agent's skills folder).

name: ios-worker
description: Implements and tests SwiftUI views, navigation flows, and shared iOS design-system work for ADE

iOS Worker

NOTE: Startup and cleanup are handled by worker-base. This skill defines the WORK PROCEDURE.

When to Use This Skill

Use for features that are primarily iOS UI work inside apps/ios/ADE/, including:

SwiftUI screen extraction and file splitting
mobile information architecture changes inside existing tabs
shared iOS design-system and Liquid Glass component work
accessibility and motion-polish work
iOS-side performance cleanup in view code
iOS tests in apps/ios/ADETests/

Do not use this skill for desktop sync-host, shared contract, SyncService, RemoteModels, or database features. Those belong to a sync/backend worker.

Work Procedure

1. Understand the Feature

Read the feature description, preconditions, expectedBehavior, and verificationSteps carefully. Then:

Read mission.md for overall mission context
Read AGENTS.md for boundaries and conventions
Read .factory/library/architecture.md for app architecture and patterns
Read .factory/library/tab-parity.md and .factory/library/performance.md when the feature touches parity or lag-sensitive flows
Read the existing code files you'll be modifying in full
If the feature touches a tab other than Lanes, still read the relevant Lanes benchmark components to match the established mobile quality bar

2. Plan the Changes

Before writing any code:

List every file you'll create or modify
Identify which existing code to preserve vs. rewrite
Note which existing syncService methods the views need to call
Identify which shared components should be promoted into Views/Components/ instead of duplicated inside a tab
Check that your plan stays on the iOS/UI side of the boundary; if the feature needs SyncService, RemoteModels, Database, or desktop host changes, stop and return to the orchestrator

3. Write Tests First (Red)

For any testable logic (filters, computed properties, data transformations, directory grouping):

Add test cases to ADETests.swift (the single test file)
Tests should fail initially (red phase)
Use @testable import ADE and XCTest patterns matching existing tests
Focus on logic tests, not UI rendering tests

4. Implement (Green)

Write the SwiftUI code:

File organization: Each major screen or slice gets its own file under the relevant tab folder (Views/Lanes/, Views/Files/, Views/Work/, Views/PRs/, Views/Settings/). Keep files under 500 lines; if a feature leaves a file bigger than that, split again before handing off.
Design system: Use ADEColor.*, ADEMotion.*, .adeGlassCard(), .adeInsetField(), .adeNavigationGlass(), .adeScreenBackground(), ADENoticeCard, ADEStatusPill, ADEEmptyStateView, ADESkeletonView, ADECardSkeleton, and shared glass helpers instead of ad-hoc styling.
Liquid Glass: Prefer shared glass primitives and matched navigation transitions over one-off background/stroke recipes. When adding repeated chips or buttons, prefer reusable shared components instead of tab-local copies.
Accessibility: Add .accessibilityLabel to all interactive elements. Use ADEMotion which respects reduceMotion. Preserve .sensoryFeedback on appropriate interactions.
Data access: Use @EnvironmentObject var syncService: SyncService. Call existing SyncService methods — never add new ones.
State management: Use @State for local state. Prefer debounced .task(id: syncService.localStateRevision) patterns matching the Lanes benchmark when reloading cached projections.
Performance: Use lazy containers for large lists, avoid heavy parsing/computation in body, cache expensive derived values in state/view-model helpers, and preserve source-tab context on return navigation.
Boundary: No changes to SyncService.swift, RemoteModels.swift, Database.swift, desktop services, or shared sync contracts from this skill.

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

5. Update Xcode Project

When creating new Swift files, you MUST add them to the Xcode project:

Edit apps/ios/ADE.xcodeproj/project.pbxproj to add file references and build phase entries
Follow the existing pattern in the pbxproj for file references (PBXFileReference, PBXBuildFile, PBXGroup children)
Alternatively, if the project uses folder references, ensure files are in the correct directory

6. Verify

Run these commands and fix any issues:

bash

# Mission simulator target
DESTINATION="platform=iOS Simulator,name=iPhone 17 Pro,OS=26.3.1"

# Build / test / analyzer
xcodebuild build -project apps/ios/ADE.xcodeproj -scheme ADE -destination "$DESTINATION" -quiet
xcodebuild test -project apps/ios/ADE.xcodeproj -scheme ADE -destination "$DESTINATION" -quiet
xcodebuild -project apps/ios/ADE.xcodeproj -scheme ADE -destination "$DESTINATION" -derivedDataPath /tmp/ade-build analyze

# Check file sizes (no file should exceed 500 lines)
find apps/ios/ADE -name '*.swift' -exec wc -l {} + | sort -rn | head -20

All must pass for the touched surface. If build or tests fail, fix immediately. If a failure is clearly pre-existing and outside the feature boundary, return to the orchestrator with evidence instead of hand-waving past it.

7. Manual Verification

Do the strongest manual verification the feature allows:

Trace the full data flow from SyncService through the view hierarchy
Verify syncService method calls and model property names match the existing API exactly
If the feature can be checked in the simulator without a live host, do so
If the feature depends on live sync data, validate against the paired desktop host when that service is available in the mission
Check that navigation back/return preserves the source context for mobile triage flows
Ensure no unused imports, dead code, placeholder copy, or TODO markers remain

8. Commit

Commit with a clear message describing what was implemented.

Example Handoff

json

{
  "salientSummary": "Split the Work tab into mobile-first subviews, added a reusable glass section/chip stack in Views/Components, and stabilized session list/detail navigation so filters and context survive round-trips. Build, tests, and analyzer passed on the mission simulator target.",
  "whatWasImplemented": "Refactored WorkTabView.swift into focused files under Views/Work/, promoted reusable glass chips/section containers into Views/Components/, and updated the Work list/detail flows to preserve lane/search/filter context when opening sessions and returning. The new UI keeps chat/terminal sessions readable on iPhone, uses shared glass styling, and removes several hot-path computations from SwiftUI body evaluation.",
  "whatWasLeftUndone": "",
  "verification": {
    "commandsRun": [
      {
        "command": "xcodebuild build -project apps/ios/ADE.xcodeproj -scheme ADE -destination 'platform=iOS Simulator,name=iPhone 17 Pro,OS=26.3.1' -quiet",
        "exitCode": 0,
        "observation": "Build succeeded with no errors or warnings"
      },
      {
        "command": "xcodebuild test -project apps/ios/ADE.xcodeproj -scheme ADE -destination 'platform=iOS Simulator,name=iPhone 17 Pro,OS=26.3.1' -quiet",
        "exitCode": 0,
        "observation": "The iOS test suite passed on the mission destination"
      },
      {
        "command": "xcodebuild -project apps/ios/ADE.xcodeproj -scheme ADE -destination 'platform=iOS Simulator,name=iPhone 17 Pro,OS=26.3.1' -derivedDataPath /tmp/ade-build analyze",
        "exitCode": 0,
        "observation": "Static analysis completed without blocking diagnostics"
      },
      {
        "command": "find apps/ios/ADE -name '*.swift' -exec wc -l {} + | sort -rn | head -20",
        "exitCode": 0,
        "observation": "New and modified Swift files stayed within the file-size limit after extraction"
      }
    ],
    "interactiveChecks": [
      {
        "action": "Traced session list → session detail → back navigation on the refactored Work surface",
        "observed": "The source lane/filter/search context remained intact after returning from detail"
      },
      {
        "action": "Reviewed all promoted shared components and the new Work subviews against the existing SyncService API",
        "observed": "All property and method accesses remained within the existing iOS/UI boundary and matched current signatures"
      }
    ]
  },
  "tests": {
    "added": []
  },
  "discoveredIssues": []
}

When to Return to Orchestrator

The feature requires changes to SyncService, RemoteModels, Database, desktop services, or shared sync contracts
The existing API/data shape cannot support the feature without backend or contract work
Xcode project state becomes corrupted or unrecoverable
Build/test/analyzer failures are outside the touched iOS surface and cannot be repaired safely inside the feature boundary
A file still exceeds 500 lines after a reasonable split attempt

Files

Just SKILL.md in .factory/skills/ios-worker of arul28/ADE.

Open the folder on GitHubat commit fbbd974

Compare with similar skills

iOS Worker 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.

iOS Worker compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
iOS Worker this skillarul28/ADE	114	—	~2.3k	Automated safety check: Pass	AGPL-3.0	today
Native App Designercuriositech/some_claude_skills	243	—	~1.9k	Automated safety check: Notes	MIT	1 mo ago
Hig Project Contextraintree-technology/hig-doctor	143	5 repos	~1.2k	Automated safety check: Pass	MIT	27 days ago
Hig Components Contentraintree-technology/hig-doctor	143	5 repos	~1.3k	Automated safety check: Pass	MIT	27 days ago
macOS App Designvaayne/mori	303	—	~789	Automated safety check: Pass	MIT	2 mo ago
iOS Design Guidelinesehmo/platform-design-skills	606	—	~9k	Automated safety check: Pass	MIT	6 mo ago

Similar skills

Native App Designer
curiositech/some_claude_skills
Creates breathtaking iOS/Mac and web apps with organic, non-AI aesthetic.
243 GitHub stars~1.9k tokensUpdated 1 mo ago
MobileAuto-check: notes
Hig Project Context
raintree-technology/hig-doctor
Create or update a shared Apple design context document that other HIG skills use to tailor guidance.
143 GitHub starsUsed in 5 repos~1.2k tokens
MobileAuto-check passed
Hig Components Content
raintree-technology/hig-doctor
Apple Human Interface Guidelines for content display components.
143 GitHub starsUsed in 5 repos~1.3k tokens
MobileAuto-check passed
macOS App Design
vaayne/mori
A skill your agent uses when designing or building native macOS applications with SwiftUI or AppKit.
303 GitHub stars~789 tokensUpdated 2 mo ago
MobileAuto-check passed
iOS Design Guidelines
ehmo/platform-design-skills
Apple Human Interface Guidelines for iPhone. An agent skill from ehmo/platform-design-skills.
606 GitHub stars~9k tokensUpdated 6 mo ago
MobileAuto-check passed
Aipay Frontend Theme
OpenAIPay/openaipay
A skill your agent uses when changing AiPay iOS frontend color style, replacing blue UI to purple, updating screenshot-based Reference pages, or enforcing component theme consistency across parallel…
129 GitHub stars~386 tokensUpdated 5 mo ago
MobileAuto-check passed

Questions about iOS Worker

What does iOS Worker do?

Implements and tests SwiftUI views, navigation flows, and shared iOS design-system work for ADE. iOS Worker is an agent skill from arul28/ADE.

When should I use iOS Worker?

iOS Worker fits situations like: tasks that involve iOS development; tasks that involve Design systems.

How do I install iOS Worker in Claude Code?

Run `npx skills add arul28/ADE --skill ios-worker -a claude-code`. Or copy the skill folder (.factory/skills/ios-worker in arul28/ADE) into .claude/skills/ios-worker in your project. Claude Code loads it when a task matches its description.

How do I install iOS Worker in Codex?

Run `npx skills add arul28/ADE --skill ios-worker -a codex`. Or copy the skill folder (.factory/skills/ios-worker in arul28/ADE) into .agents/skills/ios-worker in your project. Codex loads it when a task matches its description.

Can I use iOS Worker 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 arul28/ADE --skill ios-worker -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ios-worker, .gemini/skills/ios-worker, .github/skills/ios-worker and .opencode/skills/ios-worker in your project.

What does iOS Worker need to run?

Going by SKILL.md and its folder, iOS Worker needs the command-line tools its instructions call (xcodebuild).

Does iOS Worker 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 iOS Worker 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 iOS Worker use?

iOS Worker is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does iOS Worker use?

About 2.3k tokens (SKILL.md is roughly 9k 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 iOS Worker?

Skills that share tags, products or a category with iOS Worker: Native App Designer (curiositech/some_claude_skills, 243 stars), Hig Project Context (raintree-technology/hig-doctor, 143 stars), Hig Components Content (raintree-technology/hig-doctor, 143 stars) and macOS App Design (vaayne/mori, 303 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains iOS Worker?

arul28 (a GitHub user) maintains it in arul28/ADE, which has 114 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on October 8, 2026.

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

Install iOS Worker

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

iOS Worker

When to Use This Skill

Work Procedure

1. Understand the Feature

2. Plan the Changes

3. Write Tests First (Red)

4. Implement (Green)

5. Update Xcode Project

6. Verify

7. Manual Verification

8. Commit

Example Handoff

When to Return to Orchestrator

Files

Compare with similar skills

Similar skills

More from arul28/ADE

Related

Questions about iOS Worker