adobe-xd
When to use this skill
Use this skill whenever the user wants to:
- Create or edit UI/UX designs using Adobe XD artboards and components
- Build interactive prototypes with transitions, auto-animate, or voice triggers
- Work with repeat grids, component states, or responsive resize
- Export design specs or assets for developer handoff
- Manage shared libraries, design tokens, or collaborate via shared links
How to use this skill
1. Design Creation
- Create artboards: Select device preset or custom size, name artboards by screen (e.g., "Login", "Dashboard").
- Build components: Select elements -> right-click -> "Make Component". Use slash naming for categories (e.g.,
Button/Primary,Button/Secondary). - Add states: Select component -> "Default State" dropdown -> "New State" to create hover/active states.
- Use repeat grid: Select element -> "Repeat Grid" to create lists or card grids; drag handles to adjust count and spacing.
2. Prototyping
- Switch to Prototype mode.
- Drag a connector from a trigger element to the target artboard.
- Configure transition: trigger (Tap/Drag/Voice), action (Transition/Auto-Animate/Overlay), and easing.
- Preview with Play button (Cmd+Enter / Ctrl+Enter).
3. Developer Handoff
- Click Share -> "Share for Development".
- Developers access the published link to inspect spacing, colors, fonts, and export assets.
Example prototype link setup:
Trigger: Tap on "Login" button
Action: Transition to "Dashboard" artboard
Animation: Auto-Animate, 0.3s ease-out
Best Practices
- Keep components consistent with a shared design library.
- Ensure prototypes are fully linked with clear interaction annotations.
- Export assets at 1x, 2x, and 3x for multi-density screens.
- Use version history and shared links for team collaboration.
- Note: Adobe has deprecated XD in favor of Figma; evaluate for new projects.
Keywords
adobe xd, UI design, prototype, artboard, components, repeat grid, developer handoff, Adobe
More from teachingai/full-stack-skills
electron
Build cross-platform desktop applications with Electron, covering main/renderer process architecture, IPC communication, BrowserWindow management, menus, tray icons, packaging, and security best practices. Use when the user asks about Electron, needs to create desktop applications, implement Electron features, or build cross-platform desktop apps.
1.8Kelement-plus-vue3
Provides comprehensive guidance for Element Plus Vue 3 component library including installation, components, themes, internationalization, and API reference. Use when the user asks about Element Plus for Vue 3, needs to build Vue 3 applications with Element Plus, or customize component styles.
1.5Kuniapp-project
Provides per-component and per-API examples with cross-platform compatibility details for uni-app, covering built-in components, uni-ui components, and APIs (network, storage, device, UI, navigation, media). Use when the user needs official uni-app components or APIs, wants per-component examples with doc links, or needs platform compatibility checks.
741vue3
Guidance for Vue 3 using the official guide and API reference. Use when the user needs Vue 3 concepts, patterns, or API details to build components, apps, and tooling.
487drawio-flowchart
Creates flowcharts, swim lane diagrams, and business process diagrams using Draw.io (diagrams.net). Covers standard flowchart shapes (process, decision, start/end), connectors, auto-layout, and export to PNG/SVG/PDF. Use when the user needs to visualize workflows, decision trees, or business processes.
347mybatis-plus-generator
Generates MyBatis-Plus code (Entity, Mapper, Service, ServiceImpl, Controller, DTO, VO, BO) from database tables. Supports MVC and DDD architectures, Java and Kotlin, with standard CRUD and custom methods. Use ONLY when the user explicitly mentions MyBatis-Plus or mybatis-plus-generator; do NOT trigger for JPA, Hibernate, or other ORMs.
268