agentleFS
hushh-labshushh-labs/hushh-research/.agents/skills/mobile-native/SKILL.md

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

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.
  • emilkowalskiSkill

    ask-emil

    Ask which skill or flow fits your situation. A router over the skills in this repo.

    Also in 4 projects that use this

  • boraoztuncSkill

    choreograph

    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

  • boraoztuncSkill

    remove-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

  • jtfasulo7Skill

    animation-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

  • arkanSkill

    break-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

  • sanmidableSkill

    write-swift

    Also in 16 projects that use this

  • +4 more from boraoztunc

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
  1. Very specific:

    Avoid overlap with frontend, backend, and repo-context.

    line 12
  2. Distinctive:

    Keep native registration and service-layer contracts aligned across web, iOS, and Android.

    line 52
  3. Very specific:

    If the request is broad repo mapping, start with repo-context.

    line 60
  4. Very specific:

    If the task becomes broad web-frontend work, route it to frontend.

    line 61

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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, and repo-context.

Coverage and Ownership

  • Role: owner
  • Owner family: mobile-native

Owned repo surfaces:

  1. hushh-webapp/ios
  2. hushh-webapp/android

Non-owned surfaces:

  1. frontend
  2. backend
  3. docs-governance

Do Use

  1. Broad native intake before the correct spoke is clear.
  2. Mobile parity, plugin registration, native runtime behavior, and release-readiness questions.
  3. Choosing whether work belongs to plugin contracts or parity audit specialists.

Do Not Use

  1. Pure web-only frontend work.
  2. Backend-only or trust-only work without a native surface.
  3. Broad repo mapping before the domain itself is known.

Read First

  1. docs/development/mobile/README.md
  2. docs/development/guides/new-feature.md
  3. hushh-webapp/ios/App/CapApp-SPM/README.md
  4. hushh-webapp/docs/ios-native-surface-adoption.md

Workflow

  1. Decide whether the task is plugin-contract work or parity/audit work.
  2. Keep native registration and service-layer contracts aligned across web, iOS, and Android.
  3. Route trust and consent boundary questions into security-audit when native is only one part of the problem.
  4. 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

  1. Route plugin implementation and registration work to mobile-plugin-contracts.
  2. Route parity, release-readiness, and native audit work to mobile-parity-audit.
  3. If the request is broad repo mapping, start with repo-context.
  4. 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:build

Download now (ZIP)

Does 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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.