AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Ux Navigation

skill-parhamb-design-skills-navigation · by parhamb

>

No reviews yet
0 installs
4 views
0.0% view→install

Install

$ agentstack add skill-parhamb-design-skills-navigation

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-parhamb-design-skills-navigation)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Ux Navigation? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Navigation UX

Navigation is the skeleton of the app. When it is invisible and predictable, users feel in control. When it is broken or confusing, they leave.


Checklist

| Item | Guidance | |---|---| | Home accessible anywhere | Logo or home tab always returns to the root screen from anywhere in the app. | | Persistent navigation | Tab bar or bottom navigation is visible on all primary screens. | | Max 3 taps to content | Any piece of content is reachable in 3 taps or fewer from the home screen. | | Current location indicator | The active tab is highlighted. Deep screens show a breadcrumb or clear title. | | Android back button | Follows the back stack correctly. Never exits the app unexpectedly. | | Back button on every screen | Every pushed screen has a back or close button in the top-left corner. | | Logical flow | Navigation order matches the user's mental model and task sequence. | | Deep link support | Every major screen has a URI scheme or Universal Link for direct access. | | Tab bar badge counts | Unread count badges are accurate and clear when the content is viewed. | | Scroll padding | Content at the bottom is padded above the tab bar height and safe area. | | Status bar visible | Status bar is shown during normal app use. Hidden only in full-screen media. |


Navigation Patterns

Bottom tab bar (iOS): 3 to 5 items maximum. Icon and label together. Badge for notification counts. Not used for destructive actions.

Side drawer (Android): Suitable for apps with 5 or more top-level sections. Opened by a hamburger icon or a left-edge swipe. User avatar and name at the top.

Top navigation bar: Single screen title centered or left-aligned. Action icons on the right, maximum 2 visible. Back or close on the left.

Modal vs push: Push (drill-down) is for content that is part of the hierarchy. Modal (sheet or dialog) is for tasks that interrupt the main flow such as creating, editing, or confirming something. Never push where you should modal — it breaks the expected back stack behavior.

Deep linking strategy: Every major content screen should have a stable URL or URI scheme. This enables sharing, notifications, and marketing links to land users directly in the right place without going through the home screen.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.