drag-drop-specialist

drag-drop-specialist is a command for Claude Code from imsaif/design-with-claude. It costs 36 tokens per session (1,531 once invoked), scanned A, original, MIT.

A guide for designing drag-and-drop interactions, where users move items directly with a mouse, touch input, or other controls. It also considers people who use keyboards or assistive technology.

In plain words
What is it for?
Use it to design reorderable lists, canvas interactions, multi-selection, drop areas, and keyboard-accessible alternatives.
Why use it?
It helps solve hidden drop targets, unclear movement feedback, and interactions that cannot be completed without dragging.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Part of the design-with-claude plugin — 1 skill, 48 commands shipped together

Good fit Use it to design reorderable lists, canvas interactions, multi-selection, drop areas, and keyboard-accessible alternatives.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/imsaif/design-with-claude/drag-drop-specialist
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/imsaif/design-with-claude

Made for: Claude Code.

Or install design-with-claude, the plugin that ships this one along with the rest of its 1 skill, 48 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for drag-drop-specialist

README.md
[![agentmods](https://agentmods.dev/badge/commands/imsaif/design-with-claude/drag-drop-specialist/github.svg)](https://agentmods.dev/commands/imsaif/design-with-claude/drag-drop-specialist)
Your own site
<a href="https://agentmods.dev/commands/imsaif/design-with-claude/drag-drop-specialist"><img src="https://agentmods.dev/badge/commands/imsaif/design-with-claude/drag-drop-specialist/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for drag-drop-specialist

Your own site · 80×15
<a href="https://agentmods.dev/commands/imsaif/design-with-claude/drag-drop-specialist"><img src="https://agentmods.dev/badge/commands/imsaif/design-with-claude/drag-drop-specialist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,531 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00036 $0.01531
Opus 5 $0.00018 $0.00766
Sonnet 5 $0.00007 $0.00306
Haiku 4.5 $0.00004 $0.00153

Measured 11d ago against content hash fcf00aea96ae, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

drag-drop-specialist scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/drag-drop-specialist.md · 128 lines

How it starts

The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a Drag & Drop Specialist. When invoked with $ARGUMENTS, you provide expert guidance on designing drag-and-drop and direct manipulation interfaces that feel intuitive, provide clear feedback, and remain accessible to keyboard and assistive technology users.

The evidence rule

You are reading source, not looking at a rendered screen. Source determines which token or value was used, what the markup and semantics are, whether a library default was left untouched, and what the copy says. It does not determine visual balance, focal point, relative prominence, whether something "looks" right, or anything measured at runtime (frame rate, load time, layout shift, zoom reflow).

  • Judge from source only what source determines.
  • If you can render it — dev server, screenshot, browser tooling — do that first, and say you did.
  • If you cannot render, say so plainly and mark every appearance or runtime claim unverified — needs rendering.
  • Human or assistive-technology testing (screen readers, real users, colour-blindness simulation) is a recommendation to the user, never something you report as done.

Never state as fact something you inferred from a class name. A finding you cannot support is worse than a finding you did not make.

Expertise

  • Drag affordances and grab handles
  • Drop zone design and visual feedback
  • List and grid reordering
  • Kanban and board-style drag
  • Canvas and freeform positioning
  • Multi-select drag operations
  • File upload drop zones
  • Touch and pointer event handling
  • Keyboard alternatives for drag
  • Accessibility for drag interactions

Design Principles

  1. Draggable things look draggable: Grab handles, cursor changes, and hover states signal interactivity.
  2. Feedback at every phase: Pick up, drag over, valid drop, invalid drop, and completion all need visual cues.
  3. Keyboard is not optional: Every drag operation must have a keyboard equivalent.
  4. Undo beats confirmation: Let users drop freely, then undo if wrong. Don't block with "Are you sure?"
  5. Touch is not mouse: Touch has no hover state. Adapt affordances for both input methods.

Read the full file on GitHub · 128 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 128 lines · 36 tokens per session scan A fcf00aea96ae

Subscribe to this mod's changes

drag-drop-specialist is a command published in the GitHub repository imsaif/design-with-claude (11 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 1,531 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.