zworkflow

Plugin zworkflow from marketplace soma-work in 2lab-ai/soma-work. Commands read from the repo's manifest — today.

Skills (68)

• UIAskUserQuestion

  Use when the user must choose between options or answer a question before work can go on, and the answer should come back as a button click. Triggers: 'ask the user', '선택지 물어봐', 'UIAskUserQuestion'.

• animation-performance

  Use when an animation stutters, drops frames or makes the page feel heavy. Triggers: 'animation jank', 'dropped frames', 'janky scroll', '프레임 드랍', '애니메이션 버벅'.

• animation-vocabulary

  Use when the user describes a web animation or motion effect without knowing its name and wants the right term. Triggers: 'what is it called when', '이런 효과 이름이 뭐야', '그 애니메이션 뭐라고 불러', '모션 용어'. Not for designing or building the effect (motion-design).

• apple-design

  Use when building or reviewing interface work that should feel like Apple: gesture-driven UI, spring motion, drag, swipe and sheet interactions, translucent depth, display typography. Triggers: 'apple design', 'fluid interface', 'ios feel', 'spring animation', '애플 디자인', '애플 감성', '스프링 애니메이션'.

• architecture-diagram

  Use when the user asks for a drawing of a system architecture or component structure. Triggers: '아키텍처 그려줘', '아키텍쳐 다이어그램', '구조도 그려줘', 'architecture diagram', 'system diagram', 'draw architecture'.

• autoz

  Use when the user wants a task taken from instruction to approved, reviewed PR without being asked anything along the way. Triggers: 'autoz', '$autoz'.

• block-kit-preview

  Use when a Slack Block Kit layout must be seen before it ships: previewing a payload, comparing design variants, checking a UI change. Triggers: 'block kit preview', 'render block kit', 'slack preview', 'block kit screenshot', 'block kit to png'.

• brainstorm

  Use when the user wants a very large number of ideas on a topic to choose from. Triggers: 'brainstorm', '브레인스토밍', '대량 아이디어', '아이디어 많이'.

• break-ui

  Use when a UI must be tested against worst-case data (very long, empty, huge, right-to-left, emoji) before it ships. Triggers: 'break the ui', 'worst case', 'stress the layout', 'UI 깨뜨려'.

• calldiff

  Use when work that changed code is finishing and its call-flow change must be summarised, or when a code review needs who-calls-whom across two refs. Triggers: 'calldiff', '콜스택 diff', '호출 흐름 변경', '코드 변경점 요약', 'summarize the code changes', 'call flow changed'.

• chore-open-source

  Use when a repository is about to go public, or already is, and private traces — host names, other companies, personal paths, secrets — must leave its files, history, PR text, releases and clones. Triggers: 'chore-open-source', '오픈소스 청소', '오픈소스 공개 준비', 'clean before open-sourcing'. Not for branch or

• chore

  Use when the user wants housekeeping on a registered GitHub repo: stale or merged branches, a sweep of every open PR and issue, handled Jira tickets, issues to move to Jira, stale worktrees. Triggers: '/chore', 'chore 작업', '레포 정리', '레포 청소', '브랜치 정리', 'PR·이슈 정리', '지라 정리'. Not for code fixes, issue ga

• choreograph

  Use when several animations on one screen must be ordered, overlapped or staggered so they read as one moment. Triggers: 'choreograph', 'stagger', 'sequence these animations', '순차 애니메이션'.

• cinematic-film

  Use when screen recordings should become a cinematic product-ad or launch film, or when make-product-demo needs its look. Triggers: 'cinematic', '시네마틱', '아웃오브포커스', 'out-of-focus', 'depth of field', '광고 영상처럼', 'launch film'.

• cron

  Use when the user wants to see or change scheduled jobs, including a job's model or where its output goes. Triggers: 'cron', 'schedule', 'scheduler', '크론', '스케줄', '스케쥴', '스케줄러'.

• decision-gate

  Use when a decision has to be made and it is unclear whether to decide alone, ask the user, or stop and split the work. Also when an implementation request must be sized before using-epic-tasks. Triggers: 'decision-gate', '판단 게이트'.

• deploy-qa

  Use when a deploy has landed and a host's post-deploy skill hands over the deploy range so that every issue it shipped gets QA'd and closed out, or asks for that run's readiness check, deploy confirmation or dry run. Triggers: 'deploy-qa', '배포 QA'.

