End-to-end SEED component implementation guide that starts with a brainstorming session to clarify requirements, then makes architecture decisions, follows the category-specific pattern, and runs through verification. Use this whenever the user is adding a new component, changing behavior across component layers, or extending a snippet — even if they don't explicitly say "create component". Always invoke this skill before touching rootage YAML, qvism recipes, react packages, or component docs. Covers all 5 component categories (simple, compound stateless, compound stateful, multi-recipe, layout) and refuses to skip the requirements brainstorming.
Drives the snapshot-release flow for the current branch's PR. Posts a `/snapshot` comment on the PR if one isn't already there (with confirmation), waits for the `Continuous Releases` workflow to finish, and reports the tarball URLs from the resulting `📦 Snapshot Release` comment. Use for both triggering and waiting — phrases like "trigger a snapshot", "ship a snapshot release", "post `/snapshot` for me", "let me know when snapshot is done", "wait for the snapshot and show me the tarballs", "did the snapshot finish?", "snapshot 해줘", "snapshot 완료되면 알려줘", "snapshot 결과 보여줘", "tarball 받아와".
SEED Design 통합 가이드. 프로젝트 셋업, 컴포넌트 탐색/사용, 파운데이션(색상·타이포·스페이싱) 활용, 테마/스타일링, CLI 워크플로우(init/add/add-all/compat/docs/upgrade), 스니펫 버전 호환성, 업그레이드 진단까지 커버. SEED Design 관련 질문이면 이 스킬을 사용한다. 사용자가 "SEED 어떻게 써?", "컴포넌트 뭐 있어?", "색상 토큰 쓰는 법", "디자인시스템 셋업" 같은 질문을 하면 반드시 이 스킬을 로드한다.
Develop and maintain the Figma V3 migration plugin, including metadata extraction, mapping updates, and type-safe property conversion. Use when updating V2 to V3 migration mappings in tools/figma-v3-migration.
git diff 분석 기반으로 changeset 파일을 자동 생성합니다. 변경된 패키지를 감지하고, 변경 타입을 분류하고, 한국어 유저향 메시지를 작성합니다.
Write or rewrite SEED Design component guideline docs (MDX) by extracting content and images from Figma documentation layers. Use this skill whenever the user wants to create, update, or migrate component documentation from Figma into docs/content/docs/components/, provides a Figma node URL for documentation, or asks to write/update a component guideline page. Also triggers for "write the docs for X component", "create guideline from Figma", "update the MDX for [component]", "가이드라인 문서 작성", or "피그마에서 문서 가져오기".
Manage deprecation lifecycle for components, interfaces, and tokens with versioned notices, replacement guidance, migration docs, and removal tracking. Use when deprecating, migrating, or removing API/spec options.