claude-design

To import Claude Design handoffs into Segmently, provide the project link and target so the skill can pull the design, choose the correct workflow, and prepare the import plan automatically. This prevents guessing the target path for custom screens, sections, and themes.

Native theme extraction and design-system routing pulls design tokens and components from Claude Design links and directs them into the correct Segmently design-system round trips. This ensures imported themes stay incremental, reviewable, and safe without manual path selection.

Yes, you can import FlexibleLayout sections and custom screens from Claude Design. The skill detects section-versus-screen cases from handoff prompts and routes each export to the proper Segmently import workflow with per-workflow validation.

Yes, you need to specify a Segmently target so the skill can resolve where the design belongs. Providing the target allows DesignSync-based retrieval, target resolution, and publish-gated CLI execution to move the design safely.

The best way to handle untrusted design content during Segmently design intake is using the skill's operational guardrails. It applies per-workflow validation, health checks, and publish gating so imports remain reviewable and safe from malicious content.

Claude Code handoff review for Segmently plugins fails validation when trigger detection is imprecise or DesignSync retrieval is incomplete. The skill requires precise trigger detection and per-workflow validation to prevent incorrect target resolution and import errors.