'spr' 검색 결과

Run the full feature workflow — task validation, technical design, implementation, testing, review, and documentation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generates a commit in English following Conventional Commits based on staged changes

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run a structured code review — produces a Review Report with CRITICAL, WARNING, and SUGGESTION findings; CRITICAL findings block merge.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Spec-locked TDD with a mutation-testing gate — refine the intent into an immutable Gherkin contract (SHA-256 frozen), implement under the three laws of TDD, pass a judge audit, and merge only if every mutant dies.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the project follows API-first / OpenAPI-first approach: generating controller interfaces, DTOs, and clients from an OpenAPI spec. Use when you see openapi.yaml, openapi-generator-maven-plugin, or ApiDelegate pattern in the project.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run the API contract workflow for request/response shape changes, compatibility constraints, contract tests, documentation, and review.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when creating database migrations, schema changes, seed data, or any SQL that modifies database structure. Covers Flyway naming conventions, versioning, and safe migration patterns.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run the bug fix workflow — risk-based routing through task validation, implementation, testing, and optional review.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Configura cobertura de tests y CI pipeline

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run the refactor workflow — mandatory architectural justification, test verification, risk-based implementation, and scope enforcement.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when working in a multi-module Maven project. Covers parent POM conventions, shared dependency management, inter-module rules, and build ordering.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guides agents through Red-Green-Refactor with runner-captured evidence. Use when running /cc-tdd-cycle, writing tests before implementation, or Global TDD required is yes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run the PageSpeed performance audit — 80/20 analysis of Core Web Vitals using the PageSpeed Insights API.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when generating REST controllers, response wrappers, DTOs, error handlers, or any HTTP-facing code. Defines response envelope, HTTP status mapping, pagination, and versioning.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Read this before the first Google Drive, Docs, Sheets or Slides connector call whenever the task creates or changes a Google file. Use this skill whenever the user wants to create or change a Google Doc, Sheet or Slides file in their Google Drive. Triggers include: a request that names Google Docs, Sheets, Slides or Drive and asks to make, edit, format, copy or rename a file; a docs.google.com link with a request to change that file, even a one-line fix or suggested edits; and any follow-up change to a Google file from earlier in the chat, even "change it" or "add a tab". Includes helper scripts for document positions, cell ranges and slide layout. However, if the user asks for a doc, deck or spreadsheet without naming Google, or gives a Google file only as source material for something new, use Claude's own output type instead. Do NOT use for read-only questions about a Google file, or for Word, Excel, PowerPoint or PDF files.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx) or Word templates (.dotx). Triggers include: any mention of Microsoft Word Documents, such as 'Word doc', 'word document', '.docx', '.dotx', 'microsoft doc'. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a deliverable as a Word or .docx file (to download, email or print), use this skill. However, if they ask for a document, page, report, memo, or notes WITHOUT naming a file format and the session offers Claude's own dedicated document or page skill or connector, use that instead, even if they will email or print it. Do NOT use for PDFs, spreadsheets, Google Docs, or coding unrelated to document generation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

小红书 (XHS) 3:4 vertical cover template — two voices: spring/lifestyle soft watercolor cover with Songti + ink-green accents, and bold editorial typography cover with cobalt-blue bands + folded-paper interior. Despite the "ppt" prefix in the path, these are fixed-image XHS covers, not slide decks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Team operations dashboard template — Linear/Asana-clean hybrid with sprint status hero, 4-segment progress bar, workstream cards, chronological activity stream with colored event badges, right-rail with today's schedule + team-presence + upcoming milestones. For team status snapshots, OKR reviews, "team this week" all-hands views.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Issues, busca, comentários, tags, artigos e registro de trabalho no YouTrack Cloud via MCP oficial. Use quando o usuário disser "YouTrack", "criar issue", "minhas issues", "buscar tarefas", "comentar na issue", "atribuir para", "mudar o estado", "registrar horas", "artigo da knowledge base", ou citar um ID tipo PROJ-123. Boards e sprints são da skill youtrack-rest.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When the user wants to create, plan, or optimize a lead magnet for email capture or lead generation. Also use when the user mentions "lead magnet," "gated content," "content upgrade," "downloadable," "ebook," "cheat sheet," "checklist," "template download," "opt-in," "freebie," "PDF download," "resource library," "content offer," "email capture content," "Notion template," "spreadsheet template," or "what should I give away for emails." Use this for planning what to create and how to distribute it. For interactive tools as lead magnets, see free-tool-strategy. For writing the actual content, see copywriting. For the email sequence after capture, see email-sequence.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas. Use when asked to "weekly retro", "what did we ship", or "engineering retrospective". Proactively suggest at the end of a work week or sprint. (gstack)

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.