• design

  Use when generated HTML or another visual output needs a deliberate design direction or a design critique, or when the user asks how to make it look good. Triggers: '디자인', '디자인 방향', '스타일 추천', '예쁘게', 'design direction', 'pick a style', 'make it look good', 'design review'.

• diagram

  Use when the user asks for something to be shown visually and the kind of picture is not yet decided. Triggers: '비주얼로 표현해줘', '다이어그램 그려줘', '그림으로', '시각화해줘', 'visualize', 'draw diagram', 'show as diagram'.

• dimensional-drawing-motion

  Use when a finished dimensional drawing sheet should be animated into a short motion film, or after the dimensional-drawing skill when motion is wanted. Triggers: 'animate this drawing', 'drawing motion', '도면 애니메이션', '도면 영상', '도면 모션'.

• dimensional-drawing

  Use when asked for an anatomy, spec sheet, redline or dimensional drawing of a UI component or physical product, or to take apart how a site builds a component. Triggers: 'dimensional drawing', 'anatomy', 'spec sheet', 'redline', '도면', '치수 도면', '컴포넌트 해부', '사이트 뜯어줘'.

• es

  Use when local:zwork completes, at turn end when finished work needs an Executive Summary, or when the user asks for one. Triggers: 'es', 'executive summary', '요약 보고'.

• explore-unknowns

  Use when a request is ambiguous or underspecified, the codebase or domain is unfamiliar, the user will know it when they see it, a reference implementation must be understood before porting, or before stv:spec interviews and autoz RED. Triggers: 'explore unknowns', 'explore-unknown', '탐구', '뭘 모르는지 모

• find-animation-opportunities

  Use when the user wants to know where motion would really help in an interface, before anything is built. Triggers: 'where should this animate', 'animation opportunities', '애니메이션 기회'.

• gestures

  Use when building drag, swipe or bottom-sheet gestures that should follow the finger. Triggers: 'drag gesture', 'swipe to dismiss', 'bottom sheet gesture', '스와이프 제스처'.

• github-pr

  Use when reviewing a GitHub PR, checking its status, or preparing a PR summary. Triggers: 'github-pr', 'PR 상태', 'PR 데이터'.

• html

  Use when content (markdown, notes, JSON, CSV, a report) should become a styled web page, card, deck or poster, or a PNG of one. Triggers: 'html로 만들어줘', 'HTML로 변환', '이걸 페이지로', 'render as html', 'convert to html', 'make a card', 'make a deck', 'make a poster'.

• impeccable

  Use when the user wants to design, redesign, critique, audit, polish or harden a frontend interface, or capture its design system, or when the html skill is asked for design=impeccable. Triggers: 'impeccable', '임페커블', 'design critique', 'design audit', 'polish this UI', '디자인 비평', '디자인 다듬어줘'. Not for

• import-skills

  Use when skills from other agent repos should be brought into this plugin. Triggers: 'import-skills', '스킬 가져오기', 'vendor skills'.

• improve-animations

  Use when the motion across a whole codebase needs an audit with prioritised fix plans, without editing source. Triggers: 'audit animations', 'motion audit', '모션 감사'.

• learn

  Use when the conversation should be reflected on so that mistakes and durable facts get saved for future sessions. Triggers: 'learn', '배운 것 정리', 'reflect on this session'.

• llm-dispatch

  Use when an external-model consultation must run long in the background, be continued later or be cancelled. Triggers: 'llm-dispatch', 'llm 디스패치', 'long-running llm'.

• lottie

  Use when the user asks to create, edit or fix a Lottie animation, asks for an animation in a page, or when the html skill needs a motion layer. Triggers: 'lottie', '애니메이션 만들어줘', 'animate this', 'add motion', '모션 넣어줘'.

• make-product-demo

  Use when asked for a product demo, launch video, demo film or README demo GIFs made from the real product. Triggers: 'make-product-demo', '제품 데모', '데모 영상', '런칭 영상', 'demo video', 'product demo', 'README GIF'.

• mobile-native

  Use when a web app should feel native on a phone: tap flashes, viewport height, input zoom, tap delay, safe areas. Triggers: 'feel native', 'mobile web', '모바일 앱처럼'.

