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

frontend-surface-placement

Skill40 starsChanged 4 days agoApache-2.0View on GitHub

Use when deciding whether frontend code belongs in Morphy UX, app-ui, or a feature folder inside the frontend owner family.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 1 is distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

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

    Avoid overlap with frontend-design-system and frontend-architecture.

    line 12
  2. Distinctive:

    Keep primitive behavior in Morphy UX, semantic shared surfaces in app-ui, and feature mapping in feature folders.

    line 54
  3. Very specific:

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

    line 59
  4. Very specific:

    If the task changes the visual-system rules themselves, use frontend-design-system.

    line 60
  5. Very specific:

    If the task changes route governance or verification ownership, use frontend-architecture.

    line 61
  6. Very specific:

    If the task begins as a cross-domain scan, start with repo-context.

    line 62

≈ “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 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-system and frontend-architecture.

Coverage and Ownership

  • Role: spoke
  • Owner family: frontend

Owned repo surfaces:

  1. hushh-webapp/components/app-ui
  2. hushh-webapp/lib/morphy-ux
  3. hushh-webapp/components/kai
  4. hushh-webapp/components/ria

Non-owned surfaces:

  1. frontend
  2. mobile-native
  3. docs-governance

Do Use

  1. File-placement and layer-ownership decisions for shared frontend code.
  2. Auditing whether a new surface should be promoted into shared UI rather than staying feature-local.
  3. Protecting the single card, surface, and route-container system from parallel implementations.

Do Not Use

  1. Broad frontend intake where the correct spoke is still unclear.
  2. Visual-system changes where the owning layer is already clear.
  3. Native plugin or route-contract work that belongs elsewhere.

Read First

  1. hushh-webapp/lib/morphy-ux/README.md
  2. hushh-webapp/components/app-ui/README.md
  3. docs/development/quality/design-system.md
  4. docs/development/quality/frontend-ui-architecture-map.md

Workflow

  1. Decide whether the change owns primitives, semantic shared surfaces, feature-local composition, or labs exploration.
  2. Keep primitive behavior in Morphy UX, semantic shared surfaces in app-ui, and feature mapping in feature folders.
  3. Promote repeated feature-local patterns into the correct shared layer instead of cloning them.

Handoff Rules

  1. If the request is still broad or ambiguous, route it back to frontend.
  2. If the task changes the visual-system rules themselves, use frontend-design-system.
  3. If the task changes route governance or verification ownership, use frontend-architecture.
  4. 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

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.