Blazemeter/claude-base

constraint-engineering

Use when a team wants to apply the Constraint Engineering guideline to a feature or repo — audits the current repo against an 8-item build checklist (spec-first, small checked steps, right-sized models, fast checks, an independent reviewer, isolated…

원문 언어: 영어

design-rationale

Produce a Design Rationale section for a design/spec/architecture artifact — justifying OOP/SOLID application, which design pattern(s) were considered and chosen (or why none applies), and which collection/data-structure was picked for each non-trivial data…

원문 언어: 영어

file-doc-task

File or update a documentation-planning JIRA task for a customer-facing feature, using the documentation team's standard template. Idempotent create-or-update — safe to run early (draft a DOC-ready ticket from the specs/design to guide development) and again…

원문 언어: 영어

example-skill

Template skill — copy this directory and edit. Replace this description with WHEN Claude should invoke the skill (e.g. "Use when the user asks to inspect X" or "Triggers on mentions of Y"). The description is the only signal Claude uses to auto-load the…

원문 언어: 영어

jira-lifecycle

Keep a related JIRA issue's status and comment trail in step with AI-driven work so the lifecycle is visible in JIRA metrics. Idempotent, forward-only transitions at each lifecycle point — move to In Progress when work starts, add progress comments for…

원문 언어: 영어

summarize-pr

Summarize a GitHub pull request — purpose, key changes, review state, CI status, and outstanding blockers. Use when the user pastes a PR URL (github.com/<org>/<repo>/pull/<n>), references a PR by number (e.g. "PR

원문 언어: 영어