app-logic
Logic for financial calculations, period management, and complex application flows.
Découvrez les skills devops project management, comparez leurs dépôts et consultez leurs instructions.
Logic for financial calculations, period management, and complex application flows.
ユーザー要件を分析し、システム設計ドキュメント(DESIGN.md)を生成します。ユーザー要件が曖昧または不明確な場合、システムアーキテクチャの設計が必要な場合、大規模な機能開発の設計仕様が必要な場合、技術的実現可能性の...
承認済みの設計書(DESIGN.md)からTDD準拠のTODO.mdを作成します。analyzing-requirementsスキルで設計が完了・承認された後に使用します。developingスキルで実装できる形式のタスクリストを生成します。
Expert UI/UX design and frontend development guidance. Use when designing interfaces, creating design systems, improving user experience, implementing accessible components, or building responsive layouts. Cove...
Jira integration via jira-cli. Use when: searching issues, viewing issue details, creating issues, transitioning status, adding comments, logging work, managing sprints, managing boards, linking issues, formatt...
Fetches Jira ticket details, creates an appropriately named branch, and initiates the task planning workflow. Use when the user says "work on [TICKET_ID]" or similar phrases.
Generate a morning MR status report. Use when the user says "morning report", "mr status", "what needs my attention", or similar morning standup queries.
Explore interaction design, user flows, and information architecture. Use when exploring "how should users interact with this?" or "what's the best way to organize this information?"
Create a lightweight implementation plan for medium-scope features (1-5 files). Use when you need a plan but not a full PRD.
Performance analysis and optimization opportunities. Use when application feels slow or before optimization work.
Tree-of-thoughts reasoning for elusive, intermittent bugs. Use when standard debugging fails or the bug is hard to reproduce.
Create technical architecture specification with data models, component hierarchy, and risk analysis. Use after PRD approval for large features.
Git workflow assistant for common tasks. Use this skill when the user asks to: - Create a commit with proper conventional commit formatting (feat, fix, docs, style, refactor, test, chore) - Create a new feature...
Use when you have a written implementation plan to execute in a separate session with review checkpoints
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...
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é.