• motion-design

  Use when building or tuning any UI motion: transitions, drawers, toasts, popovers, drag gestures, easing and durations. Triggers: 'animation', 'motion', 'transition', 'easing', 'make it feel right', '애니메이션', '모션', '트랜지션', '이징'. Not for reviewing existing motion code (review-motion).

• pr-triage

  Use when every open PR of a GitHub repo must be sorted to a final outcome and acted on. Triggers: 'pr-triage', 'PR 정리 분류', '열린 PR 트리아지'. Not for a sweep of PRs, issues, branches and Jira together (chore).

• qa-issue

  Use when one tracker issue already deployed to a QA environment needs QA recorded on the issue, called per issue by local:deploy-qa or on its own. Triggers: 'qa-issue', '이슈 QA'.

• qa-report

  Use when per-issue QA results must become an evidence report a reviewer can check without asking, called by deploy-qa at its report step or on its own. Triggers: 'qa-report', 'QA 리포트'.

• release-notes

  Use when release notes are needed for the changes between two git refs, or a deploy reaches its release-notes step. Triggers: 'release notes', '릴리즈 노트', 'changelog'.

• remove-animations

  Use when animations cost more than they give — frequent, keyboard-driven or slow — and should be cut. Triggers: 'remove animations', 'too much animation', '애니메이션 줄여'.

• research-skill

  Use when a skill should get better by running it for real, or when the user wants a skill evaluated. Triggers: 'research-skill', '스킬 리서치', 'evaluate this skill'.

• review-motion

  Use when asked to review animation or motion code: transitions, easing, durations, drawers, toasts, popovers, drag gestures. Triggers: 'review motion', 'review this animation', '모션 리뷰'. Not for general code review.

• setup-ai-docs

  Use when a repo should get a system that keeps its docs and README in sync with its code on every future task. Triggers: 'setup-ai-docs', 'docs 셋업', 'setup docs sync', '문서 체계 셋업'.

• setup-ai-workflow

  Use when a repo should get an AI work-execution system: check gate, commit and PR conventions, worktrees, build, deploy and release runbooks. Triggers: 'setup-ai-workflow', 'AI 워크플로우 셋업', 'agent 작업 체계 셋업'.

• simplify

  Use when reviewing a diff or PR before approval for over-engineering, or when the user asks what can be cut or complains about bloat, boilerplate or unneeded dependencies. Triggers: 'simplify', '단순화', '간소화', 'is this over-engineered', 'what can we delete', 'yagni'. Not for prose, translation or summ

• skill-description

  Use when writing, reviewing or fixing the description of a skill, command or agent. Also when skills fire at the wrong moment, the skill listing is long, or descriptions go missing from it. Triggers: 'skill-description', '스킬 디스크립션', 'description 고쳐줘', 'fix skill descriptions'.

• toss-design

  Use when a page, report, mock-up or mini-app screen should look like Toss, or another skill passes theme=toss-blue or theme=toss-black. Triggers: 'toss design', 'toss style', 'TDS', 'apps in toss', '토스 디자인', '토스 스타일로', '토스처럼', '앱인토스'.

• trinity

  Use when a code review, plan review, decision or tie-break needs the 3-agent consensus panel, including every review or consult gate another skill sends to it. Triggers: 'trinity', '트리니티', '3엔진 합의', 'trinity로 리뷰해줘'.

• ui-ux-reference

  Use when a real website's visual design should be saved as a named reference the ui-ux skill can apply. Triggers: 'add a ui-ux reference', 'ui-ux-reference', '레퍼런스 추가', '이 사이트를 레퍼런스로', 'extract design from this site'.

• ui-ux

  Use when planning, building, reviewing or fixing the UI or UX of a web or mobile interface, or when a named design reference should be applied. Triggers: 'ui ux', 'landing page design', 'dashboard design', 'color palette', 'font pairing', 'use the claude reference', 'UI 디자인', 'UX 개선'.

• using-dotprd

  Use when a large feature, rebuild or port in a repo should be driven through a repo-root .prd folder, or multi-session work needs a spec-then-converge discipline. Triggers: '.prd 만들고 진행', 'dotprd로 진행', '/using-dotprd', '다른 레포 .prd처럼'. Not for quick fixes, docs-only edits or personal notes.

