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.
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
- 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-nativeSkill
- 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
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
- Very specific: line 12
Avoid overlap with frontend-architecture, mobile-parity-audit, backend-api-contracts, and one-voice-governance.
- Very specific: line 35
Before changing a route that depends on a Next.js proxy, backend endpoint family, native plugin, or voice/action contract.
- Distinctive: line 36
When mapping a screen's API calls to native transport and plugin behavior.
- Distinctive: line 37
When adding route-specific overrides to the generated surface map.
- Distinctive: line 38
When auditing whether a native iOS/Android screen still matches web route behavior.
- Very specific: line 56
Run cd hushh-webapp && npm run verify:surface-map before trusting the map.
- Very specific: line 58
If the route uses a new service, proxy, backend family, plugin, loader, header, or back-button pattern, update generate-surface-map.mjs.
- Distinctive: line 62
When a finite nested route family renders through one shared workspace, keep every route file represented in the generated surface map and …
- Very specific: line 66
If the request is still broad or ambiguous, route it back to frontend.
- Very specific: line 67
If the work is broad route/package structure, route to frontend-architecture.
- Very specific: line 68
If native parity evidence or simulator proof is needed, route to mobile-parity-audit.
- Very specific: line 69
If a Next.js proxy or backend endpoint contract changes, route to backend-api-contracts.
- Very specific: line 70
If voice/action ids, reachability, or execution policy changes, route to one-voice-governance.
- Very specific: line 71
If documentation homes or stale links are the main problem, route to docs-governance.
≈ “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.
Files
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, andone-voice-governance.
Coverage and Ownership
- Role:
spoke - Owner family:
frontend
Owned repo surfaces:
hushh-webapp/frontend-native-surface-map.generated.jsonhushh-webapp/scripts/architecture/generate-surface-map.mjsdocs/development/contracts/frontend-native-surface-map.md
Non-owned surfaces:
frontendmobile-nativebackend-api-contractsone-voice-governancedocs-governance
Do Use
- Before changing a route that depends on a Next.js proxy, backend endpoint family, native plugin, or voice/action contract.
- When mapping a screen's API calls to native transport and plugin behavior.
- When adding route-specific overrides to the generated surface map.
- When auditing whether a native iOS/Android screen still matches web route behavior.
Do Not Use
- Broad frontend structure work that belongs to
frontend-architecture. - Native plugin implementation or registration work that belongs to
mobile-plugin-contracts. - Backend route wire-shape changes that belong to
backend-api-contracts. - Voice/action gateway authoring that belongs to
one-voice-governance.
Read First
docs/development/contracts/frontend-native-surface-map.mddocs/development/contracts/route-contracts.mddocs/development/mobile/capacitor-parity-audit.mdhushh-webapp/frontend-native-surface-map.generated.json
Workflow
- Run
cd hushh-webapp && npm run verify:surface-mapbefore trusting the map. - Inspect the target route's page file, service imports,
page.voice-action-contract.json, and native inventory row. - If the route uses a new service, proxy, backend family, plugin, loader, header, or back-button pattern, update
generate-surface-map.mjs. - Regenerate the contract from
hushh-webappwithnode ./scripts/architecture/generate-surface-map.mjs. - Re-run
cd hushh-webapp && npm run verify:surface-map. - Hand off to backend, mobile, or voice skills when the map reveals a contract change outside this skill's ownership.
- 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
- If the request is still broad or ambiguous, route it back to
frontend. - If the work is broad route/package structure, route to
frontend-architecture. - If native parity evidence or simulator proof is needed, route to
mobile-parity-audit. - If a Next.js proxy or backend endpoint contract changes, route to
backend-api-contracts. - If voice/action ids, reachability, or execution policy changes, route to
one-voice-governance. - 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:docsDoes 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.

