sketch-init

Scaffold routes and blank page/component structures from Sketch export artboards.

5|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/YamadaAoi/mcp-sketch --skill sketch-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sketch-init
Source: https://github.com/YamadaAoi/mcp-sketch/tree/main/skills/sketch-init
Command: npx skills add https://github.com/YamadaAoi/mcp-sketch --skill sketch-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of turning a Sketch export zip into a structured, project-ready page/component scaffold without manually planning routes and files for every artboard.

Core Features & Use Cases

  • Artboard-wide route planning: Extracts all artboards from a Sketch export zip and plans routing structure from preview images.
  • Safe, reusable scaffolding: Reuses existing route entries and never overwrites existing component files; creates only blank skeletons plus description markdown.
  • Technology-stack adaptation: Detects the target project’s tech stack (by reading package.json) and aligns route/component formats to the existing code style.
  • Workflow-friendly: Supports automated workflow mode by running silently and prepares artifacts for later split/draw steps.

Quick Start

Use the skill to scan a Sketch export zip and generate blank page and component scaffolds with planned routes, for example: run the AI command to execute sketch-init on your exported Sketch zip.

Frequently Asked Questions about sketch-init

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scaffold components and plan routes from a Sketch export?

To scaffold components from a Sketch export, the tool scans the zip file's preview images, plans a routing structure, and generates blank page directories alongside component skeleton files automatically.

What is the best way to bootstrap a design-to-code project without manual route planning?

The best way to bootstrap design-to-code projects is automating artboard extraction to generate planned route entries and blank component structures, eliminating manual file and route creation for each design page.

Does the scaffolding tool overwrite existing component files or duplicate routes?

No, the scaffolding tool reads existing routes and component paths to avoid duplicate writes, ensuring it only creates blank skeletons and description markdown without overwriting any existing component files.

Can I adapt generated route and component formats to match my existing tech stack?

Yes, the scaffolding process detects your target project's tech stack by reading package.json, aligning generated route and component file formats to match your existing code style and conventions.

How do I scaffold only specific artboards from a Sketch export zip?

You can scaffold specific artboards by using target_artboards filtering, which restricts preview-based analysis and file generation to only the selected artboards within your Sketch export zip.

Why does the generated scaffold only contain blank component skeletons?

Generated scaffolds contain blank component skeletons because the tool prepares initial artifacts for later split and draw steps, creating planned directories and description markdown rather than fully implemented UI code.