'implementation' 검색 결과

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

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

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.

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

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), turn the issue into an Epic and split it into sub-issues when its work should ship as separate PRs (cc-epic-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.

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

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.

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

Write the merged Pencil design reference back into a UI implementation Issue's description. Takes the Issue number as argument, resolves the merged design PR on the `cc-ui-design-<Issue number>` branch, collects the `.pen` and snapshot paths it added, and appends (or replaces) the `## UIデザイン` section at the end of the Issue body using a lost-update-safe edit.

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

新規開発の前に、GitHub の公開リポジトリから参考実装を探す。スターの多い定番と、関連分野で実績ある作者の低スターなプロジェクトを別経路で発見し、目的への適合を軽く確認する。実装監査や依存導入そのものは対象外。

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

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.

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

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

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

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 refactor workflow — mandatory architectural justification, test verification, risk-based implementation, and scope enforcement.

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

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

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

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

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

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.

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

Integrate and maintain Robelest Convex Auth in apps by always checking upstream before implementation. Use when adding auth setup, updating auth wiring, migrating between upstream patterns, or troubleshooting @robelest/convex-auth behavior across projects.

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

Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.

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

Build secure, scalable authentication and authorization systems using industry-standard patterns and modern best practices.

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

Expert patterns for Algolia search implementation, indexing strategies, React InstantSearch, and relevance tuning

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

Use when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.

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

AI and machine learning workflow covering LLM application development, RAG implementation, agent architecture, ML pipelines, and AI-powered features.

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

Generate production-ready Next.js/React components from design specifications. Use this skill when you have a design specification document and need to create React/TypeScript components with Tailwind CSS styling, Vitest tests, and Storybook documentation.

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

Android data layer implementation guide. Provides comprehensive patterns for Room Database (Entity, DAO, Migration), DataStore (Preferences), Repository layer design, and common pitfalls. Use when implementing local data storage, cache strategies, or data source integration in Android projects.

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

JSONで定義されたAPI仕様を元にRuby on RailsでAPIと管理画面を実装するスキル。全体のオーケストレーションを行い、各ステップの詳細ガイドラインに従って実装を進めます。

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