ryugi

In the author's own words, from each skill's SKILL.md.

• 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 when they paste a Ryugi Cloud link (…/a/…) to read. Inside brainstorming or anywhere else

  skills/artifacts/SKILL.md on GitHub (opens in a new tab)

• 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).

  skills/brainstorming/SKILL.md on GitHub (opens in a new tab)

• 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

  skills/executing-specs/SKILL.md on GitHub (opens in a new tab)

• 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.

  skills/interface-craft/SKILL.md on GitHub (opens in a new tab)

• systematic-debugging

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

  skills/systematic-debugging/SKILL.md on GitHub (opens in a new tab)

• test-driven-development

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

  skills/test-driven-development/SKILL.md on GitHub (opens in a new tab)

• 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

  skills/using-git-worktrees/SKILL.md on GitHub (opens in a new tab)

• using-ryugi

  Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

  skills/using-ryugi/SKILL.md on GitHub (opens in a new tab)

• verifying-ui

  Use when work changes what your human partner sees in a running app — a spec with UI has just been built, or a visible bug (layout, style, wrong state on screen) is about to be fixed — and before telling them it is done or ready

  skills/verifying-ui/SKILL.md on GitHub (opens in a new tab)

• writing-skills

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

  .claude/skills/writing-skills/SKILL.md on GitHub (opens in a new tab)

No skill matches that filter.

Similar skills

• CowAgentby zhayujie Open-source personal AI assistant & Agent Harness. Plans tasks, runs tools and skills, self-evolves with memory and knowledge. Multi-agent,… 47.8k stars · 3 skills
• J-Space-Cognition-Suiteby Tiger3807861189 J-Space Cognition Suite — a model-agnostic inference-time control suite for deep reasoning, long-horizon work, verification, and recovery.… 3k stars · 1 skill
• skillshareby runkids 📚 Sync skills, agents, MCP, plugins to all AI CLI tools with one command and simplify team sharing. 2.9k stars · 10 skills
• reaby morluto Reverse engineer anything with agents, from app behavior down to native binaries. 423k stars · 5 skills
• ECCby affaan-m The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Cod… 296k stars · 30 skills
• ponytailby DietrichGebert Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote. 183k stars · 6 skills