Use when creating a Jira ticket to plan upcoming work. Guides ticket drafting with clear structure, self-contained context, and testable acceptance criteria, then creates the ticket via the available Jira/Atlassian broker tool.
Use when reviewing a pull request, branch, commit range, working tree diff, plan, document, or other coherent unit of work across correctness, security, codebase alignment, code quality, test quality, performance, and simplicity.
Use when the user asks to create or polish a standalone HTML artifact such as an HTML report, interactive explainer, visual plan, dashboard, slide deck, diagram, prototype, or throwaway HTML tool.
Use when debugging bugs, failures, exceptions, flaky behavior, regressions, or performance problems where the cause is not already proven.
Use when the user asks to build web components, pages, or applications that need distinctive, production-grade frontend interfaces with high design quality
Reference skill for browser automation: web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
Use when implementing a feature or bugfix that involves writing meaningful application logic
Use when turning an implementation plan, project plan, design plan, roadmap, migration plan, or execution checklist into a visual HTML document for easier human review.