Use when deciding whether frontend code belongs in Morphy UX, app-ui, or a feature folder inside the frontend owner family.
Resources
1Install
npx skillscat add hushh-labs/hushh-research/frontend-surface-placement Install via the SkillsCat registry.
SKILL.md
Hussh Frontend Surface Placement Skill
Purpose and Trigger
- Primary scope:
frontend-surface-placement - Trigger on deciding whether frontend code belongs in Morphy UX, app-ui, a feature folder, or labs.
- Avoid overlap with
frontend-design-systemandfrontend-architecture.
Coverage and Ownership
- Role:
spoke - Owner family:
frontend
Owned repo surfaces:
hushh-webapp/components/app-uihushh-webapp/lib/morphy-uxhushh-webapp/components/kaihushh-webapp/components/ria
Non-owned surfaces:
frontendmobile-nativedocs-governance
Do Use
- File-placement and layer-ownership decisions for shared frontend code.
- Auditing whether a new surface should be promoted into shared UI rather than staying feature-local.
- Protecting the single card, surface, and route-container system from parallel implementations.
Do Not Use
- Broad frontend intake where the correct spoke is still unclear.
- Visual-system changes where the owning layer is already clear.
- Native plugin or route-contract work that belongs elsewhere.
Read First
hushh-webapp/lib/morphy-ux/README.mdhushh-webapp/components/app-ui/README.mddocs/reference/quality/design-system.mddocs/reference/quality/frontend-ui-architecture-map.md
Workflow
- Decide whether the change owns primitives, semantic shared surfaces, feature-local composition, or labs exploration.
- Keep primitive behavior in Morphy UX, semantic shared surfaces in app-ui, and feature mapping in feature folders.
- Promote repeated feature-local patterns into the correct shared layer instead of cloning them.
Handoff Rules
- If the request is still broad or ambiguous, route it back to
frontend. - If the task changes the visual-system rules themselves, use
frontend-design-system. - If the task changes route governance or verification ownership, use
frontend-architecture. - If the task begins as a cross-domain scan, start with
repo-context.
Required Checks
cd hushh-webapp && npm run audit:ui-surfaces
cd hushh-webapp && npm run verify:design-system
cd hushh-webapp && npm run verify:docs
cd hushh-webapp && npm run typecheck