Découvrez les skills databases project management, comparez leurs dépôts et consultez leurs instructions.
This skill should be used when the user asks about "key startup metrics", "SaaS metrics", "CAC and LTV", "unit economics", "burn multiple", "rule of 40", "marketplace metrics", or requests guidance on tracking...
This skill should be used when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls. Implements Manus-style file-based planning with task_plan.md, findings.md, and progress....
Use when implementing distributed transactions, coordinating multi-service workflows, handling compensating transactions, or asking about "saga pattern", "distributed transactions", "compensating actions", "wor...
Use when evaluating agent performance, building test frameworks, measuring quality, or asking about "agent evaluation", "LLM-as-judge", "agent testing", "quality metrics", "evaluation rubrics", "agent benchmark...
This skill should be used when the user asks to "analyze competitors", "assess competitive landscape", "identify differentiation", "evaluate market positioning", "apply Porter's Five Forces", or requests compet...
This skill should be used when the user asks about "UI design", "UX design", "user interface", "user experience", "wireframes", "mockups", "design patterns", "design system", "component design", "layout", or me...
Use when executing implementation plans with independent tasks in the current session
Use when "product strategy", "OKR planning", "product vision", "market positioning", or asking about "competitive analysis", "product-market fit", "go-to-market strategy", "product roadmap"
Use when "RICE prioritization", "feature prioritization", "PRD writing", "user stories", or asking about "product roadmap", "customer interviews", "sprint planning", "backlog grooming"
Use when "SHAP", "Shapley values", "feature importance", "model explainability", or asking about "explain predictions", "interpretable ML", "feature attribution", "waterfall plot", "beeswarm plot", "model debug...
This skill should be used when the user asks to "plan team structure", "determine hiring needs", "design org chart", "calculate compensation", "plan equity allocation", or requests organizational design and hea...
Complete Jira ticket management including viewing tickets, transitioning statuses, linking tickets, searching, creating, and updating. Use when the user asks to view, show, display, check, move, transition, sta...
This skill should be used when the user asks to "create a workflow diagram", "visualize a workflow", "generate a process flow", "make a flowchart", "diagram these steps", or provides workflow steps that need vi...
Provides Git workflow guidance for branching, committing, merging, and creating pull requests. Use when creating commits, making PRs, managing branches, resolving conflicts, or asking about Git workflow.
Provides game design advice for tower defense balance, enemy stats, tower abilities, progression curves, and difficulty tuning. Use when designing new enemies, towers, waves, or asking about game balance, diffi...
Automated git workflow helpers for common development tasks like creating feature branches, cleaning up merged branches, and interactive rebasing. Use when the user mentions git branching, branch cleanup, featu...
문서 생성, 언어 초기화, 템플릿 최적화를 통합한 프로젝트 관리 시스템
TDD, 디버깅, 성능 최적화, 코드 리뷰, 품질 보증을 통합 개발 워크플로우로 결합하는 포괄적 개발 워크플로우 전문가
엔터프라이즈 템플릿 관리 (코드 보일러플레이트, 피드백 템플릿, 프로젝트 최적화 워크플로우 포함)
EARS 형식, 요구사항 명확화, Plan-Run-Sync 통합을 통한 SPEC workflow 오케스트레이션
既存資料のREADME.mdを読み込み、推奨所要時間を再見積もりして更新するスキル。学習ガイド、チュートリアル、練習問題、実践課題の各資料タイプに対応し、章/ステップ/回ごとの目安時間と合計時間をテーブル形式で生成する。
Steps for creating better Github actions by gathering context on how they are used
Development workflow emphasizing test-first development, task classification, and appropriate tracking. Use when starting implementation, planning changes, or structuring development work.
A structured workflow for AI-assisted development using research, planning, and systematic implementation phases. Users refer to this skill as RPI, rpi or Research Plan Implement.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.