ryugi-artifacts

Plugin ryugi-artifacts from marketplace ryugi-dev in Innei/ryugi. Commands read from the repo's manifest — today.

Skills (13)

• writing-skills

  Use when creating new skills, editing existing skills, or verifying skills work before deployment

• artifacts

  Use when seeing decides faster than reading — UI directions or mockups to choose between, a page to tune or click through, a design doc, review, proposal, or architecture walkthrough for them or their team to read — or when they ask for an artifact or artboard by name, or for a link to share one, or

• artifacts

  Use when seeing decides faster than reading — UI directions or mockups to choose between, a page to tune or click through, a design doc, review, proposal, or architecture walkthrough for them or their team to read — or when they ask for an artifact or artboard by name, or for a link to share one, or

• verifying

  Use before telling your human partner that work is done, fixed, live or ready, whatever it touched — UI, an API, a CLI, data, a deploy, performance — and before fixing a bug they can see, to capture it first

• artifacts

  Use when seeing decides faster than reading — UI directions or mockups to choose between, a page to tune or click through, a design doc, review, proposal, or architecture walkthrough for them or their team to read — or when they ask for an artifact or artboard by name, or for a link to share one, or

• brainstorming

  You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).

• executing-specs

  Use when an approved spec or design document is ready to implement and your human partner chose inline execution, or when they point you at a written design and ask you to build it in this session

• interface-craft

  Use when a visible product interface needs design judgment, including UI mockups during brainstorming, landing and marketing pages, visual direction exploration, reviewing an existing screen, or refining a prototype that feels generic or inconsistent.

• systematic-debugging

  Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

• test-driven-development

  Use when implementing any feature or bugfix, before writing implementation code

• using-git-worktrees

  Use when ryugi:executing-specs or ryugi:test-driven-development sends you here before the first implementation edit, when uncommitted work has to move to or be committed on a branch other than the one checked out, or when work done in a worktree has landed

• using-ryugi

  Use when starting any conversation - routes each task to the Ryugi workflow for its stage

• verifying

  Use before telling your human partner that work is done, fixed, live or ready, whatever it touched — UI, an API, a CLI, data, a deploy, performance — and before fixing a bug they can see, to capture it first

Hooks (10)

• SessionStart

  "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.cmd" session-start

• UserPromptSubmit

  "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.cmd" user-prompt-submit

• UserPromptSubmit

  "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.cmd" agent-event

• Stop

  "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.cmd" stop

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.cmd" agent-event

• PostToolUse

  "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.cmd" agent-event

• PostToolUseFailure

  "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.cmd" agent-event

• PermissionRequest

  "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.cmd" agent-event

• PermissionDenied

  "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.cmd" agent-event

• SessionEnd

  "${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.cmd" agent-event

Similar plugins