1.5万 件 ・ 関連度順
概要と使いどころ
Use when designing, reviewing, or implementing a command-palette / ⌘K layer for an Apple-platform app — keyboard-first global search, ranked and grouped results, native floating panel, and protected destructive commands.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing or designing a color palette for a UI, website, or app — seven principles for premium, calm, accessible color (palette size, muted tones, contrast, accent restraint, near-black/white, consistency, whitespace).
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing, reviewing, or implementing Apple-platform toolbars — current-screen actions vs sidebar navigation, one primary action per screen, overflow menus, protected destructive actions, and keyboard shortcuts.
日本語の概要は準備中です。原文の説明を表示しています。
Obtain an independent review of the approach and trade-offs in completed work.
日本語の概要は準備中です。原文の説明を表示しています。
Update an existing GitHub Issue's description based on the issue number. Reads all issue comments and reflects any items not yet captured in the description. After refreshing the description, reviews it for remaining ambiguities or unclear requirements and posts any open questions as a follow-up 確認事項 comment.
日本語の概要は準備中です。原文の説明を表示しています。
Triage a single GitHub PR by PR number. Check out the PR's branch, detect conflicts with the target branch via `gh pr status` (and label the PR with `cc-resolve-conflict` if any are found), generate and evaluate a fix plan via create-review-fix-plan, then take action (add cc-fix-onetime label if fixes are needed, or merge the PR if it's ready).
日本語の概要は準備中です。原文の説明を表示しています。
GitHub PRの未解決レビューコメント・会話コメント・CIステータスを確認し、修正プランを作成します。
Virtual QA Lead that turns requirements into review-ready, TestRail-importable test cases in one conversation. Use it whenever the user has requirements, a spec, a user story, or acceptance criteria (PDF, DOCX, XLSX, TXT, MD, or pasted text) and wants test cases, a test plan, a checklist, test coverage, a regression suite, or a TestRail/Qase/Zephyr export, even without saying "test cases" ("write tests for this spec", "what should we check here?"). Especially useful when they attach their team's existing test cases to match. When the spec describes an API (endpoints, status codes, schemas, auth, OpenAPI/Swagger), Casely also builds a runnable Postman collection, so use it for "API tests", "Postman collection", or "tests I can run in Newman/CI". Triggers on the same request in any language.
日本語の概要は準備中です。原文の説明を表示しています。
Turn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
日本語の概要は準備中です。原文の説明を表示しています。
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
日本語の概要は準備中です。原文の説明を表示しています。
Project-level visual direction skill for WeChat Official Account articles. Use when planning, improving, diversifying, generating, or reviewing cover images and body illustrations for公众号文章, especially when Codex image generation should be used without being constrained by repetitive preset-based illustration skills.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluate, rewrite, and select WeChat Official Account article titles for open rate, depth, reader promise, and account tone. Use when drafting, reviewing, publishing, or revising公众号文章标题, especially when titles may be generic, stale, clickbait, AI-flavored, or misaligned with the article's commercial/editorial intent.
日本語の概要は準備中です。原文の説明を表示しています。
Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).
日本語の概要は準備中です。原文の説明を表示しています。
医学证据等级排序与编排层 skill - evidence grading orchestrator. 当用户请求"证据等级 / GRADE / 证据排序 / 医学证据评估 / 系统评价排序 / 临床证据排序 / 证据金字塔 / 给 PMID 打分 / Practice Guideline 优先 / Cochrane 优先 / 反向证据交叉验证 / evidence grading / quality of evidence / evidence pyramid / GRADE assessment / Cochrane review ranking / clinical evidence ranking"时,**调用本 skill 进行医学证据自动分级,自动选择最佳信息源**。本 skill 是编排层(L2)·不直接打 NCBI/Europe PMC/ClinicalTrials API,而是编排 6 个底层原子 skill(pubmed-eutils / europepmc-search / clinical-trials-v2 / aact-bulk-trials / bioc-fulltext-fetch / pubtator-entity-search)的召回结果,按证据金字塔(指南 > Meta > RCT > Cohort > Case-Control > Case Report)做 GRADE A/B/C/D 自动评级,自动剔除 editorial/letter/comment。优先使用 BioMCP MCP server 做 fan-out(genomoncology/biomcp);无 BioMCP 时走自建 slow-path 兜底。跨平台无锁(Claude Code / Codex / Gemini CLI)。
日本語の概要は準備中です。原文の説明を表示しています。
Conduct comprehensive AI-powered research with citations via the Tavily CLI. Use this skill when the user wants deep research, a detailed report, a comparison, market analysis, literature review, or says "research", "investigate", "analyze in depth", "compare X vs Y", "what does the market look like for", or needs multi-source synthesis with explicit citations. Returns a structured report grounded in web sources. Takes 30-120 seconds. For quick fact-finding, use tavily-search instead.
日本語の概要は準備中です。原文の説明を表示しています。
Design engineering principles for making interfaces feel polished. Use when building UI components, reviewing frontend code, implementing animations, hover states, shadows, borders, typography, micro-interactions, enter/exit animations, or any visual detail work. Triggers on UI polish, design details, "make it feel better", "feels off", stagger animations, border radius, optical alignment, font smoothing, tabular numbers, image outlines, box shadows.
日本語の概要は準備中です。原文の説明を表示しています。
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
日本語の概要は準備中です。原文の説明を表示しています。
Use before pushing, force-pushing, marking ready for review, or claiming checks pass on a deepseek-harness branch, and immediately after gh stack sync publishes rewritten branches, to select the smallest tests and checks that cover the outgoing or just-published diff without reflexively running the full repository suite.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you have a written implementation plan to execute in a separate session with review checkpoints
日本語の概要は準備中です。原文の説明を表示しています。
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing, reviewing, restoring, trimming, or auditing prose in the deepseek-harness repo, including deciding where documentation or comments are required across Markdown, JSDoc, code and test comments, prompts, descriptions, diagnostics, and CLI or UI strings.
日本語の概要は準備中です。原文の説明を表示しています。
Use when adding, auditing, pruning, archiving, restoring, or reviewing Agent Notes in deepseek-harness; checks every new note for superseded active records, classifies implemented notes by future decision value, deletes rejected notes that no longer prevent a tempting fallacy, and applies the frozen archived/{kind} triplet and manifest rules.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing, moving, reviewing, or auditing documentation in the deepseek-harness repo — choosing hierarchy and detail, separating tutorials from references, checking tutorial progression, trimming doc slop, responding to a verify-doc-budgets failure, or requests like "improve the docs", "audit the docs", "where should this be documented", or "this doc is too long".
日本語の概要は準備中です。原文の説明を表示しています。
A relentless interview to sharpen a plan or design.
日本語の概要は準備中です。原文の説明を表示しています。