app-shell
/app-shell
App shell, navigation, layouts, breadcrumbs, deep links, 404/empty routes. Use when building dashboard shells, side nav, top nav, multi-page flows, "routing", "layout app", "404", or information architecture for web apps. Requires modern chrome: logo, topbar theme icon, avatar→account menu, custom filter selects — not a bare settings page or native OS selects.
- Author
- sukirman1901 ↗
- Repository
- frontend-expert ↗
- Licence
- MIT
- Last repository change
- 18.09.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 18.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
App shell, navigation, layouts, breadcrumbs, deep links, 404/empty routes. Use when building dashboard shells, side nav, top nav, multi-page flows, "routing", "layout app", "404", or information architecture for web apps. Requires modern chrome: logo, topbar theme icon, avatar→account menu, custom filter selects — not a bare settings page or native OS selects.
Triggers from the description
Original author description
App shell, navigation, layouts, breadcrumbs, deep links, 404/empty routes. Use when building dashboard shells, side nav, top nav, multi-page flows, "routing", "layout app", "404", or information architecture for web apps. Requires modern chrome: logo, topbar theme icon, avatar→account menu, custom filter selects — not a bare settings page or native OS selects.
How it works
- Overview
- When to use
- Workflow
- Checklist
- Anti-patterns (fail / High)
- Depth
SKILL.md preview
--- name: app-shell description: >- App shell, navigation, layouts, breadcrumbs, deep links, 404/empty routes. Use when building dashboard shells, side nav, top nav, multi-page flows, "routing", "layout app", "404", or information architecture for web apps. Requires modern chrome: logo, topbar theme icon, avatar→account menu, custom filter selects — not a bare settings page or native OS selects. --- # App Shell & Routing ## Overview Define **where the user is** and **how they move**. Shell (chrome) stays stable; page content swaps. Match **modern SaaS dashboard** chrome — not a blank header with only text brand. ## When to use - New app layout, dashboard shell, marketing+app split - Nav IA, breadcrumbs, nested routes, 404/unauthorized - Settings / admin pages (still need full shell) ## Workflow 1. **Shell chrome (MUST for product/dashboard UI)** - **Logo** — real mark (SVG/img), not a letter in a box alone - **Brand name** visible next to logo (can truncate on tiny widths) - **Utilities** — at least 1–2 of: search, notifications, help (icon buttons OK) - **Theme** — if light/dark exists, put it in **topbar utilities** as an **icon toggle** (moon/sun). Do **not** park a labeled “Dark mode” button in the sidebar footer - **Profile** — **avatar-only** control in the topbar at **all** breakpoints; name/email live in an **account dropdown** on click — never `display:none` the whole account control on mobile; do **not** spill name/email into the header chrome by default - Anatomy: `brand · (optional primary nav) · utilities (theme/help/bell) · avatar menu` 2. **Sidebar** - Desktop: persistent rail; support **collapse → icon-only** (≥768) - Prefer **auto-collapse** near tablet / narrow desktop; remember preference when useful - Mobile: **overlay drawer + backdrop** (not push-down accordion under the header) — see `responsive` - Sidebar is for **nav**, not theme/account chrome 3. **IA** — primary nav ≤7 items; nest the rest; active state clear 4. **Routing** — URLs reflect location; filters in query when shareable 5. **Fallbacks** — 404, empty route, unauthorized → clear CTA 6. **Motion** — load `motion` for shell/drawer/section enter (light defaults) ## Checklist - [ ] Logo mark + brand (not letter-only placeholder as the final chrome) - [ ] Theme toggle in topbar utilities (if theming) — not sidebar footer - [ ] Avatar-only profile → account dropdown (name/email inside menu) - [ ] Utility cluster present (or explicit waiver: minimal tool) - [ ] Sidebar collapse (desktop) + drawer+backdrop (mobile) - [ ] Main landmark; active nav indication - [ ] 404 / empty route handled when multi-route - [ ] Icons via Reicon (or project lib) on nav items ## Anti-patterns (fail / High) - Header = brand text only, no logo/utilities/profile - Theme as a full-width labeled button under the sidebar nav - Name + email always visible in the topbar (use avatar + menu instead) - Hiding profile entirely below a breakpoint - Mobile nav that pushes content down while burger stays visible as a second competing control - Sidebar that never collapses on mid-width dashboards ## Depth `references/app-shell.md`. Drawer rules: `references/responsive.md`. Optional local sandbox: `test/` (gitignored; not shipped).
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · sukirman1901/frontend-expert | 90 | MIT |
| tykimos/agent-native-agent | 100 | AGPL-3.0 |
| dembrandt/dembrandt-skills | 90 | MIT |
Database snapshot: 13.11.2026 · package version 71c5fe5bed79 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100contributor-docs-nav
Run the CONTRIBUTOR-DOCS nav script to update breadcrumbs and TOCs, and handle link verification. Use when updating contributor docs structure, regenerating navigation, or fixing broken links. - 100hide-show-shell
MUST be used when a Flows/Fusion app needs full-screen "app-only" mode — hiding the Fusion sidebar and topbar so the app gets the whole viewport, and giving users a clear way to bring the shell back. Triggers: hideShell, full screen app, fullscreen mode, hide sidebar, hide… - 100migrate-breadcrumb-list
Migrates legacy page-navigation breadcrumbs to @sentry/scraps/breadcrumbList and the required typed title on TopBar.Slot name="breadcrumbs". Use for "migrate breadcrumbs", "replace sentry/components/breadcrumbs", "BreadcrumbList.Title", duplicate page titles, or preserving page… - 100portal-navigation-audit
Audit and improve portal navigation, route organization, and page hierarchy for complex web apps. Use when evaluating top nav, sub nav, workspace chrome, page grouping, information architecture, menu overlap, or when planning a scalable navigation model for future growth. - 100sb-flows
Map the whole app — routes, navigation edges, and persistent nav chrome, not just a screen list. Use for 'map the app', 'show the flow', 'app map', 'audit navigation', or 'how do screens connect'. - 90flutter-core:flutter-navigation-routing
Expert guidance on implementing navigation and routing in Flutter applications with declarative routing patterns, GoRouter integration, deep linking, route guards, and complex navigation flows. Use when implementing navigation, setting up routing, or handling deep links.