en un clic
claude-plugins
claude-plugins contient 12 skills collectées depuis tommymorgan, avec une couverture métier par dépôt et des pages de détail sur le site.
Skills dans ce dépôt
Use when working with Jujutsu (jj) version control system, creating changes, managing bookmarks, or pushing code. Triggers on jj commands and .jj/ directory presence.
Provides Vacanti's flow metrics principles when discussing predictability, forecasting, cycle time, throughput, or delivery estimates. Triggers on keywords like "estimate", "when will", "how long", "velocity", "average cycle time", "story points", "deadline", "SLE", "percentile", "forecast"
Guides appropriate responses to process variation using Vacanti's framework. Triggers when discussing process improvement, responding to metric changes, XmR chart signals, sprint retrospectives, or when someone asks "why did our velocity/throughput change?"
This skill should be used when performing browser-based exploratory testing of web applications, including functional testing, visual inspection, accessibility checks, and performance analysis. Triggers when testing web UIs, checking for browser bugs, validating WCAG compliance, or measuring Core Web Vitals.
Turn ideas into fully formed designs through collaborative dialogue
This skill should be used when creating plan files, writing Gherkin requirements, or parsing plan file structure. Provides the plan file template and format specifications.
Opinionated REST API design guidance for resource naming, HTTP semantics, error formats, pagination, versioning, and more. Use when designing REST APIs during brainstorming or plan creation.
This skill should be used when executing plan tasks autonomously, implementing features using TDD, running the red-green-refactor cycle, handling code review loops, or dealing with blocked tasks. Provides the autonomous TDD execution workflow.
This skill should be used when the user reports "error", "bug", "problem", needs to "fix" something, mentions "debug", "failing", "broken", "issue", "not working", "crash", or any problem-solving scenario. Enforces systematic root cause identification using five whys methodology before attempting solutions.
This skill should be used when checking plan status, running verification commands, updating task statuses, or determining what work remains. Provides the verification sweep algorithm and status update procedures.
This skill should be used when performing exploratory testing of REST or GraphQL APIs, including endpoint discovery, request/response validation, authentication testing, and error handling checks. Triggers when testing APIs, validating OpenAPI specs, checking endpoint security, or verifying API responses.
This skill should be used when performing exploratory testing of command-line tools and scripts, including help text validation, option testing, error handling verification, and output validation. Triggers when testing CLI commands, scripts, build tools, or command-line interfaces.