96 tagged swift, measured the same way as everything else here.
Browse within: ios 73swiftui 35android 17base-project 17baseview 17kotlin 17kotlin-multiplatform 17programmatically-layout 17herdr 14terminal 14terminal-app 14tmux 14axiom 12macos 11
Agent
Hermex ships one String Catalog, HermesMobile/Resources/Localizable.xcstrings, included in the app, widget, and share-extension targets. Every user-facing literal is already externalized (String(localized:) / LocalizedStringKey), so adding a language is normally translation-only — no Swift edits.
Agent
Durable rules for the shipped Kanban feature (HermesMobile/Features/Kanban/). These are normative where they differ from the desktop WebUI. Vocabulary is owned by root CONTEXT.md: upstream task/taskid stay network-boundary names; user-facing and Swift domain names use Card with a Kanban qualifier.
Agent
Which app state is per-server versus intentionally global, where each lives, and which tests guard the isolation. Almost all isolation holds by construction through the server-keyed view tree and cache keys described below; "Clear Offline Cache" is explicitly scoped to the active server.
Agent
How engineering skills should consume this repo's domain documentation.
Agent
Issues and PRDs for this repo live as GitHub issues in shaps80/SwiftUIBackports. Use the gh CLI for operations when connector tools are not already handling GitHub work.
Agent
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
Agent
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
Agent
Issues and PRDs for this repo live as GitHub issues on christopherkarani/Swarm. Use the gh CLI for all operations.
Agent
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
Agent Claude Code
No-fix diagnoser for one failing PR status check on the TMDb repo — runs the routed diagnosis skill (/diagnose-ci-failure or /diagnose-integration-failure) and returns only its three-section Summary / Likely cause / Suggested fix result, never raw logs; it reports, never applies. Spawned by /fix-pr-checks (directly…
Agent Claude Code
Code reviewer subagent to be used to review code changes when asked, or at appropriate points when implementing new features.
Agent Claude Code
Haiku runner for TMDb build/test commands — executes exactly one make target (or its xcode-tools MCP equivalent), writes the full output to a .build/last-.log file, and returns only a concise pass/fail + failures-as-file:line summary. Spawned by the /build, /build-for-testing, /test, and /integration-test skills; not…
Agent
Connect Claude Code to Remarc with the remarc plugin, and optionally let comments wake live sessions with remarc-hooks.
Agent
Install Remarc's public OMP plugins, verify the MCP connection, and pair a session for instant comment delivery.
Agent
Send Remarc comment events as HTTP POST JSON to Zapier, Make, n8n, IFTTT, Slack, or any other endpoint that accepts JSON.
ahmed3elshaer/everything-claude-code-mobile
Agent
Jetpack Compose patterns specialist. Guides on state management, recomposition optimization, theming, animations, and Compose best practices. Use when building or reviewing Compose UI.
ahmed3elshaer/everything-claude-code-mobile
Agent
Mobile architecture expert. Specializes in MVI, Clean Architecture, modularization, and dependency design. Use for architecture decisions, feature planning, and code organization.
ahmed3elshaer/everything-claude-code-mobile
Agent
SwiftUI patterns specialist. Guides on state management, view optimization, theming, animations, and SwiftUI best practices. Use when building or reviewing SwiftUI UI.
Agent
Layer 3 systematically scans ALL entry points from Layer 1 and applies issue detection rules. Unlike Layer 2 (which traces specific flows in depth), Layer 3 does a breadth-first scan to categorize issues across the entire codebase.
Agent
Layer 4 evaluates workflows from the user's perspective. While Layers 1-3 analyze code structure, Layer 4 asks: "Does this workflow help the user achieve their goal?".
Agent
Layer 5 verifies that features use real user data instead of mock/hardcoded values, and that model capabilities are fully wired into the features that need them. While Layers 1-4 audit navigation and UX, Layer 5 audits whether the data flowing through those workflows is genuine.
Agent
Builds complex custom SwiftUI views using standard SwiftUI components with TTBaseUIKit design tokens (XView/XSize/XFont). Does NOT use TTBaseSUI wrapper components.
Agent
Reviews native SwiftUI code for iOS 14+ API compliance, accessibility, performance, design, and TTBaseUIKit token compliance. Does NOT check for TTBaseSUI components.
Agent
Builds complete SwiftUI screens and components following TTBaseSUI and MVVM standards.