syncfusion-react-appbar
Create responsive navigation headers with AppBar component. Build top, bottom, or sticky app bars with buttons, menus, icons, and sidebars. Use when building navigation elements, toolbars, action bars, or responsive headers with dynamic content layout. Includes color modes (Light, Dark, Primary, Inherit), size modes (Regular, Prominent, Dense), spacing, separators, and full accessibility support.
What this skill does
# Implementing Syncfusion React AppBar
The AppBar component creates flexible navigation headers and toolbars at the top or bottom of your application. It's used to display branding, screen titles, navigation controls, and actions while supporting responsive layouts, multiple positioning modes, and rich styling options.
## When to Use This Skill
Use AppBar when you need to:
- Display application branding and navigation at the top/bottom of pages
- Create action bars with buttons, menus, or dropdowns
- Build responsive toolbars that adapt to screen size
- Implement sticky/fixed navigation that stays visible while scrolling
- Create responsive sidebars with menu navigation
- Add visual separation between grouped controls
- Support accessibility standards (WCAG 2.2, Section 508, keyboard navigation)
## Documentation and Navigation Guide
### Getting Started
๐ **Read:** [references/getting-started.md](references/getting-started.md)
- Package installation and dependencies
- React setup (Vite and Create React App)
- CSS imports and theme configuration
- Basic AppBar with buttons and icons
- First working example
### Positioning and Layout
๐ **Read:** [references/positioning-and-layout.md](references/positioning-and-layout.md)
- Position modes: Top (default), Bottom, Sticky
- Spacer for horizontal content spacing
- Separator for visual grouping
- Media queries for responsive design
- Layout patterns for different screen sizes
### Size and Color Modes
๐ **Read:** [references/size-and-color-modes.md](references/size-and-color-modes.md)
- Mode property: Regular, Prominent, Dense
- ColorMode property: Light, Dark, Primary, Inherit
- When to use each mode combination
- Height customization for prominent AppBars
- Visual hierarchy with color modes
### Design Patterns
๐ **Read:** [references/design-patterns.md](references/design-patterns.md)
- AppBar with Menu component integration
- AppBar with Button and DropDownButton
- AppBar with Sidebar for responsive navigation
- Navigation and branding patterns
- e-inherit CSS class usage
- Responsive sidebar with TreeView
### Styling and Accessibility
๐ **Read:** [references/styling-and-accessibility.md](references/styling-and-accessibility.md)
- CSS customization with cssClass property
- HTML attributes and aria-label
- CSS class reference (.e-appbar, .e-prominent, etc.)
- WCAG 2.2 and Section 508 compliance
- Keyboard navigation support
- RTL, color contrast, and mobile support
### API Reference
๐ **Read:** [references/api-reference.md](references/api-reference.md)
- Complete property documentation (colorMode, mode, position, isSticky, cssClass, htmlAttributes, enableRtl, enablePersistence, locale)
- Event documentation (created, destroyed)
- Working code examples for every property
- Event handler examples
- Common property combinations
- Summary table of all APIs
## Quick Start
```tsx
import { AppBarComponent } from "@syncfusion/ej2-react-navigations";
import { ButtonComponent } from '@syncfusion/ej2-react-buttons';
import * as React from "react";
const App = () => {
return (
<AppBarComponent colorMode="Primary">
<ButtonComponent cssClass='e-inherit menu' iconCss='e-icons e-menu'></ButtonComponent>
<span className="regular">My App</span>
<div className="e-appbar-spacer"></div>
<ButtonComponent cssClass='e-inherit login'>Login</ButtonComponent>
</AppBarComponent>
);
}
export default App;
```
## Common Patterns
### Pattern 1: Basic Navigation Bar
```tsx
<AppBarComponent colorMode="Primary">
<ButtonComponent cssClass="e-inherit" iconCss="e-icons e-menu"></ButtonComponent>
<ButtonComponent cssClass="e-inherit">Home</ButtonComponent>
<ButtonComponent cssClass="e-inherit">About</ButtonComponent>
<div className="e-appbar-spacer"></div>
<ButtonComponent cssClass="e-inherit">Contact</ButtonComponent>
</AppBarComponent>
```
### Pattern 2: Prominent AppBar with Title
```tsx
<AppBarComponent colorMode="Primary" mode="Prominent" cssClass="prominent-appbar">
<ButtonComponent cssClass="e-inherit" iconCss="e-icons e-menu"></ButtonComponent>
<span className="prominent">Large Title Section</span>
<div className="e-appbar-spacer"></div>
<ButtonComponent cssClass="e-inherit">Action</ButtonComponent>
</AppBarComponent>
```
### Pattern 3: Dense Toolbar
```tsx
<AppBarComponent colorMode="Dark" mode="Dense">
<ButtonComponent cssClass="e-inherit" iconCss="e-icons e-cut"></ButtonComponent>
<ButtonComponent cssClass="e-inherit" iconCss="e-icons e-copy"></ButtonComponent>
<ButtonComponent cssClass="e-inherit" iconCss="e-icons e-paste"></ButtonComponent>
<div className="e-appbar-separator"></div>
<ButtonComponent cssClass="e-inherit" iconCss="e-icons e-bold"></ButtonComponent>
</AppBarComponent>
```
### Pattern 4: Sticky AppBar with Bottom Position
```tsx
<AppBarComponent colorMode="Primary" isSticky position="Bottom">
<div className="e-appbar-spacer"></div>
<ButtonComponent cssClass="e-inherit">Save</ButtonComponent>
<ButtonComponent cssClass="e-inherit">Cancel</ButtonComponent>
</AppBarComponent>
```
## Key Props
Quick reference for the most commonly used AppBar properties:
| Prop | Type | Default | Purpose |
|------|------|---------|---------|
| `colorMode` | string | `"Light"` | Color scheme: Light, Dark, Primary, Inherit |
| `mode` | string | `"Regular"` | Size mode: Regular, Prominent, Dense |
| `position` | string | `"Top"` | Vertical position: Top, Bottom |
| `isSticky` | boolean | `false` | Stick to viewport while scrolling |
| `cssClass` | string | - | Custom CSS classes for styling |
| `htmlAttributes` | Record | `{}` | HTML attributes (aria-label, data-*, etc.) |
| `enableRtl` | boolean | `false` | Enable right-to-left direction |
| `enablePersistence` | boolean | `false` | Persist state between reloads |
| `locale` | string | `"en-US"` | Language and culture settings |
**For detailed explanations and code examples for all properties, events, and methods, see the [API Reference](references/api-reference.md).**
## Common Use Cases
**Use Case 1: E-commerce Product Page**
- Primary AppBar at top with brand logo and search
- Navigation buttons (Home, Products, About)
- Right-aligned user account and cart icons
- Sticky so it stays visible when scrolling products
**Use Case 2: Admin Dashboard**
- Dark AppBar with application name
- Left sidebar toggle button (e-menu icon)
- Center spacer for balance
- Right-aligned user profile and logout
**Use Case 3: Mobile-First App**
- Responsive menu button (hidden on desktop)
- Dense mode to save screen space
- Bottom AppBar with action buttons on mobile
- Top AppBar on desktop with full navigation
**Use Case 4: Document Editor**
- Dense AppBar with editing tools (cut, copy, paste)
- Separators to group related buttons
- Undo/Redo on left, Format options on right
- Sticky while editing document
---
**Next Steps:** Choose a reference file above based on your specific task. For example, if you're getting started, read "Getting Started". If you need to position the AppBar, read "Positioning and Layout".
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context โ no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes โ information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development โ guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.