agentleFS
hushh-labshushh-labs/hushh-research/.agents/skills/frontend-native-surface-mapper/SKILL.md

frontend-native-surface-mapper

Skill40 starsChanged 3 days agoApache-2.0View on GitHub

Use when regenerating or auditing the frontend surface map that joins app routes, page files, Next.js API proxies, backend endpoint families, native transport, Capacitor plugins, and voice/action contracts.

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. About 0 are common, 4 are distinctive, and 10 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 10

    Very specific

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

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

    Avoid overlap with frontend-architecture, mobile-parity-audit, backend-api-contracts, and one-voice-governance.

    line 12
  2. Very specific:

    Before changing a route that depends on a Next.js proxy, backend endpoint family, native plugin, or voice/action contract.

    line 35
  3. Distinctive:

    When mapping a screen's API calls to native transport and plugin behavior.

    line 36
  4. Distinctive:

    When adding route-specific overrides to the generated surface map.

    line 37
  5. Distinctive:

    When auditing whether a native iOS/Android screen still matches web route behavior.

    line 38
  6. Very specific:

    Run cd hushh-webapp && npm run verify:surface-map before trusting the map.

    line 56
  7. Very specific:

    If the route uses a new service, proxy, backend family, plugin, loader, header, or back-button pattern, update generate-surface-map.mjs.

    line 58
  8. Distinctive:

    When a finite nested route family renders through one shared workspace, keep every route file represented in the generated surface map and …

    line 62
  9. Very specific:

    If the request is still broad or ambiguous, route it back to frontend.

    line 66
  10. Very specific:

    If the work is broad route/package structure, route to frontend-architecture.

    line 67
  11. Very specific:

    If native parity evidence or simulator proof is needed, route to mobile-parity-audit.

    line 68
  12. Very specific:

    If a Next.js proxy or backend endpoint contract changes, route to backend-api-contracts.

    line 69
  13. Very specific:

    If voice/action ids, reachability, or execution policy changes, route to one-voice-governance.

    line 70
  14. Very specific:

    If documentation homes or stale links are the main problem, route to docs-governance.

    line 71

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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 Frontend Native Surface Mapper Skill

Purpose and Trigger

  • Primary scope: frontend-native-surface-map
  • Trigger on route-to-API/native/plugin/voice mapping, screen parity audits, Next.js server API dependency mapping, and generated surface-map contract changes.
  • Avoid overlap with frontend-architecture, mobile-parity-audit, backend-api-contracts, and one-voice-governance.

Coverage and Ownership

  • Role: spoke
  • Owner family: frontend

Owned repo surfaces:

  1. hushh-webapp/frontend-native-surface-map.generated.json
  2. hushh-webapp/scripts/architecture/generate-surface-map.mjs
  3. docs/development/contracts/frontend-native-surface-map.md

Non-owned surfaces:

  1. frontend
  2. mobile-native
  3. backend-api-contracts
  4. one-voice-governance
  5. docs-governance

Do Use

  1. Before changing a route that depends on a Next.js proxy, backend endpoint family, native plugin, or voice/action contract.
  2. When mapping a screen's API calls to native transport and plugin behavior.
  3. When adding route-specific overrides to the generated surface map.
  4. When auditing whether a native iOS/Android screen still matches web route behavior.

Do Not Use

  1. Broad frontend structure work that belongs to frontend-architecture.
  2. Native plugin implementation or registration work that belongs to mobile-plugin-contracts.
  3. Backend route wire-shape changes that belong to backend-api-contracts.
  4. Voice/action gateway authoring that belongs to one-voice-governance.

Read First

  1. docs/development/contracts/frontend-native-surface-map.md
  2. docs/development/contracts/route-contracts.md
  3. docs/development/mobile/capacitor-parity-audit.md
  4. hushh-webapp/frontend-native-surface-map.generated.json

Workflow

  1. Run cd hushh-webapp && npm run verify:surface-map before trusting the map.
  2. Inspect the target route's page file, service imports, page.voice-action-contract.json, and native inventory row.
  3. If the route uses a new service, proxy, backend family, plugin, loader, header, or back-button pattern, update generate-surface-map.mjs.
  4. Regenerate the contract from hushh-webapp with node ./scripts/architecture/generate-surface-map.mjs.
  5. Re-run cd hushh-webapp && npm run verify:surface-map.
  6. Hand off to backend, mobile, or voice skills when the map reveals a contract change outside this skill's ownership.
  7. When a finite nested route family renders through one shared workspace, keep every route file represented in the generated surface map and native route inventory instead of relying on only the parent route.

Handoff Rules

  1. If the request is still broad or ambiguous, route it back to frontend.
  2. If the work is broad route/package structure, route to frontend-architecture.
  3. If native parity evidence or simulator proof is needed, route to mobile-parity-audit.
  4. If a Next.js proxy or backend endpoint contract changes, route to backend-api-contracts.
  5. If voice/action ids, reachability, or execution policy changes, route to one-voice-governance.
  6. If documentation homes or stale links are the main problem, route to docs-governance.

Required Checks

cd hushh-webapp && npm run verify:surface-map
cd hushh-webapp && npm run verify:capacitor:static
cd hushh-webapp && npm run verify:docs

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.