syncfusion-angular-stepper
Create and configure Syncfusion Angular Stepper component for multi-step workflows, wizards, forms, and onboarding flows. Use this skill when implementing step-by-step navigation, configuring step validation, handling step events, or customizing step appearance with icons, labels, and templates. This covers stepper-based wizard interfaces, progress tracking workflows, and multi-form configurations.
What this skill does
# Implementing Syncfusion Angular Stepper
The Syncfusion Angular Stepper component displays a step-by-step process or workflow, ideal for wizards, onboarding, or multi-step forms. This skill guides you through implementing, configuring, and customizing the Stepper component with complete control over step appearance, validation, events, and animations.
## When to Use This Skill
**Use this skill when:**
- Building multi-step wizards or workflows
- Creating step-by-step forms or onboarding flows
- Configuring step validation and linear flow
- Adding icons, labels, and custom templates to steps
- Handling step events (created, stepChanged, stepChanging, beforeStepRender, stepClick)
- Customizing step appearance with animations and styling
- Implementing tooltips, globalization, or RTL support
## Component Overview
The Stepper component provides:
- **Multiple step types**: Default (icons + labels), Indicator Only, Label Only
- **Two orientations**: Horizontal (default) and Vertical
- **Rich event system**: created, stepChanged, stepChanging, beforeStepRender, stepClick
- **Step validation**: Linear flow, completion states, conditional progression
- **Customization**: Icons, labels, templates, animations, tooltips
- **Accessibility**: WCAG compliance, keyboard navigation, RTL support
## Complete Table of Contents
### ๐ Getting Started
๐ **Read:** [references/getting-started.md](references/getting-started.md)
- Installation and package configuration
- Angular CLI setup and dependencies
- Basic stepper implementation in standalone Angular
- CSS imports and theme setup
- First render and initial configuration
### ๐ API Reference
๐ **Read:** [references/api-reference.md](references/api-reference.md)
- **Stepper Component Properties**: `activeStep`, `animation`, `cssClass`, `enablePersistence`, `enableRtl`, `labelPosition`, `linear`, `locale`, `orientation`, `readOnly`, `showTooltip`, `stepType`, `steps`, `template`, `tooltipTemplate`
- **Step Model Properties**: `cssClass`, `disabled`, `iconCss`, `isValid`, `label`, `optional`, `status`, `text`
- **Animation Settings**: `enable`, `duration`, `delay`
- **Stepper Methods**: `destroy()`, `nextStep()`, `previousStep()`, `refreshProgressbar()`, `reset()`
- **Events Overview**: `created`, `stepChanged`, `stepChanging`, `stepClick`, `beforeStepRender`
- **Enumerations**: `StepType`, `StepStatus`, `StepLabelPosition`, `StepperOrientation`
### โ๏ธ Configuring Steps
๐ **Read:** [references/steps-configuration.md](references/steps-configuration.md)
- Adding steps with `<e-step>` directive
- Configuring icons with `iconCss` property
- Setting labels and text content
- Setting active step with `activeStep`
- Optional steps and disabling steps
- Step read-only mode
- Step status tracking
- Step validation with `isValid` property
- Label positioning and alignment
### ๐จ Choosing Step Types
๐ **Read:** [references/step-types.md](references/step-types.md)
- Default type with indicators and labels
- Indicator Only type for compact layouts
- Label Only type for text-based navigation
- Label positions (Top, Bottom, Start, End)
- When to use each type
- Type selection patterns
### ๐ Setting Orientations
๐ **Read:** [references/orientations-and-layouts.md](references/orientations-and-layouts.md)
- Horizontal orientation (default)
- Vertical orientation for tall layouts
- Layout configuration and responsive design
- Orientation selection based on use case
### ๐ฏ Handling Events & Interactions
๐ **Read:** [references/events-and-interactions.md](references/events-and-interactions.md)
- `created` event for initialization
- `stepChanged` event after step changes (with EventArgs)
- `stepChanging` event for step change prevention (with EventArgs)
- `beforeStepRender` event for pre-render customization (with EventArgs)
- `stepClick` event for click handling (with EventArgs)
- Complete EventArgs reference documentation
- Event handler patterns and best practices
### โ
Validation and Flow Control
๐ **Read:** [references/validation-and-flow.md](references/validation-and-flow.md)
- Linear flow configuration for sequential progression
- Step validation and completion states
- Step status management
- Conditional step progression
- Error handling and state management
### ๐ญ Templates and Styling
๐ **Read:** [references/templates-and-customization.md](references/templates-and-customization.md)
- Custom step templates using `<ng-template>`
- Template binding and data context
- CSS class customization (`cssClass` property)
- Layout and appearance customization
- Responsive styling patterns
### ๐ Advanced Features
๐ **Read:** [references/advanced-features.md](references/advanced-features.md)
- Animation settings (duration, delay, enable) with StepperAnimationSettingsModel
- Tooltip configuration and tooltip templates
- Globalization and localization (i18n)
- RTL (Right-to-Left) support with `enableRtl`
- Accessibility features and keyboard navigation
- WCAG compliance and screen reader support
## Quick Start Example
```ts
import { Component } from "@angular/core";
import { StepperAllModule, StepperModule } from "@syncfusion/ej2-angular-navigations";
@Component({
imports: [ StepperAllModule, StepperModule ],
standalone: true,
selector: 'app-root',
template: `
<div class="stepper-container">
<ejs-stepper>
<e-steps>
<e-step label="Cart" iconCss="sf-icon-cart"></e-step>
<e-step label="Delivery Address" iconCss="sf-icon-transport"></e-step>
<e-step label="Payment" iconCss="sf-icon-payment"></e-step>
<e-step label="Confirmation" iconCss="sf-icon-success"></e-step>
</e-steps>
</ejs-stepper>
</div>
`,
styles: [`
.stepper-container {
padding: 20px;
max-width: 800px;
margin: 0 auto;
}
`]
})
export class AppComponent { }
```
## Common Patterns
### Pattern 1: Wizard with Form Validation
```html
<ejs-stepper (stepChanging)="onStepChanging($event)">
<e-steps>
<e-step label="Personal Info"></e-step>
<e-step label="Contact Details"></e-step>
<e-step label="Address"></e-step>
<e-step label="Confirmation"></e-step>
</e-steps>
</ejs-stepper>
```
Use the `stepChanging` event to validate form data before allowing step progression.
### Pattern 2: Dynamic Step Icons
```html
<ejs-stepper>
<e-steps>
<e-step *ngFor="let step of steps"
[label]="step.label"
[iconCss]="step.icon"></e-step>
</e-steps>
</ejs-stepper>
```
Bind step data dynamically using `*ngFor` directive.
### Pattern 3: Linear Workflow
```html
<ejs-stepper [linear]="true">
<e-steps>
<e-step label="Step 1"></e-step>
<e-step label="Step 2"></e-step>
<e-step label="Step 3"></e-step>
</e-steps>
</ejs-stepper>
```
Enable `linear` property to enforce sequential progression.
### Pattern 4: Event Handling
```ts
onStepChanged(args: StepperChangedEventArgs) {
console.log(`Active step index: ${args.activeStep}`);
}
onStepChanging(args: StepperChangingEventArgs) {
if (!isFormValid()) {
args.cancel = true; // Prevent step change
}
}
```
Use event handlers to track navigation and validate progress.
## Key Properties Summary
| Property | Type | Default | When to Use |
|----------|------|---------|------------|
| `stepType` | StepType | Default | Change display style: Default, Indicator, Label |
| `orientation` | Orientation | Horizontal | Set layout: Horizontal or Vertical |
| `linear` | boolean | false | Enforce sequential progression |
| `activeStep` | number | 0 | Set current active step (0-indexed) |
| `animation` | StepperAnimationSettingsModel | enabled | Configure transition animations |
| `showTooltip` | boolean | false | Display tooltips on step hover |
| `labelPosition` | string | Bottom | Position labels: Top, Bottom, Start, End |
| `readOnly` | boolean | false | Disable all step interactions |
| `cssClass` | string | - | Apply custom CSS classes |
| `enableRtl` | boolean | falsRelated 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.