Results for “navigation”

Visualises and validates a map's pedestrian navigation mesh by sampling walkable locations (get_random_location_from_navigation) and drawing them as debug points. Use when the user asks to "show/visualise the pedestrian navmesh", "check walkable areas", "validate pedestrian navigation after a map import", or "why won't my walkers move". Confirms the navmesh loaded and how far it covers.

The English summary is being prepared. Showing the original description.

visionOS / iOS 空間コンピューティング。RealityKit、ARKit、visionOS SwiftUI、USDKit、Spatial Preview。 Entity, ModelEntity, AnchorEntity, Component, System, RealityView, MeshResource, Material, EntityAction, MeshDeformerComponent, GaussianSplatComponent, ComputeGraphComponent, ComputeNodeGraph, PhysicsJointsComponent, ForceEffectComponent, ClothBodyComponent, NavigationComponent, NavigationMeshComponent, NavigationController, USDStage, SpatialPreviewSession, ImmersiveSpace, ImmersionStyle, WindowGroup, VolumetricWindowStyle, Model3D, ARKitSession, ARSession, ARWorldTrackingConfiguration, WorldTrackingProvider, HandTrackingProvider, ImageTrackingProvider, AccessoryTrackingProvider, CameraFrameProvider, ObjectTrackingProvider, RoomTrackingProvider, SceneReconstructionProvider。

The English summary is being prepared. Showing the original description.

When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what pages a website should have and how they connect. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema-markup.

The English summary is being prepared. Showing the original description.

Flutter state management expert with BLoC/Cubit, Riverpod, Provider, and Navigation 2.0 (GoRouter). Activate on: Flutter state management, BLoC pattern, Cubit, Riverpod, Provider, GetX, GoRouter, Flutter navigation, flutter_bloc. NOT for: React Native (use react-native-architect), SwiftUI (use swiftui-data-flow-expert), Jetpack Compose (use jetpack-compose-navigation-expert).

The English summary is being prepared. Showing the original description.

Implement WCAG 2.2 AA/AAA compliance with automated testing, keyboard navigation, screen reader support, and focus management. Activate on: accessibility audit, WCAG compliance, keyboard navigation, screen reader, aria attributes, axe-core, focus trap. NOT for: design-level accessibility review (use design-accessibility-auditor), color contrast only (use css-in-js-architect).

The English summary is being prepared. Showing the original description.

Build and review React or Next.js interfaces using practical patterns for reusable components, state management, data fetching, forms, and rendering performance. Includes keyboard navigation and focus management to support accessible interactions.

• Build reusable React components
• Review state management and data fetching
• Improve rendering performance for long lists

Build and review React and Next.js interfaces for keyboard use and screen readers, tools that read content aloud. Apply practical patterns for form labels, error messages, accessible controls, and focus movement.

• Making form labels and errors accessible
• Reviewing keyboard controls for dropdowns
• Managing focus when modals open and close

Create Angular components and services with guidance on state management, forms, and navigation. Adapt implementation choices to the project's Angular version, and check the resulting code through tests and builds.

• Starting an Angular project
• Building forms and managing state
• Setting up navigation and route access

Build complex interactive artifacts for claude.ai with React, Tailwind CSS, and shadcn/ui. Start from a configured project, develop interfaces with state management or navigation, and bundle the result into one shareable HTML file.

• Building interactive interfaces with multiple components
• Creating artifacts with state management and navigation
• Developing interfaces with shadcn/ui components

Launch GStack Browser, a visible Chromium browser controlled by an AI agent. Watch actions in a sidebar activity feed and use sidebar chat to request page navigation, clicks, form entry, and reading page content.

• Watching an AI agent operate a browser
• Requesting page navigation and form entry through sidebar chat
• Viewing browser actions during QA or design review

Open web pages, follow navigation, and check form flows in a browser. Capture screenshots at different screen sizes, compare pages before and after actions, and collect console errors, the technical messages that can reveal page problems.

