mobile-native
Skill40 starsChanged 4 days agoApache-2.0View on GitHub
Use when the request is broadly about iOS, Android, Capacitor plugins, or native parity and the correct mobile specialist skill is not yet clear.
27 other projects use a version of this.
Adopted by
Most recently taken up by
- sanity-io/sanitytheir own version, first seen Nov 16, 2026
- christofferbergj/agent-skillstheir own version, first seen Nov 16, 2026
- atpaawej/opencode-skillpacktheir own version, first seen Nov 16, 2026
- boraoztunc/skillstheir own version, first seen Nov 15, 2026
- egagofur/ai-engineering-looptheir own version, first seen Nov 15, 2026
- emilkowalski/skillstheir own version, first seen Nov 13, 2026
Used with
Projects with it also use ask-emil, choreograph and 8 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
emilkowalskiSkillask-emil
Ask which skill or flow fits your situation. A router over the skills in this repo.
Also in 4 projects that use this
boraoztuncSkillchoreograph
Coordinate several elements that animate together — decide what moves, in what order, how much they overlap, and what stays still — so a group reads as one intentional motion instead of a pile of separate animations. Use when building or fixing a staggered list, a hero entrance, a view swap inside a container, a multi-step flow, an element leaving while its siblings close the gap, a morph between rich states, or any interaction with several moving parts (icon + background + lines, panel + content, items flying into a target). Triggers on — stagger, sequence, choreography, "one after another", crossfade, AnimatePresence mode, hero entrance, multi-step, useAnimate, "feels mechanical", "too much going on", "feels slow to open".
Also in 5 projects that use this
boraoztuncSkillremove-animations
Find the animations an interface doesn't need and remove them — motion on keyboard actions, high-frequency surfaces, functional data, and decoration with no purpose — then clean up what they leave behind. Edits code, but only to subtract; it never adds or retunes motion. Use when the user says the app "feels slow", "has too much animation", "feels over-animated", wants to "tone down the motion", or asks what animations to remove. For finding places that should animate, use find-animation-opportunities; for fixing animations that should stay, use improve-animations or review-animations.
Also in 7 projects that use this
jtfasulo7Skillanimation-performance
Apply when building scroll-scrubbed animations, marquees, continuous SVG/canvas animations, or fixing reports of "laggy", "stuttering", "doesn't render", "disappears and reappears", "jumps". Encodes the perf rules learned from the realtor-website rebuild.
Also in 13 projects that use this
arkanSkillbreak-ui
Try to break a piece of UI by feeding it worst-case data — long names, unbreakable emails, one-letter names, missing fields, huge counts, zero items, long labels, non-Latin text, emoji, extreme numbers — then render it behind a "Demo data / Worst case" toggle and report everything that broke, with the fix for each. Use when the user asks to stress-test, break, or find edge cases in a component or screen, or to "try the worst case". For visual design critique use emil-design-eng; for motion use review-animations.
Also in 16 projects that use this
sanmidableSkillwrite-swift
Also in 16 projects that use this
- +4 more from boraoztunc
Other versions27 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 27
- emilkowalski/skill★ 57ksame name
- emilkowalski/skills★ 57ksame name
- sanity-io/sanity★ 6.4ksame name
- leepokai/Codync★ 2.1ksame name
- boraoztunc/skills★ 473same name
- swyxio/skills★ 199same name
- anis-dr/skills★ 4same name
- malinskibeniamin/skills★ 4same name
- robinbril/claude-code-harness★ 3same name
- Wanghaoyihaoyi/agent-skills★ 3same name
17 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository69 other files it gives its agents.
- AGENTS.mdAGENTS.md
- hushh-webapp/AGENTS.mdAGENTS.md
- impeccableSkill
- agent-orchestration-governanceSkill
- analytics-observability-governanceSkill
- animateSkill
- animation-vocabularySkill
- apple-designSkill
- autonomous-rca-governanceSkill
- backend-agents-operonsSkill
- backend-api-contractsSkill
- backend-runtime-governanceSkill
- backendSkill
- brandkitSkill
- client-env-paritySkill
- codex-skill-authoringSkill
- comms-communitySkill
- context-refreshSkill
- contributor-onboardingSkill
- docs-governanceSkill
- emil-design-engSkill
- find-animation-opportunitiesSkill
- founder-brief-curationSkill
- frontend-architectureSkill
- frontend-cache-coherenceSkill
- frontend-design-systemSkill
- frontend-native-surface-mapperSkill
- frontendSkill
- frontend-surface-placementSkill
- future-plannerSkill
- github-contribution-governanceSkill
- hushh-consent-mcpSkill
- hushh-icon-themeSkill
- iam-consent-governanceSkill
- imagegen-frontend-mobileSkill
- imagegen-frontend-webSkill
- improve-animationsSkill
- industrial-brutalist-uiSkill
- kai-test-account-resetSkill
- less-text-karma-jiSkill
- mcp-developer-surfaceSkill
- mobile-parity-auditSkill
- mobile-plugin-contractsSkill
- morphy-axSkill
- one-voice-governanceSkill
- oss-license-governanceSkill
- pdf-artifact-generationSkill
- pick-ui-librarySkill
- pkm-upgrade-rehearsalSkill
- planning-boardSkill
- pr-governance-reviewSkill
- profile-uiSkill
- prototypeSkill
- puppy-one-harnessSkill
- quality-contractsSkill
- release-ios-appstoreSkill
- repo-contextSkill
- repo-operationsSkill
- review-animationsSkill
- reviewer-app-testingSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.
0
Common
Most of the 27 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Avoid overlap with frontend, backend, and repo-context.
- Distinctive: line 52
Keep native registration and service-layer contracts aligned across web, iOS, and Android.
- Very specific: line 60
If the request is broad repo mapping, start with repo-context.
- Very specific: line 61
If the task becomes broad web-frontend work, route it to frontend.
“Common” is measured: kept by at least 6 in 10 of the 27 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Hussh Mobile Native Skill
Purpose and Trigger
- Primary scope:
mobile-native-intake - Trigger on broad native requests across iOS, Android, Capacitor plugins, parity, and device-specific runtime behavior.
- Avoid overlap with
frontend,backend, andrepo-context.
Coverage and Ownership
- Role:
owner - Owner family:
mobile-native
Owned repo surfaces:
hushh-webapp/ioshushh-webapp/android
Non-owned surfaces:
frontendbackenddocs-governance
Do Use
- Broad native intake before the correct spoke is clear.
- Mobile parity, plugin registration, native runtime behavior, and release-readiness questions.
- Choosing whether work belongs to plugin contracts or parity audit specialists.
Do Not Use
- Pure web-only frontend work.
- Backend-only or trust-only work without a native surface.
- Broad repo mapping before the domain itself is known.
Read First
docs/development/mobile/README.mddocs/development/guides/new-feature.mdhushh-webapp/ios/App/CapApp-SPM/README.mdhushh-webapp/docs/ios-native-surface-adoption.md
Workflow
- Decide whether the task is plugin-contract work or parity/audit work.
- Keep native registration and service-layer contracts aligned across web, iOS, and Android.
- Route trust and consent boundary questions into
security-auditwhen native is only one part of the problem. - For native chrome, follow the adoption reference's presentation qualification rules: establish feasible complete composition and one renderer per control lifetime before expanding families. A successful isolated study does not qualify the product's draft, operation or overlapping-presentation owners.
Handoff Rules
- Route plugin implementation and registration work to
mobile-plugin-contracts. - Route parity, release-readiness, and native audit work to
mobile-parity-audit. - If the request is broad repo mapping, start with
repo-context. - If the task becomes broad web-frontend work, route it to
frontend.
Required Checks
cd hushh-webapp && npm run typecheck
cd hushh-webapp && npm run cap:buildDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

