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

mobile-parity-audit

Skill40 starsChanged 4 days agoApache-2.0View on GitHub

Use when auditing mobile/native parity, release readiness, the native route inventory report, or platform-specific coverage gates across the Hussh app.

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 6 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Avoid overlap with mobile-plugin-contracts and quality-contracts.

    line 12
  2. Distinctive:

    Start from the documented parity contract and then validate the live native surfaces.

    line 54
  3. Distinctive:

    Keep findings tied to concrete platform gaps, not generic “mobile broken” summaries.

    line 55
  4. Distinctive:

    Before physical voice or route smoke, run the static native parity gate so missing microphone permission metadata, missing route-inventory …

    line 58
  5. Distinctive:

    Keep destructive cold audits and non-destructive continuity rehearsals separate.

    line 60
  6. Distinctive:

    Start with static and host-native tests.

    line 61
  7. Very specific:

    Before physical reviewer XCUI, read references/physical-reviewer-preflight.md.

    line 62
  8. Distinctive:

    Keep installation, XCTest body entry, product interaction, visual/accessibility and Release performance receipts separate and …

    line 65
  9. Very specific:

    If the request is still broad or ambiguous, route it back to mobile-native.

    line 69
  10. Very specific:

    If the audit isolates a plugin-contract issue, use mobile-plugin-contracts.

    line 70
  11. Very specific:

    If the problem is actually broader quality or trust validation, route to quality-contracts or security-audit.

    line 71
  12. Very specific:

    Run npm run ios:cold:audit, npm run android:cold:audit, or the UI cold-audit equivalent only when the task explicitly authorizes a reset.

    line 81

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “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 Parity Audit Skill

Purpose and Trigger

  • Primary scope: mobile-parity-audit
  • Trigger on parity audits, native release-readiness checks, and platform-specific coverage or regression review.
  • Avoid overlap with mobile-plugin-contracts and quality-contracts.

Coverage and Ownership

  • Role: spoke
  • Owner family: mobile-native

Owned repo surfaces:

  1. docs/development/mobile
  2. hushh-webapp/scripts/native
  3. hushh-webapp/ios/App/AppTests
  4. hushh-webapp/ios/App/AppUITests

Non-owned surfaces:

  1. mobile-native
  2. frontend
  3. security-audit

Do Use

  1. Auditing web/iOS/Android parity and platform-specific gaps.
  2. Running native release-readiness checks and reviewing native regression risk.
  3. Confirming documented parity expectations against the current app surface.

Do Not Use

  1. Implementing plugin contracts or native bridge details directly.
  2. Broad native intake when the actual subtype is still unclear.
  3. Generic test-strategy work outside the mobile family.

Read First

  1. docs/development/mobile/README.md
  2. docs/development/mobile/capacitor-parity-audit.md
  3. docs/development/mobile/capacitor-parity-audit-report.md
  4. hushh-webapp/docs/ios-native-surface-adoption.md
  5. .agents/skills/repo-operations/references/admin-release-sop.md

Workflow

  1. Start from the documented parity contract and then validate the live native surfaces.
  2. Keep findings tied to concrete platform gaps, not generic “mobile broken” summaries.
  3. Route implementation work back into plugin-contract or owner skills after the audit isolates the issue.
  4. For generated native route audit reports, treat ok: true as advisory until the observed status also proves ready=1, found=1, and the observed marker equals the expected marker. A passed report with a missing marker is a blocker, not release evidence.
  5. Before physical voice or route smoke, run the static native parity gate so missing microphone permission metadata, missing route-inventory entries, or unclassified legacy aliases fail before device work.
  6. Any route added to ROUTES must be classified in native-route-inventory.json in the same change. Nested route families that share one workspace may share a marker, but each canonical route still needs an explicit inventory row and static-export-safe fixture.
  7. Keep destructive cold audits and non-destructive continuity rehearsals separate. Cold fixture evidence never proves an active memory-only vault or route survives background/resume.
  8. Start with static and host-native tests. A cold audit requires explicit authority, must terminate its test app on every host terminal path, and is never a default diagnosis command for a continuity failure.
  9. Before physical reviewer XCUI, read references/physical-reviewer-preflight.md; distinguish transport, device unlock, automation authorization and vault admission before supplying credentials.
  10. Qualify shared families across their authored routes with transition evidence and separate visual, touch, accessibility and privacy checks. Prepare installation separately from attach-only warm-session tests; follow the adoption reference, not repeated settled-button screenshots.
  11. Distinguish expected glass press feedback from missing/replaced controls. Compare first touch and keyboard transitions, not only settled frames; host retention is not pixel acceptance. If cross-renderer motion fails the documented fluidity standard, stop expansion instead of hiding controls or weakening the gate.
  12. Keep installation, XCTest body entry, product interaction, visual/accessibility and Release performance receipts separate and exact-build-bound. Qualification must use the real One/Puppy ports and complete History/Profile handoffs; do not transfer acceptance from a synthetic study or a recovery renderer.

Handoff Rules

  1. If the request is still broad or ambiguous, route it back to mobile-native.
  2. If the audit isolates a plugin-contract issue, use mobile-plugin-contracts.
  3. If the problem is actually broader quality or trust validation, route to quality-contracts or security-audit.

Required Checks

cd hushh-webapp && npm run verify:capacitor:static
cd hushh-webapp && ./android/gradlew -p android :app:testDebugUnitTest --no-daemon
cd hushh-webapp && xcodebuild -project ios/App/App.xcodeproj -scheme App -sdk iphonesimulator -destination 'generic/platform=iOS Simulator' -derivedDataPath ios/App/build/DerivedData build-for-testing

Run npm run ios:cold:audit, npm run android:cold:audit, or the UI cold-audit equivalent only when the task explicitly authorizes a reset. Run ios:continuity:local or android:continuity:local only for an intentional normal-session rehearsal. Keep agent-driven simulations headless. Use the explicit visible opt-in only when the user requests a desktop window.

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.