「implementation」の検索結果

Implement REST APIs in ABP Framework with AppServices, DTOs, pagination, filtering, and authorization. Use when building API endpoints for ABP applications.

日本語の概要は準備中です。原文の説明を表示しています。

This skill enables Claude to audit access control implementations in various systems. It uses the access-control-auditor plugin to identify potential vulnerabilities and misconfigurations related to access control. Use this skill when the user asks to "audit access control", "check permissions", "assess access rights", or requests a "security review" focused on access management. It's particularly useful for analyzing IAM policies, ACLs, and other access control mechanisms in cloud environments, applications, or infrastructure. The skill helps ensure compliance with security best practices and identify potential privilege escalation paths.

日本語の概要は準備中です。原文の説明を表示しています。

You MUST use this when building projects end-to-end. Orchestrates all 12 team roles — automatically switches between CTO, architect, PM, engineers, SRE, security, DBA, QA, and EM based on the current phase of work. Starts with brainstorming before any implementation.

日本語の概要は準備中です。原文の説明を表示しています。

Full pipeline: evaluation -> spec -> implementation -> review -> QA

日本語の概要は準備中です。原文の説明を表示しています。

Discipline skill — TDD red-green-refactor cycle. Use when implementing any feature or bugfix, before writing implementation code.

日本語の概要は準備中です。原文の説明を表示しています。

Use when implementing any feature or bugfix, before writing implementation code

日本語の概要は準備中です。原文の説明を表示しています。

Use when verified implementation is ready for an integration decision or authorized integration

日本語の概要は準備中です。原文の説明を表示しています。

Use when continuing implementation from an existing plan

日本語の概要は準備中です。原文の説明を表示しています。

Use when independent bounded tasks benefit from delegation during implementation

日本語の概要は準備中です。原文の説明を表示しています。

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

日本語の概要は準備中です。原文の説明を表示しています。

PR作成時に使用。実装レポート（計画との対応、品質チェック結果、レビュー指摘対応）をPR descriptionに出力する。

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

日本語の概要は準備中です。原文の説明を表示しています。

Re-analyze an existing GitHub Issue using its current title and body, refresh the implementation plan against the latest code state, and update the Issue in place. Use when the user provides an Issue number (numeric, `#`-prefixed, or Issue URL) and wants to regenerate the code analysis via the explore-agent subagent. For reflecting comment-driven updates, use update-issue. For creating a brand-new Issue from a natural-language task description, use create-issue.

日本語の概要は準備中です。原文の説明を表示しています。

Create or update the Pencil (`.pen`) design for a UI implementation Issue before any code is written, then open a design-only PR. Takes the Issue number as argument, delegates `.pen` edits to the pencil-design-updater agent, pushes `.pen` and snapshot PNGs on the fixed `cc-ui-design-<Issue number>` branch, and opens a PR referencing the Issue with `Refs #<N>` (never a closing keyword).

日本語の概要は準備中です。原文の説明を表示しています。

INTERNAL/HELPER skill — do NOT invoke directly from a user query. This is the shared formatter/poster used by create-issue, create-issue-from-issue-number, and update-issue. It formats an implementation-ready GitHub Issue body, runs the pre-posting checklist, executes `gh issue create` or `gh issue edit`, and optionally posts a 確認事項 follow-up comment. Invoke this skill ONLY from one of the three parent skills via the Skill tool, after the parent has completed analysis. If a user asks to 'format an issue body' or similar, route them to the appropriate parent skill (/create-issue, /create-issue-from-issue-number, or /update-issue) rather than invoking this one directly.

日本語の概要は準備中です。原文の説明を表示しています。

Triage a GitHub issue that already has the cc-issue-created label and is assumed ready to start. Inspect the comment history first to decide whether human confirmation is needed (cc-need-human-check, highest priority — reserved for issue-level deadlock, or for confirmation items answer-issue-questions already investigated and explicitly marked unanswerable); otherwise close the issue as not needed, delegate unanswered confirmation items in the last comment or the description to answer-issue-questions (cc-answer-issue-questions), refresh a description stale relative to settled comment-history content (cc-update-issue), or move to execution (cc-exec-issue). Any UI-changing issue is routed to the design-first flow (cc-create-ui-design) before execution; the exceptions are an issue whose description already names the .pen design to implement against, and a minor UI change that introduces no new visual decision (no new screen/section, no layout change, no new reusable component, no visual expression outside existing design tokens/components). Design files are never edited in the implementation PR. Dependency checks are out of scope.

日本語の概要は準備中です。原文の説明を表示しています。

Generate a structured test plan for a feature or module — covers unit, integration, contract, and edge cases without writing implementation code.

日本語の概要は準備中です。原文の説明を表示しています。

Provides fault tolerance patterns for Spring Boot 3.x using Resilience4j. Use when implementing circuit breakers, handling service failures, adding retry logic with exponential backoff, configuring rate limiters, or protecting services from cascading failures. Generates circuit breaker, retry, rate limiter, bulkhead, time limiter, and fallback implementations. Validates resilience configurations through Actuator endpoints.

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

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 full feature workflow — task validation, technical design, implementation, testing, review, and documentation.

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

Generate a structured test plan for a feature or module — covers unit, integration, contract, and edge cases without writing any implementation code.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。