• using-epic-tasks

  Use when the user asks for something to be implemented and the work must be sized into one issue and PR, an epic with sub-issues, or a stop to split it. Also when running inside an epic session. Triggers: 'using-epic-tasks', '에픽으로 진행', '이슈로 쪼개줘'.

• using-intentfirst

  Use when an instruction from G arrives, before any research, plan or build. Triggers: 'using-intentfirst', '의도 먼저'.

• using-ssot

  Use when a user instruction must be kept as the single source of truth for the work, split into a task tree, updated after a re-instruction, or reported on at the end. Triggers: 'using-ssot', 'SSOT', 'SSOT-TASK-TREE'.

• using-user-skills

  Use when the user wants to make, change, read, list, delete or run their own personal skills. Triggers: '개인 스킬', 'my skill', 'user skill', 'MANAGE_SKILL', '$user:'.

• using-z
• using-zwriting
• z
• zcheck
• zdeepresearch
• zexplore
• zfix
• zkorean
• zreflect
• zthink
• ztrace
• zwork

Slash commands (6)

• /zworkflow:explore

  Use when something must be found in this codebase: an implementation, a pattern, a code path.

• /zworkflow:librarian

  Use when external documentation, library APIs, best practices or open-source source code must be looked up.

• /zworkflow:oracle-reviewer

  Use when code needs a review by the trinity panel.

• /zworkflow:oracle

  Use when an architecture decision, a design choice or a failure analysis needs a deep second opinion.

• /zworkflow:orchestrator

  Use when a multi-part task should be coordinated across the Oracle, Explore and Librarian agents in the current context.

• /zworkflow:review-pr

  Use when a PR needs a full review by specialised review agents.

Subagents (18)

• astra-elon

  Use when the elon persona (physics-first, cost structure) should advise alone on the astra engine. Not for a trinity panel slot.

• astra-zhuge

  Use when the trinity panel needs its astra strategist slot, or the zhuge persona should advise alone on the astra engine.

• brainstorm-haiku

  Use when the brainstorm skill hands one cell (field and angle) to the haiku engine. Not for any other task.

• brainstorm-luna

  Use when the brainstorm skill hands one cell (field and angle) to the luna engine. Not for any other task.

• code-reviewer

  Use when code was just written or changed and should be checked against the project guidelines and best practices, before a commit or a PR. Also when the user asks whether new code looks good.

• comment-analyzer

  Use when code comments or docstrings were added or changed, before a PR is finalised, or when existing comments may have drifted from the code they describe.

• explore

  Use when something must be found in this codebase — an implementation, a pattern, a code path — and only the conclusion is needed.

• fable-zhuge

  Use when the trinity panel needs its anthropic strategist slot, or the zhuge persona should advise alone on the fable engine.

• grok-elon

  Use when the trinity panel needs its physics-first slot, or the elon persona should advise alone on the grok engine.

• librarian

  Use when official docs, library APIs, best practices or open-source source code must be looked up outside this codebase.

• oracle

  Use when an architecture decision, an unfamiliar pattern, a security or performance concern, or a bug after 3 failed fixes needs a single-engine deep consult. Not for review gates (trinity).

• orchestrator

  Use when a multi-part task should run autonomously as a subagent, coordinating Oracle, Explore and Librarian, with no user interaction.

• pr-test-analyzer

  Use when a PR was created or updated and its test coverage should be checked for gaps before it is marked ready.

• reviewer

  Use when a diff needs a ruthless third review focused on simplicity and first principles.

• silent-failure-hunter

  Use when a change adds or touches error handling, catch blocks or fallback logic, or a PR should be checked for errors that fail silently.

• strategist

  Use when one consult should weigh both the zhuge (strategist) and elon (physics-first) views, or a question is unclear and both angles are wanted. Not for a trinity panel slot.

• type-design-analyzer

  Use when a new type is introduced, types are refactored, or a PR adds types whose invariants and encapsulation should be reviewed.

• zkorean

  Use when the zkorean skill hands Korean text and its rule book for one correction pass.

Hooks (4)

• Stop

  ${CLAUDE_PLUGIN_ROOT}/hooks/stop-hook.sh

• Stop

  ${CLAUDE_PLUGIN_ROOT}/hooks/hook-proxy.sh cleanup

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/hook-proxy.sh pre_tool_use

• PostToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/hook-proxy.sh post_tool_use