Skip to content
Skills Library
AI & agents · Planning

using-ryugi

/using-ryugi

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

Author
innei ↗
Repository
ryugi ↗
Licence
MIT
Last repository change
28.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
8
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 28.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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

Original author description

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

How it works

  1. The Rule
  2. Skill Priority
  3. Evidence Before Claims
  4. Red Flags
  5. Platform Adaptation
  6. User Instructions
Original SKILL.md headings · 73 lines, 631 words
SKILL.md preview
---
name: using-ryugi
description: Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
---

<SUBAGENT-STOP>
If you were dispatched as a subagent to execute a specific task, ignore this skill.
</SUBAGENT-STOP>

<EXTREMELY-IMPORTANT>
If you think there is even a 1% chance a skill might apply to what you are doing, you ABSOLUTELY MUST invoke the skill.

IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.

This is not negotiable. You cannot rationalize your way out of this.
</EXTREMELY-IMPORTANT>

## The Rule

**Invoke relevant or requested skills BEFORE any response or action** — including clarifying questions, exploring the codebase, or checking files. If it turns out wrong for the situation, you don't have to use it.

**Before entering plan mode:** if you haven't already brainstormed, invoke the brainstorming skill first.

Then announce "Using [skill] to [purpose]" and follow the skill exactly. If it has a checklist, create a todo per item.

**A change of output format re-opens the contract.** When the deliverable
changes (document → html, code → spec, …), re-read the skill's docs before
writing. "Already read once" does not carry over.

## Skill Priority

When multiple skills apply, process skills come first — they set the approach, then implementation skills (frontend-design, etc.) carry it out. Brainstorming and systematic-debugging are Ryugi' most common process skills, but the rule holds for any of them.

- "Let's build X" → ryugi:brainstorming first, then implementation skills.
- "Fix this bug" → ryugi:systematic-debugging first, then domain skills.
- UI built, or a visible bug to fix → ryugi:verifying-ui before calling it done; the project's own app-checking skill can make the evidence, not the verdict.

When the project has its own skill for a step — its design system, checking the running app, shipping — that skill does that step. Ryugi sets the process; the project's skills carry its domain.

## Evidence Before Claims

Before saying anything is done, fixed, or passing — and before committing, pushing, or opening a PR — run the command that proves it in this session, read its full output, and state the result with that evidence. A previous run, "should pass", a subagent's success report, or a diff that looks right is not evidence. If the check fails, report the actual state.

## Red Flags

These thoughts mean STOP—you're rationalizing:

| Thought                             | Reality                                                |
| ----------------------------------- | ------------------------------------------------------ |
| "This is just a simple question"    | Questions are tasks. Check for skills.                 |
| "I need more context first"         | Skill check comes BEFORE clarifying questions.         |
| "Let me explore the codebase first" | Skills tell you HOW to explore. Check first.           |
| "I can check git/files quickly"     | Files lack conversation context. Check for skills.     |
| "Let me gather information first"   | Skills tell you HOW to gather information.             |
| "This doesn't need a formal skill"  | If a skill exists, use it.                             |
| "I remember this skill"             | Skills evolve. Read current version.                   |
| "This doesn't count as a task"      | Action = task. Check for skills.                       |
| "The skill is overkill"             | Simple things become complex. Use it.                  |
| "I'll just do this one thing first" | Check BEFORE doing anything.                           |
| "This feels productive"             | Undisciplined action wastes time. Skills prevent this. |
| "I know what that means"            | Knowing the concept ≠ using the skill. Invoke it.      |

## Platform Adaptation

If your harness appears here, read its reference file for special instructions:

- Claude Code: `references/claude-code-tools.md`
- Codex: `references/codex-tools.md`
- Pi: `references/pi-tools.md`
- Antigravity: `references/antigravity-tools.md`
- Hermes Agent: `references/hermes-tools.md`
- Muse: `references/muse-tools.md`

## User Instructions

User instructions (CLAUDE.md, AGENTS.md, GEMINI.md, etc, direct requests) take precedence over skills, which in turn override default behavior. Only skip skill workflows or instructions when your human partner has explicitly told you to.
Files in this package (8)
  • SKILL.md 4 KB
  • references/antigravity-tools.md 2 KB
  • references/claude-code-tools.md 1 KB
  • references/codex-tools.md 5 KB
  • references/gemini-tools.md 8 KB
  • references/hermes-tools.md 3 KB
  • references/muse-tools.md 3 KB
  • references/pi-tools.md 1 KB

Versions

The database has no other skills named using-ryugi.

Database snapshot: 13.11.2026 · package version 1e7d307a3fbd (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90using-kisune
    Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
  • 90using-14all
    Use when starting any conversation - establishes how to find and use 14All skills, requiring a skill check before any response, including clarifying questions
  • 90using-superpowers
    Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
  • 100using-werkstatt
    Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
  • 100using-ultraship
    Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
  • 90next-level-agent
    Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.