Provides backend domain guidance for API, data, authorization, reliability, and service-boundary decisions. Workflow skills use it when backend context, validation, or expert review is needed. Follow the repository's existing architecture and conventions before applying generic patterns. Not for running tests, Docker…
Turns unclear or undecided intent into an agreed direction with enough reasoning and acceptance criteria for planning. Use for fuzzy feature requests, material product, UX, API, architecture, or stack decisions, and bug fixes where more than one cause-aligned remedy remains viable. It does not implement, decompose…
Implement a settled plan, GitHub issue, or explicit small change while preserving scope, diagnosing feedback, and producing a coherent verified diff. Use when the user asks to implement, build, code, fix an approved task, or pick up issue.
Independently review a local diff or pull request for concrete reasons not to trust the change. Compare intent and acceptance criteria with current repository behavior, inspect changed tests, apply risk-based domain lenses, and report evidence-backed findings or a clean review. Use after implementation or before…
Provides project-aware platform and release-engineering guidance for infrastructure, CI/CD, containers, observability, secrets, and deployment safety. Use when a change touches Terraform or cloud resources, pipeline workflows, Docker or Kubernetes configuration, health signals, identity, or runtime operations. It…
Design and build production-grade frontend interfaces, context first - capture PRODUCT.md (strategy) and DESIGN.md (visual system), pull reusable tokens into a design system, and apply shared UX/UI rules (color, typography, layout, motion, accessibility, anti-patterns) for brand and product surfaces. Its capabilities…
Turns an agreed Decision Brief or clear direction into a grounded implementation-ready plan with independently verifiable tasks and acceptance criteria. Use after hs-brainstorm or when the implementation direction is already settled. It does not choose approaches or write implementation code. With --gh, it publishes…
Reconcile an exact reviewed release candidate with live repository policy, then publish or merge only the outward actions the user has authorized. Use when opening or updating a PR, addressing PR review, waiting on required checks, merging, or finishing a landed change. It does not design CI/CD or cloud deployment…
Provide executable feedback on changed behavior with the smallest relevant white-box or black-box probe, then classify the result and report real evidence. Diagnose failures against accepted intent, domain rules, and current implementation before deciding whether code, tests, fixtures, or environment are wrong. Use…
★not rated 18
changed 1mo agoA84 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: