4.1천건 · 관련도순
Spec-driven development lifecycle — EARS requirements, technical design docs, implementation tracking, and contribution guidelines. Use when planning features, defining requirements, or managing project lifecycle.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Orchestrates the dedicated Kinect wall harp implementation team. Use whenever the user asks to build, implement, continue, fix, QA, document, or ship the Kinect wall harp, Kinect v2 wall-depth harp, FreenectTD depth-blob hand tracking, projected wall strings, pluck synth harp, or this feature's Layer 1 tool/recipe/docs. Use this before the generic tdmcp-pipeline for this feature.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert in vector databases, embedding strategies, and semantic search implementation. Masters Pinecone, Weaviate, Qdrant, Milvus, and pgvector for RAG applications, recommendation systems, and similar
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when executing implementation plans with independent tasks in the current session — trigger phrases "execute the plan", "independent tasks", "parallel tasks", "subagents for the plan","split the plan into subagents". Dispatches a fresh subagent per task with two-stage review after each: spec compliance first, then code quality.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when implementing any feature or bugfix, before writing implementation code
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you have a written implementation plan to execute in a separate session with review checkpoints
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
設計ドキュメントに基づいて実装計画を生成します。ScalarDB特有のスキーマ定義、トランザクション実装、統合テストを含む実装可能なタスク指示書を作成し、フェーズ別の実装ロードマップを提供します。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert guidance on Swift Testing best practices, patterns, and implementation. Use when developers mention: (1) Swift Testing, @Test, #expect, #require, or @Suite, (2) "use Swift Testing" or "modern testing patterns", (3) test doubles, mocks, stubs, spies, or fixtures, (4) unit tests, integration tests, or snapshot tests, (5) migrating from XCTest to Swift Testing, (6) TDD, Arrange-Act-Assert, or F.I.R.S.T. principles, (7) parameterized tests or test organization.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design principles for building polished, native-feeling SwiftUI apps and widgets. Use this skill when creating or modifying SwiftUI views, iOS widgets (WidgetKit), or any native Apple UI. Ensures proper spacing, typography, colors, and widget implementations that look and feel like quality apps rather than AI-generated slop.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan and execute large refactor or rewrite efforts efficiently with parallel multi-agent analysis and implementation. Use when a user asks to refactor many files, split workstreams, analyze a target code area, and coordinate sub-agents with clear ownership and dependency-aware execution.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert guidance on iOS accessibility best practices, patterns, and implementation. Use when developers mention: (1) iOS accessibility, VoiceOver, Dynamic Type, or assistive technologies, (2) accessibility labels, traits, hints, or values, (3) automated accessibility testing, auditing, or manual testing, (4) Switch Control, Voice Control, or Full Keyboard Access, (5) inclusive design or accessibility culture, (6) making apps work for users with disabilities.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate a polished frontend reference screenshot through a configurable GPT-image-2-compatible generations endpoint, save and show versioned previews inside the project, revise selected previews through a configurable /images/edits endpoint, and reproduce only the user-approved design as functional frontend code with high visual fidelity. Use when Codex is asked to design, build, restyle, or recreate a web page, application screen, dashboard, landing page, or UI component through an image-first workflow, design approval loop, screenshot-driven implementation, pixel matching, or a 1:1 frontend recreation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Discuss a community-edition product requirement with the user, draft a bilingual (Chinese + English) PRD for review, then — after explicit user approval — create the English-only issue on GitHub (<OWNER/REPO>). Use whenever the user wants to turn a requirement (from a Feishu doc, a meeting note, a customer ask, or a rough idea) into a GitHub issue. Triggers on phrases like "create requirement doc", "create a requirement", "put this requirement on GitHub", "create new feature issue", "draft an issue for...", or anytime the user describes a product feature/improvement they want tracked. The format is opinionated (Background / Goal / Spec / Verification / Related, NO implementation details, draft shown bilingually for human review, issue itself written in English only).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn a sufficiently understood task into an ordered implementation plan with dependencies and verification. Orchestrate Codewhale’s native plan state; do not build a parallel planner.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when: 'do work', 'dispatch builder', or team lead triggers automated task implementation. Governs end-to-end flow from dispatch through verification, fail handling, batch mode, and escalation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Behavioral guardrails for implementation work. Reduces common LLM coding mistakes: overcomplication, silent assumption-picking, scope drift, and unverifiable success criteria. Load on Builder and software-engineer-mode.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Senior engineering analyst for code review, plan review, and automation review. Use when: (1) "review this", "analyze the code", "check this plan", (2) After implementation to verify quality, (3) "is this good enough?", (4) Before marking a task complete, (5) Reviewing a blueprint from /architect, (6) Reviewing output from /refinery. Four-lens review: architecture, code quality, reliability, performance. Reads from system/blueprints/ and source code. Outputs to system/reviews/.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when executing implementation plans with independent tasks in the current session
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when implementing any feature or bugfix, before writing implementation code
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.