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

frontend-architecture

Skill40 starsChanged 4 days agoApache-2.0View on GitHub

Use when changing Hussh frontend structure, route contracts, package-level conventions, or frontend verification ownership.

16 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use backend-architecture, mobile-design and 6 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • GoldenWing-360Skill

    backend-architecture

    Design backends that survive redeploys, server reboots, and modest scaling. Covers stateless application servers, state placement (object storage, managed databases, Redis), immutable deploy artifacts, health checks, graceful shutdown, database migrations that don't lock the world, and the twelve-factor baseline. Invoke when designing a new backend, when uploads disappear after a redeploy, or when productionizing a vibe-coded prototype.

    Also in 3 projects that use this

  • xenitV1Skill

    mobile-design

    Mobile-first design thinking and decision-making for iOS and Android apps. Touch interaction, performance patterns, platform conventions. Teaches principles, not fixed values. Use when building React Native, Flutter, or native mobile apps.

    Also in 3 projects that use this

  • harrissohail6Skill

    database-design

    Database schema design and SQL best practices. Use when designing tables, writing queries, or optimizing database performance.

    Also in 3 projects that use this

  • xenitV1Skill

    clean-code

    Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments

    Also in 3 projects that use this

  • AnthropicSkill

    architecture

    Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.

    Also in 3 projects that use this

  • JetBrainsSkill

    webapp-testing

    Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 2 are distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 2

    Distinctive

    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 frontend-design-system and frontend-surface-placement.

    line 12
  2. Distinctive:

    Keep CI and local package verification aligned when adding or changing frontend rules.

    line 56
  3. Distinctive:

    Keep signed-in route families covered by the contract-driven browser sweep.

    line 58
  4. Very specific:

    Keep Playwright baseURL, webServer.url, and the dev-server port in one configuration path so local browser proof does not silently wait on …

    line 60
  5. Very specific:

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

    line 67
  6. Very specific:

    If the task is shared visual-system ownership, use frontend-design-system.

    line 68
  7. Very specific:

    If the task is deciding where code belongs between layers, use frontend-surface-placement.

    line 69
  8. Very specific:

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

    line 70

“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “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 Architecture Skill

Purpose and Trigger

  • Primary scope: frontend-architecture
  • Trigger on frontend structure, route contracts, package conventions, shared frontend governance rules, and verification ownership.
  • Avoid overlap with frontend-design-system and frontend-surface-placement.

Coverage and Ownership

  • Role: spoke
  • Owner family: frontend

Owned repo surfaces:

  1. hushh-webapp/lib/navigation
  2. hushh-webapp/scripts/architecture
  3. hushh-webapp/package.json
  4. docs/development/contracts/route-contracts.md

Non-owned surfaces:

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

Do Use

  1. Route-container and route-contract work.
  2. Frontend package-script and verification ownership changes.
  3. Shared frontend structure and governance decisions affecting multiple routes or folders.

Do Not Use

  1. Broad frontend intake where the correct spoke is still unclear.
  2. Purely visual design-system work where structure is not changing.
  3. Native-only plugin or parity work.

Read First

  1. hushh-webapp/package.json
  2. scripts/ci/web-check.sh
  3. docs/operations/releases/ci.md
  4. docs/development/quality/frontend-ui-architecture-map.md
  5. docs/development/contracts/route-contracts.md
  6. docs/development/contracts/ui-contract-contributor-guide.md

Workflow

  1. Inspect current package scripts, route contracts, and frontend docs before changing structure. Read the UI contributor scaffold and run cd hushh-webapp && npm run ui:doctor before UI edits; review Back cases and Search actions, then generate with npm run build:ui-contracts and verify with npm run verify:ui-contracts.
  2. Keep CI and local package verification aligned when adding or changing frontend rules.
  3. Centralize route-container behavior in AppPageShell or FullscreenFlowShell; signed-in routes use AppPageHeaderRegion/PageHeader rather than route-local hero or logo chrome.
  4. Keep signed-in route families covered by the contract-driven browser sweep.
  5. When adding Playwright route coverage, distinguish cold-entry checks from Next.js client navigation checks. Browser tests that assert memory, vault, cache, or provider continuity must run as a sequential UI-navigation lane through shell controls with a same-document navigation probe, or use the signed-in route sweep; page.goto(...) alone is cold-entry evidence.
  6. Keep Playwright baseURL, webServer.url, and the dev-server port in one configuration path so local browser proof does not silently wait on a different origin than the one being tested.
  7. For every added, renamed, or split app route, run the route contract cascade in one change: ROUTES, route builders, breadcrumbs, bottom-nav/sign-in coverage, route layout contract, generated surface map, cache manifest, voice action reachability, native inventory, docs, and focused route tests.
  8. Durable workspace panels should use finite nested routes when the route set is bounded. Keep query params for transient state, OAuth/redirects, filters/pagination, and static-export-sensitive identifiers.
  9. For a frontend runtime or bundle failure, reproduce it on the affected route and shipped engine, isolate the route/state/build boundary, fix the cause, then keep one focused regression. A working dev-server fallback does not prove the production or native bundle. Follow Toss's diagnose/reproduce/fix/prevent loop without copying its tooling into this repo.

Handoff Rules

  1. If the request is still broad or ambiguous, route it back to frontend.
  2. If the task is shared visual-system ownership, use frontend-design-system.
  3. If the task is deciding where code belongs between layers, use frontend-surface-placement.
  4. If the task begins as a cross-domain scan, start with repo-context.

Required Checks

cd hushh-webapp && npm run verify:docs
cd hushh-webapp && npm run typecheck
cd hushh-webapp && npm run verify:routes
cd hushh-webapp && npm run ui:doctor

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.