syncfusion-blazor-stepper
Implement the Syncfusion Blazor Stepper component for multi-step workflows. Use this skill when creating step-by-step navigation UI, wizards, form workflows, or progress tracking. This skill covers step-based navigation, wizard interfaces, step validation, animations, templates, and stepper customization in Blazor applications.
What this skill does
# Implementing the Syncfusion Blazor Stepper Component
The Blazor Stepper component provides an intuitive way to guide users through multi-step processes. It displays progress across numbered or labeled steps, supporting linear and non-linear workflows with customizable animations, templates, and validation states.
## When to Use This Skill
Use the Stepper component when you need to:
- Create multi-step wizards or workflows
- Display progress through sequential tasks
- Build step-by-step forms with validation
- Implement checklist-style navigation
- Guide users through onboarding processes
- Show optional vs. required steps
- Validate step completion before progression
## Component Overview
The Stepper displays steps in a horizontal or vertical layout with configurable indicators, labels, and templates. Each step can be customized with:
- **Visual states**: Not started, in progress, completed, error
- **Labels and icons**: Custom text and CSS icon classes
- **Validation**: Success or error indicators
- **Templates**: Custom content for advanced layouts
- **Animations**: Smooth transitions between steps
## Documentation and Navigation Guide
### API Reference
π **Read:** [references/api-reference.md](references/api-reference.md)
- Complete API documentation for all properties, methods, and events
- Component and property definitions with direct links to implementation guides
- Event arguments reference and enumeration types
- Complete component hierarchy (SfStepper, StepperStep, StepperAnimationSettings)
### Getting Started
π **Read:** [references/getting-started.md](references/getting-started.md)
- Installation and package setup for Blazor WebAssembly and Blazor Web App
- Service registration and namespace imports
- Basic Stepper implementation with icons and labels
- Interactive render modes for modern Web Apps
- Theme configuration and CSS imports
### Step Types and Configuration
π **Read:** [references/step-types.md](references/step-types.md)
- Step type variations (Default, Label, Indicator)
- Label positioning (Top, Bottom, Start, End)
- Step properties and attributes
- Optional and disabled steps
- Linear vs. non-linear workflows
- Step status management
### Events and Interactions
π **Read:** [references/events.md](references/events.md)
- Event handlers and lifecycle (Created, StepChanged, StepChanging, StepClicked, StepRendered)
- Event arguments and parameters
- Common event patterns
- Handling step progression and validation
### Templates and Customization
π **Read:** [references/templates-and-styling.md](references/templates-and-styling.md)
- Custom step templates
- Template context and properties
- CSS styling and customization
- CssClass property for individual steps
- Theme customization and appearance
### Advanced Features
π **Read:** [references/advanced-features.md](references/advanced-features.md)
- Step validation (IsValid property and validation states)
- Validation workflow implementation
- Tooltip support (ShowTooltip property and custom templates)
- Step content templates and custom layouts
- Step completion tracking and error handling
- Conditional step display patterns
### Animations and Globalization
π **Read:** [references/animations-and-globalization.md](references/animations-and-globalization.md)
- Animation settings (Duration and Delay)
- Enabling/disabling animations
- Localization support
- RTL (Right-to-Left) support
- Multi-language configuration
### Orientations and Layouts
π **Read:** [references/orientations-and-layouts.md](references/orientations-and-layouts.md)
- Horizontal orientation (default)
- Vertical orientation
- Linear flow with sequential progression
- Non-linear flow with free navigation
- Responsive design patterns
- Mobile and desktop layout considerations
## Quick Start Example
```csharp
@using Syncfusion.Blazor.Navigations
<SfStepper>
<StepperSteps>
<StepperStep Label="Cart" IconCss="sf-icon-cart"></StepperStep>
<StepperStep Label="Address" IconCss="sf-icon-transport"></StepperStep>
<StepperStep Label="Payment" IconCss="sf-icon-payment"></StepperStep>
<StepperStep Label="Ordered" IconCss="sf-icon-success"></StepperStep>
</StepperSteps>
</SfStepper>
```
## Common Patterns
### Linear Workflow
Use the `Linear` property to enforce sequential progressionβusers can only move to the next step after completing the current one.
```csharp
<SfStepper Linear="true">
<!-- Steps -->
</SfStepper>
```
### Active Step Control
Set the `ActiveStep` property to control which step is currently active (0-indexed).
```csharp
<SfStepper ActiveStep="1">
<!-- Steps -->
</SfStepper>
```
### Tracking Step Changes
Handle the `StepChanged` event to respond when users navigate between steps.
```csharp
<SfStepper StepChanged="@OnStepChanged">
<!-- Steps -->
</SfStepper>
@code {
private void OnStepChanged(StepperChangedEventArgs args)
{
// Handle step change
}
}
```
### Validation States
Display success or error states using the `IsValid` property on individual steps.
```csharp
<StepperStep Label="Payment" IsValid="true"></StepperStep>
<StepperStep Label="Confirm" IsValid="false"></StepperStep>
```
## Key Properties
| Property | Type | Purpose |
|----------|------|---------|
| `ActiveStep` | `int` | Sets the currently active step (0-indexed) |
| `LinearFlow` | `bool` | Enforces sequential step progression |
| `ReadOnly` | `bool` | Disables user interaction with the stepper |
| `StepType` | `StepperType` | Display format (Default, Label, Indicator) |
| `Orientation` | `StepperOrientation` | Layout direction (Horizontal, Vertical) |
| `LabelPosition` | `StepperLabelPosition` | Label placement (Top, Bottom, Start, End) |
**Step Properties:**
- `Label`: Display text for the step
- `Text`: Alternative text content
- `IconCss`: CSS class for custom icons
- `Disabled`: Prevents interaction with the step
- `Optional`: Marks step as optional
- `IsValid`: Sets validation state (true/false/null)
- `Status`: Current state (NotStarted, InProgress, Completed)
- `CssClass`: Custom CSS class for styling
## Common Use Cases
**Checkout Flow**: Guide users through purchase steps with validation and error handling.
**Form Wizards**: Break complex forms into manageable steps with optional sections.
**Onboarding**: Create step-by-step tutorials for new users with progress tracking.
**Setup Wizards**: Guide users through configuration processes with success/error states.
**Task Lists**: Display checklist-style progress with completed/pending indicators.
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.