Skip to main content
Manusで任意のスキルを実行
ワンクリックで
gyrforge
GitHub クリエイタープロフィール

gyrforge

1 件の GitHub リポジトリにある 5 件の収集済み skills をリポジトリ単位で表示します。

収集済み skills
5
リポジトリ
1
更新
2026-06-18
リポジトリマップ

skills がある場所

収集済み skill 数が多いリポジトリを、このクリエイターカタログ内の比率と職業範囲とともに表示します。

リポジトリエクスプローラー

リポジトリと代表的な skills

interrogation
プロジェクト管理専門家

Interrogate the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

2026-06-18
understand-code
ソフトウェア開発者

Helps the human deeply understand the codebase through incremental teaching. Before each step, verifies they grasp the problem (motivation, branches, edge cases), the solution (design decisions, trade-offs), and the broader impact. Uses Socratic questioning, restatement checks, and adaptive depth (ELI5/ELI14/ELII — explain like she's an intern). Use when the user says "help me understand", "explain", "walk me through", "what does this do", "why was this done this way", or asks to be taught. Core skill for pairing with a junior developer or someone unfamiliar with the codebase.

2026-06-16
ponytail-help
その他コンピュータ職

Quick-reference card for all ponytail modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /ponytail-help, "ponytail help", "what ponytail commands", "how do I use ponytail".

2026-06-14
ponytail-review
ソフトウェア品質保証アナリスト・テスター

Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for over-engineering", "what can we delete", "is this over-engineered", "simplify review", or invokes /ponytail-review. Complements correctness-focused review, this one only hunts complexity.

2026-06-14
ponytail
ソフトウェア開発者

Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", and whenever they complain about over-engineering, bloat, boilerplate, or unnecessary dependencies.

2026-06-14
1 件中 1 件のリポジトリを表示
すべてのリポジトリを表示しました