syncfusion-react-diagram
Create and customize visual diagrams in React using Syncfusion Diagrams. Trigger for requests involving React component setup, nodes and connectors, flowcharts, org charts, process diagrams, BPMN or UML models, layout algorithms, swimlanes, symbol palettes, and interactive diagram visualization features.
What this skill does
# Syncfusion React Diagram
The Syncfusion React Diagram component enables building rich, interactive diagrams including flowcharts, organizational charts, BPMN process flows, UML diagrams, mind maps, and network diagrams. It renders using SVG and supports extensive customization through nodes, connectors, ports, annotations, layouts, and data binding.
## Table of Contents
- [When to Use This Skill](#when-to-use-this-skill)
- [Component Overview](#component-overview)
- [Documentation and Navigation Guide](#documentation-and-navigation-guide)
- [Getting Started](#getting-started)
- [Nodes](#nodes)
- [Connectors](#connectors)
- [Labels and Annotations](#labels-and-annotations)
- [Ports](#ports)
- [Shapes and Styles](#shapes-and-styles)
- [BPMN Diagrams](#bpmn-diagrams)
- [UML Diagrams](#uml-diagrams)
- [Layouts](#layouts)
- [Swimlanes](#swimlanes)
- [Groups and Containers](#groups-and-containers)
- [Symbol Palette](#symbol-palette)
- [Data Binding](#data-binding)
- [Interaction and Tools](#interaction-and-tools)
- [Serialization and Export](#serialization-and-export)
- [Diagram Settings](#diagram-settings)
- [Quick Start Example](#quick-start-example)
- [Common Patterns](#common-patterns)
- [Module Injection Reference](#module-injection-reference)
- [Key Props](#key-props)
## When to Use This Skill
Use this skill when users need to:
- **Build flowcharts** representing processes, decision trees, or workflows
- **Create org charts** from hierarchical or flat data sources
- **Model BPMN diagrams** with activities, events, gateways, and flows
- **Draw UML diagrams** including class diagrams and sequence diagrams
- **Visualize mind maps** or radial layouts from data
- **Design network/entity diagrams** with nodes and relationship connectors
- **Implement swimlane diagrams** with lanes and phases
- **Drag and drop shapes** from a symbol palette onto a canvas
- **Bind data** to automatically generate diagram structure
- **Serialize and restore** diagram state as JSON
- **Export or print** diagram content as image/SVG
## Important: API Verification Required
**API Verification Required**: Always verify API class names, properties, and signatures by reading reference files (`references/*.md`) BEFORE generating code examples. Do not assume or infer class names.
## Component Overview
The Diagram component is built around:
- **Nodes** — Graphical shapes (rectangles, circles, flow shapes, custom) placed on the canvas
- **Connectors** — Lines/arrows linking nodes or freestanding points
- **Annotations** — Text labels attached to nodes or connectors
- **Ports** — Named connection points on nodes for precise connector anchoring
- **Layouts** — Automatic arrangement algorithms (hierarchical, org-chart, mindmap, radial, flowchart)
- **Symbol Palette** — Sidebar of draggable shape symbols
- **Module System** — Opt-in feature modules (`Inject` directive) to keep bundle size lean
All diagram elements are rendered using **SVG** for crisp, resolution-independent graphics.
## Documentation and Navigation Guide
### Getting Started
📄 **Read:** [references/getting-started.md](references/getting-started.md)
**When to read:**
- First-time setup of the Diagram component
- Installing packages, CSS imports, and theme configuration
- Creating a minimal `DiagramComponent`
- Understanding the `Inject` module system
- Next.js or Preact integration
**Covers:**
- npm install and dependencies
- Vite/CRA project setup
- CSS theme import paths
- Basic `DiagramComponent` with `nodes` and `connectors`
- Module injection with `<Inject services={[...]} />`
- Next.js and Preact usage notes
---
### Nodes
📄 **Read:** [references/nodes.md](references/nodes.md)
**When to read:**
- Adding, positioning, and sizing nodes
- Customizing node appearance (fill, stroke, shadow)
- Working with node shapes (Flow, Basic, Path, Image, HTML)
- Handling node events (click, drag, resize)
- Expanding/collapsing nodes at runtime
- Setting default node properties via `getNodeDefaults`
**Covers:**
- Creating nodes via `nodes` collection
- `offsetX`/`offsetY`, `width`/`height` positioning
- Adding/removing nodes at runtime (`diagram.add`, `diagram.remove`)
- Style properties (fill, strokeColor, opacity, gradient)
- `getNodeDefaults` pattern for consistent styling
- Node expand/collapse with `expandIcon`/`collapseIcon`
- Node interaction events
---
### Connectors
📄 **Read:** [references/connectors.md](references/connectors.md)
**When to read:**
- Drawing lines/arrows between nodes or freestanding points
- Choosing connector type (Straight, Orthogonal, Bezier)
- Configuring connector segments and routing
- Customizing decorator (arrow) shapes
- Setting `sourceID`/`targetID` to link nodes
- Setting `getConnectorDefaults` for consistent styling
**Covers:**
- Connector types: `Straight`, `Orthogonal`, `Bezier`
- `sourcePoint`/`targetPoint` for freestanding connectors
- `sourceID`/`targetID` for node-to-node connections
- Multiple segment configuration
- Bezier control points and segment edit orientation
- Arrow/decorator customization
- Connector events and interaction
- `getConnectorDefaults` pattern
---
### Labels and Annotations
📄 **Read:** [references/labels-and-annotations.md](references/labels-and-annotations.md)
**When to read:**
- Adding text labels to nodes or connectors
- Styling annotation text (font, color, bold, alignment)
- Making labels draggable or editable
- Positioning labels relative to nodes/connectors
- Handling label-specific events
**Covers:**
- `annotations` array on nodes and connectors
- Label `content`, `style`, `offset`, `alignment`
- Node labels vs. connector labels
- Label interaction (edit on double-click, drag)
- Label appearance (background, border, padding)
- Label events
---
### Ports
📄 **Read:** [references/ports.md](references/ports.md)
**When to read:**
- Creating named connection points on nodes
- Controlling where connectors attach to a node
- Styling and positioning ports
- Restricting connector connections to specific ports
- Handling port interaction events
**Covers:**
- Port types and `ports` array on nodes
- Port positioning (`offset`, `alignment`)
- Port appearance (shape, fill, stroke)
- Connecting connectors to specific ports via `sourcePortID`/`targetPortID`
- Port interaction and visibility options
- Port events
---
### Shapes and Styles
📄 **Read:** [references/shapes-and-styles.md](references/shapes-and-styles.md)
**When to read:**
- Choosing the right shape type (Flow, Basic, Path, Image, HTML, Native SVG)
- Applying fill colors, gradients, and stroke styles
- Customizing node appearance with CSS or themes
- Understanding shape property structure
**Covers:**
- `shape.type` options: `Flow`, `Basic`, `Path`, `Image`, `HTML`, `Native`
- Flowchart shape values (Terminator, Process, Decision, etc.)
- Basic shape values (Rectangle, Ellipse, Diamond, etc.)
- Style properties: `fill`, `strokeColor`, `strokeWidth`, `strokeDashArray`, `opacity`
- Linear and radial gradients
- Shadow effect
- CSS class-based styling
---
### BPMN Diagrams
📄 **Read:** [references/bpmn-diagrams.md](references/bpmn-diagrams.md)
**When to read:**
- Modeling business process flows using BPMN notation
- Using BPMN-specific shapes (activities, events, gateways)
- Drawing sequence flows, message flows, associations
- Adding data objects, data sources, text annotations, and groups
**Covers:**
- `BpmnDiagrams` module injection
- BPMN shape type: `shape.type = 'Bpmn'`
- Activities: Task types, Subprocess, Expanded Subprocess
- Events: Start, End, Intermediate events and their triggers
- Gateways: Exclusive, Parallel, Inclusive, Complex
- Flows: Sequence, Message, Association
- Data objects and data sources
- BPMN groups and text annotations
---
### UML Diagrams
📄 **Read:** [references/uml-diagrams.md](references/uml-diagrams.md)
**When to read:**
- Building UML class diagrams with attributes and methods
- Modeling relationsRelated 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.