dev

Analyze and understand a problem domain thoroughly before implementation

Write Playwright acceptance tests for a user story

Fetch a Stitch design and implement it pixel-perfectly

Analyze code smells and apply comprehensive refactoring techniques

Decompose a problem analysis into granular user stories tracked as beans

Review test design quality using the Farley Index (0-10)

Refactor Playwright tests to use user-facing selectors and clean up orphaned data-testid attributes

Use for evaluating test code quality using Dave Farley's 8 Properties of Good Tests. Produces a Farley Index score (0-10) with per-property breakdown, signal evidence, worst offenders, and improvement recommendations.

This skill should be used when the user asks to "write clean code", "apply clean code principles", "follow SOLID principles", "apply GRASP patterns", "improve code quality", "naming conventions", "single responsibility", "DRY", "coupling", "cohesion", "readable code", "maintainable code", "separation of concerns", "dependency injection", or mentions clean code, design principles, or code quality. Also trigger during implementation tasks when quality matters — not only when explicitly asked. Also loaded by the /atdd and /refactor commands.

Dave Farley's 8 Properties of Good Tests, scoring rubrics, Farley Index formula, rating scale, and aggregation methodology

This skill should be used when the user explicitly asks for an interview or clarification session, says "ask me questions about this", "what do you need to know", "let me explain the requirements", "let's clarify before we start", "interview me", or "help me think through this". Also trigger when the user provides a vague or ambiguous task and asks Claude to understand it first before proceeding, or when combined with /analyze before implementation tasks where requirements are unclear.

This skill should be used when working with the /user-facing-selectors command or when the user asks about Playwright locator strategy, selector priority, user-facing locators, getByRole vs getByTestId, disambiguation strategies, "flaky selectors", "brittle tests", "data-testid", "accessible selectors", "test locators", "page.locator best practices", or needs guidance on refactoring Playwright tests to use accessible, user-facing selectors. Also useful when writing new Playwright tests — not only when refactoring existing ones.

This skill should be used when working with the /refactor command or when the user asks to apply specific refactoring techniques such as "extract method", "inline variable", "move function", "replace conditional with polymorphism", identify code smells such as "long method", "feature envy", "duplicated code", "god class", "shotgun surgery", or needs the complete catalog of 66 refactoring techniques with implementation guidance, risk assessments, smell-to-technique mappings, and sequencing dependencies. Also trigger when the user says code is messy, complex, or hard to understand and wants to clean it up.

Static detection heuristics for each Farley property, language-specific patterns for Java, Python, JavaScript, Go, and C#