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
- peterbamuhigire/chwezi-dev-enginetheir own version, first seen Nov 15, 2026
- veegres/ivorytheir own version, first seen Nov 9, 2026
- harshitsinghbhandari/domain-expansiontheir own version, first seen Nov 8, 2026
- DnsQueen/orcinus-skillstheir own version, first seen Nov 8, 2026
- ErikaAX08/erikas-skillstheir own version, first seen Nov 8, 2026
- SWEStash/swe-workflow-skillstheir own version, first seen Nov 8, 2026
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-360Skillbackend-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
xenitV1Skillmobile-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
harrissohail6Skilldatabase-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
xenitV1Skillclean-code
Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments
Also in 3 projects that use this
AnthropicSkillarchitecture
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
JetBrainsSkillwebapp-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
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- vudovn/ag-kit★ 8.2ksame name
- vudovn/antigravity-kit★ 8.2ksame name
- veegres/ivory★ 282same name
- nimadorostkar/Claude-Skills-collection★ 37same name
- peterbamuhigire/chwezi-dev-engine★ 31same name
- microsoft/FSQ★ 23same name
- stareezy-1/frontend-architecture-skill★ 10same name
- ErikaAX08/erikas-skills★ 6same name
- DnsQueen/orcinus-skills★ 3same name
- harshitsinghbhandari/domain-expansion★ 2same name
6 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
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-cache-coherenceSkill
- frontend-design-systemSkill
- frontend-native-surface-mapperSkill
- 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
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
- Very specific: line 12
Avoid overlap with frontend-design-system and frontend-surface-placement.
- Distinctive: line 56
Keep CI and local package verification aligned when adding or changing frontend rules.
- Distinctive: line 58
Keep signed-in route families covered by the contract-driven browser sweep.
- Very specific: line 60
Keep Playwright baseURL, webServer.url, and the dev-server port in one configuration path so local browser proof does not silently wait on …
- Very specific: line 67
If the request is still broad or ambiguous, route it back to frontend.
- Very specific: line 68
If the task is shared visual-system ownership, use frontend-design-system.
- Very specific: line 69
If the task is deciding where code belongs between layers, use frontend-surface-placement.
- Very specific: line 70
If the task begins as a cross-domain scan, start with repo-context.
“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.
Files
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-systemandfrontend-surface-placement.
Coverage and Ownership
- Role:
spoke - Owner family:
frontend
Owned repo surfaces:
hushh-webapp/lib/navigationhushh-webapp/scripts/architecturehushh-webapp/package.jsondocs/development/contracts/route-contracts.md
Non-owned surfaces:
frontendmobile-nativedocs-governance
Do Use
- Route-container and route-contract work.
- Frontend package-script and verification ownership changes.
- Shared frontend structure and governance decisions affecting multiple routes or folders.
Do Not Use
- Broad frontend intake where the correct spoke is still unclear.
- Purely visual design-system work where structure is not changing.
- Native-only plugin or parity work.
Read First
hushh-webapp/package.jsonscripts/ci/web-check.shdocs/operations/releases/ci.mddocs/development/quality/frontend-ui-architecture-map.mddocs/development/contracts/route-contracts.mddocs/development/contracts/ui-contract-contributor-guide.md
Workflow
- 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:doctorbefore UI edits; review Back cases and Search actions, then generate withnpm run build:ui-contractsand verify withnpm run verify:ui-contracts. - Keep CI and local package verification aligned when adding or changing frontend rules.
- Centralize route-container behavior in
AppPageShellorFullscreenFlowShell; signed-in routes useAppPageHeaderRegion/PageHeaderrather than route-local hero or logo chrome. - Keep signed-in route families covered by the contract-driven browser sweep.
- 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. - 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. - 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. - 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.
- 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
- If the request is still broad or ambiguous, route it back to
frontend. - If the task is shared visual-system ownership, use
frontend-design-system. - If the task is deciding where code belongs between layers, use
frontend-surface-placement. - 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:doctorDoes 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.

