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개 표시
모든 저장소를 표시했습니다