• Checking navigation and form flows
• Capturing mobile, tablet, and desktop views
• Recording screenshots and console errors

Create a single HTML wireframe for a desktop dashboard using grey blocks, placeholder text bars, and crossed image boxes. Review navigation, information hierarchy, and panel placement before choosing final colors, copy, or imagery.

• Reviewing a desktop dashboard layout
• Checking navigation and information hierarchy
• Planning KPI, chart, and table placement

Prototype a documentation page in one HTML file, with navigation, an article, and a linked table of contents. Includes realistic explanatory text, command examples, code, and tables, plus layouts that adapt to narrower screens and right-to-left text.

• Prototyping an API reference page
• Designing a tutorial with commands and code
• Planning a guide with navigation and a table of contents

Create a single-screen desktop dashboard for dating, matchmaking, or community products. It combines key metrics, a community ticker, match charts, and sidebar navigation in one HTML document, using editorial typography, generous spacing, and a restrained accent color.

• Prototyping a dating service dashboard
• Designing a community activity overview
• Displaying mutual matches and match-rate trends

Present user research as a three-slide HTML deck with warm paper colors, minimalist typography, and subtle motion. Organize the research framing, participant breakdown, and behavioral evidence, with keyboard navigation and interactive donut-chart highlights.

• Summarizing user research in three slides
• Showing participant composition with a donut chart
• Presenting behavioral patterns alongside evidence

Turn presentation content into Keynote-style web slides with large headings, restrained colors, and generous spacing. Each screen shows one slide, with keyboard navigation, page counts, and fade transitions for product introductions or talks.

• Building a product introduction deck
• Preparing slides for a talk
• Presenting a chart on its own slide

Create a three-slide HTML presentation for company culture, strategy, or guiding principles. Burgundy, blush, and muted gold frame bold statements, pill-shaped tags, and eight principle cards, with button and keyboard navigation.

• Presenting company culture
• Sharing eight guiding principles
• Introducing a studio through tags

Review pagination markup so people using screen readers or keyboards can understand their current page and move between pages. Check navigation labels, current-page attributes, focusable controls, and announcements when the page changes.

• Reviewing pagination in search results
• Checking keyboard navigation between pages
• Improving screen reader labels for pagination

Create a custom offline page and configure a service worker, a browser background script, to cache it in advance. Show it when page navigation fails, and review resource dependencies and fallback conditions.

• Add an offline page to a PWA
• Guide users during connection loss
• Review offline page caching

Review page landmarks, the named regions screen reader users navigate between. The skill checks semantic HTML elements, a single main content region, and labels for repeated region types, then identifies markup changes and ways to verify them.

• Reviewing page structure for screen reader navigation
• Replacing generic containers with semantic HTML elements
• Checking labels for multiple navigation regions

Review a page to ensure it has exactly one main landmark, the region identifying its primary content. Find missing or duplicate main regions and get corrections that give assistive technology users a clear navigation target.

• Checking the main region in a page template
• Fixing duplicate main regions in combined layouts
• Reviewing navigation to primary content with a screen reader

Review HTML list structure so screen readers can identify lists and announce item counts. Find list items without valid containers, check custom accessibility roles, and guide fixes to markup used for navigation or styling.

• Review list markup split across components
• Fix navigation lists with invalid nesting
• Check parent roles for custom lists

Review web page headings for skipped levels and unclear hierarchy. Identify specific elements to adjust, explain how heading structure supports screen reader navigation, and describe how to verify the revised page with accessibility tools.

• Checking heading levels across a web page
• Reviewing heading structure in shared components
• Improving navigation through screen reader heading lists

Review rendered HTML and replace generic div elements with elements that describe their purpose, such as main, nav, and article. Clarify page structure to support screen-reader navigation, search-engine understanding, and code maintenance.

• Reviewing page structure built mostly with div elements
• Checking HTML output from templates and shared components
• Improving page structure for screen-reader navigation